Plans
Align meets you where you are: start free with the open-source CLI, move to Pro when your whole org needs one shared decision graph, and choose Enterprise when you need to run everything inside your own infrastructure.
Pricing never gates an integration, on any plan. The hosted apps capture in real time from Slack, Teams, Jira, GitHub, Confluence and Zoom, plus the MCP server for AI agents. The free CLI imports history from its own source list, which is not the same set - see Integrations. The connector SDK is open source, so both grow continuously.
At a glance
| CLI | Pro | Enterprise | |
|---|---|---|---|
| Price | Free, open source (MIT) | Talk to us | Custom |
| Best for | Individual engineers and agents | Teams whose decisions are spread across tools, squads or time zones | Security, compliance, air-gapped |
| Decision graph | Personal | Shared across the org | Shared, self-hosted |
| Integrations | All included | All included | All included |
| MCP server for agents | ✅ | ✅ | ✅ |
| Hosted connectors | - | ✅ | ✅ |
| Conflict detection & alerts | Local | ✅ Org-wide | ✅ Org-wide |
| Account required | No | Yes | Yes |
| Hosting | Your machine | Align Cloud | Your infrastructure (Helm) |
| SSO (OIDC, Entra ID, Google) | - | - | ✅ |
| SCIM 2.0 provisioning | - | - | ✅ |
| Support | Community | Priority | Dedicated + SLA |
Align implements an OIDC service provider, and federates Microsoft Entra ID, Google Workspace and Okta through it. A SAML 2.0 SP exists in the codebase, but its signing library is not bundled in the shipped image, so SAML is not available in a standard deployment. If SAML specifically is a requirement, talk to us before signing anything.
CLI
Free. Open source. No account required.
The Align CLI (@aligndottech/cli) is MIT-licensed. Read the code, run it yourself,
and import decisions from every tool you already use into a personal decision graph.
Then expose that graph as a provider-agnostic MCP server any AI agent (Claude, Cursor,
or anything else) can read.
- Imports from Git, GitHub, GitLab, Jira, Linear, Confluence, Notion, Slack, Teams and Zoom
- Personal decision graph on your machine
- Provider-agnostic MCP server
- Open source (MIT), no account required
Pro
For teams whose decisions are already spread out.
The thing that decides whether you need this is fragmentation, not headcount. A 200-person org in one building, in one time zone, in self-contained teams, mostly does fine - people ask each other. A 40-person org across three time zones with six tools and a year of history does not, and neither does the same team a year later when the person who decided has moved on.
Two shapes where "just ask the person who decided" has already stopped working:
- Across teams. Two squads reach different answers on the same question because neither could see the other's decision.
- Across time. The same people, a year on, with the reasoning gone - and an agent now writing code against whatever it can infer from the repo.
Pro builds the shared decision graph across every tool your teams already use, so people and AI agents read one authoritative answer instead of guessing.
- Everything in the CLI
- One shared decision graph across the org
- Cross-team conflict detection and alerts
- MCP server for your agents
- Priority support
Pro is offered with direct founder support rather than self-serve billing. Early customers are onboarded with success criteria agreed upfront.
Enterprise
Custom. Self-hosted. Yours to control.
For organizations with security, compliance, or air-gapped deployment needs. Run the entire stack inside your own infrastructure with no data leaving your network.
- Everything in Pro
- Self-hosted via Helm, air-gap supported
- OIDC single sign-on (Microsoft Entra ID, Google Workspace, Okta) and SCIM 2.0 provisioning
- SOC 2 and ISO 27001 roadmap - see Trust & Security for what is certified today
- Dedicated support and SLA
→ Self-hosting guide · Contact us
Which should I use?
- Just me, or wiring up an agent? Use the CLI. It is free and needs no account.
- Decisions spread across several tools, squads or time zones? Use Pro.
- Strict data residency, compliance, or air-gap requirements? Use Enterprise and self-host.
You can start with the CLI today and upgrade to Pro whenever you need the org connected - nothing you capture is lost in the move.