Aitne vs Didon

Aitne and Didon are both personal assistants tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

Aitne

Aitne is a local-first, open-source personal agent that runs on your machine, wakes at 04:00, pulls from your calendar, email, GitHub, and Markdown notes, and drops a one-page briefing into your Slack, Telegram, Discord, or WhatsApp DMs before your day starts. Hourly nudges surface urgent emails and pending PR reviews throughout the day. By evening it journals what actually happened, building a Markdown knowledge base you own entirely. The agent runs via npm with no cloud dependency — your data never leaves your machine. The ceiling appears fast: this is a single-user, single-machine system, and anything requiring team-wide coordination or multi-account enterprise integrations lives outside its scope.

Didon

Didon runs as a background process on Mac, takes periodic screenshots, and feeds them through a locally-hosted Qwen-3-VL:2b model that writes a structured work journal without any manual input. You define your projects and activity categories upfront; the AI slots every window, file, and task into that context as the day progresses. The resulting logs are queryable in plain language and exportable to CSV for billing or reporting. The local-only architecture means your screen data never leaves the machine — a meaningful distinction if you're working on client material under NDA. The single-device license and Mac-only availability are hard ceilings for anyone working across machines or on Windows.

Attribute	Aitne	Didon
Pricing	Free	Paid
Price	—	€89 one-time (lifetime access)
Free trial	No	No
Open source	Yes	No
Has API	No	No
Self-hosted option	Yes	No
Platforms	macOS, Linux, Windows (Node.js-based)	macOS
Pros	Runs the full agent loop — plan, act, reflect — on your local machine with no cloud dependency, which means your calendar, email, and GitHub data never transit a vendor's infrastructure. MIT-licensed and installable via npm, so you can audit, fork, and modify the scheduling logic or briefing format without waiting for a vendor roadmap. Delivers morning briefings and hourly nudges directly to Slack, Telegram, Discord, or WhatsApp, so you receive proactive context in the app you already live in rather than opening a separate dashboard. Markdown-based knowledge journaling writes outcomes to plain files you own outright, which means your daily reflections remain readable and searchable without the tool installed. GitHub integration surfaces PR reviews and repository activity in your morning brief, so pending teammate blockers do not stay invisible until standup.	All screen analysis runs locally via Qwen-3-VL:2b, so screenshots and work data never reach an external server — which means client confidentiality obligations do not conflict with using the tool. Context-aware categorization lets you define your own project names and activity types upfront, so the AI logs time against your actual work structure rather than generic app categories you have to remap later. Auto-launch and auto-pause tied to system sleep means tracking starts from the first minute and stops the moment you step away, so idle time does not inflate your reported hours. Plain-language queries against the work journal let you ask 'how much time did I spend on Acme this week' without building a report — which matters on a Friday when a client asks and you need an answer in two minutes. CSV export of daily logs is included without restriction, so billing reconstruction and end-of-month invoicing do not require a manual audit of your own memory.
Cons	Integrations are fixed at calendar, email, GitHub, and Markdown — there is no described plugin or extension layer, so the moment a team needs Jira, Linear, Notion, or Salesforce context in their briefing, they are editing the agent source directly or abandoning the tool. Single-user, single-machine architecture means there is no shared context, no team briefing, and no multi-account support; a team lead who needs their agent to coordinate across reports' calendars or repositories has no path forward here and moves to a hosted multi-user alternative. No API surface is exposed by the agent, so wiring Aitne into a broader automation stack — triggering it from CI events, reading its journal output in another system — requires direct file-system or codebase integration, which adds maintenance overhead the moment a second engineer touches it.	The license covers installation on one machine only. If you work across a laptop and a desktop on the same day, one machine goes untracked — there is no sync or secondary-device option, and the only workaround is running separate instances under separate purchases. Windows support does not exist in the shipping version — only a waitlist. A team where even one member is on Windows cannot standardize on Didon, and those users have to maintain a separate tracking workflow entirely. The natural language query interface operates against the locally stored log files, but there is no described API or external integration path. Teams that need time data flowing into a project management tool, accounting system, or calendar will be copying CSV exports by hand until integrations ship — a task the vendor lists as upcoming but not yet available. The local LLM is fixed at Qwen-3-VL:2b. There is no described option to swap in a different model if analysis accuracy on your specific workflow proves inconsistent. Teams that try the tool and find categorization errors on niche technical work have no tuning lever beyond adjusting the context configuration.

Bottom line

Aitne is free while Didon is paid; Aitne is open source. Choose based on which difference matters most for your workflow.

Frequently asked questions

What is the difference between Aitne and Didon?

Aitne is Free and open source, while Didon is Paid. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is Aitne better than Didon?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.

Aitne vs Didon: which should I pick?

Pick Aitne if its pricing model, openness, or platform fit matches your constraints; pick Didon otherwise. Check free-trial availability on each listing if you want to test before committing.

Comparison data is sourced and verified by the AIDiveForge data pipeline. AIDiveForge is editorially independent.