Skip to main content

Quickstart

Two ways to start, and only one of them needs us.

Start now, on your own (free)

The CLI is published on npm, MIT-licensed, and needs no account and no workspace. This is the fastest way to see what your agents are missing:

npm install -g @aligndottech/cli
align import git # your own repo history - no token needed
align mcp --setup # wire it into Claude, Cursor or Copilot

Then ask your agent something only the decision graph knows. Full command reference: CLI.

Start with the shared org graph (Pro)

The hosted product gives you one graph across every team's tools, real-time capture, and cross-team conflict detection. Self-serve signup is not open yet.

The rest of this page covers the hosted experience.

Step 2: Connect Your Tools

Go to SettingsIntegrations and connect the tools your team uses. See our integration guides for detailed setup instructions for each connector.

Step 3: Capture Your First Decision

Once you've connected your tools, capture a decision. In your connected communication tool, mention Align:

@align We decided to use PostgreSQL instead of MongoDB
for the user service because we need strong consistency
for financial transactions.

Align will:

  1. Acknowledge the capture
  2. Synthesize the decision context
  3. Create a Decision Snapshot
  4. Post a confirmation back

You can also capture decisions from Jira comments, GitHub discussions, Confluence pages and meeting transcripts - depending on which integrations you've enabled.

Step 4: View Your Decision

  1. Go to your Align dashboard
  2. Find the decision in your feed
  3. See the full context: participants, rationale, evidence links

What's Next?

Explore Integrations

Connect Slack, Teams, Jira, GitHub, Confluence and Zoom.

View Integrations →

Import History

Use Discover to find past decisions.

Learn About Discover →

Invite Your Team

Add teammates to collaborate.

Manage Settings →

Tips for Better Decisions

  1. Be specific - Include the "why" not just the "what"
  2. Tag participants - Mention everyone involved in the decision
  3. Link evidence - Reference Jira tickets, PRs, or docs
  4. Use context - Align captures the surrounding conversation too