Plans
Free for one person, on your own machine. Growth when your team needs one shared record, hosted by us or in your own infrastructure. Enterprise when you also need SSO, compliance work or a support SLA.
Free
The full decision graph for one person, on your own machine. It reads your history, and your coding agent's edits can be checked against what was decided.
- All integrations included: GitHub, Jira, Linear, Slack & more
- Agent edits checked against your past decisions
- Works with Claude Code, Cursor, Codex & any MCP agent
- Runs locally, no account
- Open source (MIT)
Growth
Billed monthly, minimum 2 people
Book a demoOne shared decision graph for your team, from business intent to code. Hosted by us, or self-hosted with a licence. Decisions are captured as they're made, a person confirms which ones stand, and every GitHub pull request is checked against them.
- Everything in CLI, shared across your team
- Knows who decided what, and checks agents against colleagues' decisions
- Live capture from Slack, Teams, Jira, GitHub & more, with nothing to run
- Decisions proposed from your history, confirmed by a person
- A check on every GitHub pull request, whoever or whatever wrote it
Enterprise
For organisations that need SSO, compliance work, or a support SLA. Deploy it the same ways as Growth. Self-hosted, Align Tech Ltd has no access to your decision graph.
- Everything in Growth, hosted by us or self-hosted
- OIDC SSO + SCIM provisioning
- ISO 27001 roadmap, SOC 2 to follow if needed
- Dedicated support & SLA
Common questions
What's the difference between CLI and Growth?
The CLI is the whole engine for one person. Your decision graph lives on your machine, model calls go through your own key, and your agent's edits can be checked against it. Growth is what only works when a team shares one graph. It knows who decided what, so your agent is checked against your colleagues' decisions too. It captures from Slack, Teams, Jira and GitHub as decisions are made, with nobody running anything. A person confirms which decisions stand. And every GitHub pull request is checked, whoever wrote it.
What do I pay for on Growth?
You pay per person covered, never per check. No integration is priced or limited on its own; hosted team connectors start on Growth.
Does the Growth plan include all integrations?
Yes - all integrations are included, no limits. The connector SDK is open source, so new integrations ship continuously.
How does the Growth plan work?
Growth is hosted in our cloud, or self-hosted with a licence. We set up each team ourselves, because Growth connects to your tools and usually needs a security review first. Book a demo and we'll walk you through it.
Can I self-host Align?
Yes, on Growth or Enterprise. There are two ways to run it. For a pilot, one command installs Align on one Linux VM, with the database, cache and TLS included. We set that up with you. For production, it runs in your own Kubernetes cluster with our Helm chart, and you can mirror our images to your own registry. The pilot uses the same chart, so you keep your settings when you move. Licensing is based on the number of people covered. The deployment options are the same on both plans. Enterprise adds SSO and SCIM, compliance work and a support SLA. Contact us to talk through your requirements.
How is this different from a team-chat or workspace tool?
A workspace tool asks you to move your team into a new place to work, so context starts the day you switch. Align connects to the Slack, Jira and Confluence you already use, plus your meetings and your merged GitHub PRs, and reads the years of decisions already sitting there. The graph builds the relationships, and GitHub is the gate at the other end: Align checks every new pull request against what the graph already holds. Nothing to migrate - we'll run a scan live, on your own data, while you watch.
What does Align do on a pull request?
Two things, and they have names. The Align Report is a comment on the pull request: which decisions your change touches, and any it contradicts. The Align Decision Check is a status on the same pull request, so you can make it a required check and hold the merge until someone has looked. That is GitHub's second job - a merged pull request is a decision source, and a new one is what gets checked.