Start free. Wire Claude or Cursor to your decision graph in 90 seconds. Partner with us when you need the whole org connected.
Personal use. Import decisions from every tool you already use - then expose your local graph as a provider-agnostic MCP server any AI agent can read.
Full product, all integrations, and direct founder support for teams helping shape Align. The shared decision graph across your whole org - captured from every tool your teams already use.
For teams that need self-hosting, SSO, or compliance. Run Align in your own infrastructure, where Align Tech Ltd has no access to your decision graph.
Docs tell agents HOW things work. Code tells them WHAT was built. Neither tells them WHY decisions were made or what conflicts with what. The CLI gives your local AI agents that missing layer - a structured decision graph for your own repos. Pro scales it to the whole org: decisions captured from every tool, linked across teams, with conflicts surfaced before they reach production.
Yes - all integrations are included, no limits. The connector SDK is open source, so new integrations ship continuously.
Self-serve signup is closed. We onboard teams via a demo and work closely with each team as we grow together. Book a demo and we'll walk through the details.
Yes - self-hosted deployment is available on the Enterprise tier via Helm chart. Supports air-gapped environments and internal registry mirroring. Licensing for Enterprise and self-hosted is based on team size. Contact us to discuss your requirements.
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.
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.