Skip to content

What it is not

SituationWhy Nota is strong here
Many small responsibilities, little time — a solo developer, a freelancer, a small agencyone glance instead of ten tools; “All clear” in two seconds
Technology and administration in one handservers, deadlines and invoices stand in the same list, because they are the same question: what needs me?
Cost and revenue per client or projectmoney rolls up along “is part of”; most costs are declared, not fetched — the way they really arise
Working with coding agentsthe Brief is the hand-over, with the history and what helped last; over MCP the agent can ask back — without Nota executing anything
Processes that fail silently — backups, imports, evaluations, AI runsabsence is a rule of its own; nobody has to report a failure
Costs that vary per event — tokens, text messages, API callsan event carries its amount, or a quantity with a price
  • Operations: servers, services, certificates, domains, backups, jobs, cloud costs.
  • AI processes: steps, failed runs, cost and revenue per run.
  • Administration: tax and contract deadlines, insurances, cancellation dates, subscriptions.
  • Money: invoices and bills as outstanding amounts, retainers, rents, depreciations, the balance per client.
  • Projects: milestones from a template, with invoices that follow milestones.
  • The client’s view: all of the above per client, because a client is a thing that other things are part of.
NotInstead
accounting — no accounts, no tax, no receiptsthe ledger stays the book; Nota reads from it
a to-do app — only tasks with a due date appearthe task list stays where it is
project management — no Gantt chart, no resources, no percent completea schedule that says what is due
a dashboard builder — no query language, no charts of your ownone fixed view that looks the same for everything
a tool that acts — it starts, stops and changes nothingit hands over: to you or to an agent
a long-term archive for measurementsthe last value and one day of history; history belongs in a sink

If you already have a tool for one of these: good. Nota wants to use its source, not replace it.

  • The iPhone app is in development. It is not in the App Store and has not been seen on a device.
  • Push to the phone needs a relay that is not running yet. ntfy and webhooks work.
  • Prices and a licence are not decided. See pricing.
  • The agent package has no signed package repository yet; it is installed from a package file.
  • The widget, as designed, shows cost only: it has room for one amount.
  • What time changes, the core notices at its next tick. After a host comes back, its sign of life and its missed job stay red until then — seconds in practice.
  • A plan knows no parallel people and no effort.
  • The Beancount reader takes plain transactions only: cost and price annotations are ignored, includes are not followed, and what was not read is named.
  • What sources deliver is never translated: a German dashboard can carry an English Brief.