Allied Note
In development · Phase 0

Status and roadmap

Where the project stands

In development. Phase 0 of 9: foundations. There is no product to use yet.

Last updated .

What exists today

  • Exists

    • A code repository with a build, lint, test and type-check gate
    • Written architecture decisions, with the open ones marked
    • The planner’s date rules for weeks, fiscal years and quarters, with tests
    • Placeholder pages for the API and the web app
    • This website

  • Does not exist yet

    • Accounts, sign-in, or anything to sign in to
    • The editor, notebooks, search or sync
    • The planner screens and the goal cascade
    • Nabu
    • The API, MCP server, CLI, importers and embed
    • Desktop and mobile apps

The hosted app is planned to live at app.alliednote.com. There is nothing to use there yet.

Roadmap

Ten phases, each with an exit test. A phase does not start until the one before passes its test. There are no dates here on purpose, and the order of later phases may change.

  1. Foundations In progress

    • Monorepo scaffold, CI and a single check command
    • Architecture decision records, threat model outline, cost model structure
    • Planner date rules: weeks, fiscal years and quarters, with tests

    Done when: A fresh clone passes every check, and the self-host stack serves a hello page from the API and the web app.

  2. Core notes Planned

    • Accounts, workspaces and row-level security
    • The notebook tree: notebooks, tabs and three page levels
    • Rich text editor whose every block exports to Markdown
    • Full-text search, backlinks, attachments, Markdown export

    Done when: Create a notebook five levels deep, edit it in two browsers, export it to Markdown, import it again and get the same tree.

  3. Planner and goals Planned

    • Settings for week start, timezone and fiscal year
    • Quarter tabs with week and day pages, and a today view
    • Goals and tasks, with page checkboxes and tasks kept in step
    • Goal cascade onboarding as a form

    Done when: A new user reaches a filled-in week in under five minutes.

  4. Offline, desktop and mobile Planned

    • Local storage and an offline edit queue
    • Installable web app, desktop builds and mobile builds from one codebase
    • Quick capture on mobile

    Done when: Edits made in airplane mode on a phone and a desktop merge cleanly when both reconnect.

  5. API, MCP server and CLI Planned

    • Public REST API with scopes, rate limits and webhooks
    • MCP server so other agents can read and write notes
    • Command-line tool

    Done when: An outside agent, given only the docs and a key, creates a page, adds tasks and reads today’s plan.

  6. Nabu, first version Planned

    • Capture, align, prioritize and weekly review
    • A visible log of every run, approvals and cost tracking
    • The goal cascade as a conversation
    • Handing tasks to agents you connect, under an approval policy

    Done when: Nabu produces day plans worth following from real, messy days, and a hostile note or transcript cannot trigger an action outside the notebook.

  7. Importers Planned

    • One import pipeline with a dry run and a report
    • Markdown folders first, then other note apps

    Done when: Each importer passes its set of real export files and reports accurately what came in, what was flattened and what failed.

  8. Transcript ingest Planned

    • One ingest endpoint for meeting and voice transcripts
    • Email-in and file drop

    Done when: A recorded meeting lands on today’s page with a summary and goal-linked tasks, with no manual step.

  9. Embed and white label Planned

    • Host apps, signed tokens and the embed package
    • Theming, events and custom domains
    • First host app: one of our own products

    Done when: One of our own apps runs on the embed in production, with single sign-on and its own styling.

  10. Billing and launch Planned

    • Plans, billing and usage metering
    • Security review, license files, contributor guide, self-host docs
    • The repository becomes public

    Done when: A stranger can sign up, import their notes and self-host from the README without help.

Not decided yet

Things we would rather mark as open than guess at.

License
Allied Note will be open source. Which license, and whether contributors sign a CLA or a DCO, is not decided. Until it is, the code is all rights reserved and the repository is private.
Pricing
A free plan, low-cost paid plans and free self-hosting are planned. No price is set. Numbers will come from a cost model, not a guess.
Mobile shell
Which wrapper the mobile app uses is open until mobile editing passes a hands-on test.
Week start changes
What happens to the days between two quarters when a user changes the day their week starts on.