How Align works, in detail

From one open request to a confirmed answer

Seven steps, one example. Use the arrow keys, swipe, or press play.

The example is illustrative. Anything marked in development or planned is not available yet.

Step 1 of 7

A simple question with a scattered answer

A customer asks whether 15 July is confirmed. It could arrive as a message, a ticket or a call note. The answer depends on a ticket in review, a price clause in a quote and three people.

Each of them holds a piece. Nobody holds all of it.

Reading Gmail (read-only) and Linear: available now Other sources: in development
Step 2 of 7 · Setup

Everyone involved has Align Desktop and Align Mobile

Each person works in Align Desktop and Align Mobile. Their devices stay in step through Align Relay, so when one person moves something, everyone else involved sees it.

Only status travels between devices: who owes what and what changed. Your messages stay where they are.

Align Desktop: available now Several people on one request: in development Align Mobile and Align Relay: planned
Step 3 of 7 · Setup

You choose where the thinking happens

Align Desktop and Align Mobile stay the same in every setup. What changes is where Align Node, the brain, runs.

Everything runs on hardware you own: a capable desktop, or a server in your office that everyone’s desktop uses. Nothing goes to an AI provider.

Your hardware does the everyday work: watching, sorting and drafting. The hardest calls can use a cloud model, but only for content that is not sensitive. Sensitive content stays on your hardware.

We host everything. No setup, and the most capable models on every task, billed per use.

Model cost: the hardware you already own

Model cost: a small share, billed per use

Model cost: billed per use

How devices stay in step is a separate choice: the relay Align hosts, your own, or none if you are air-gapped.

Align Node inside Align Desktop: available now Shared office server and hybrid mode: in development Align Relay: planned Cloud node: planned
Step 4 of 7 · Align

Align finds who holds each piece

Align Node works out who holds each part of the request and sends each person only that part: the CEO a price approval, the product manager the reply, the tech lead the blocked ticket.

Each part arrives as the same three-line card: why it is yours, the one move to make, and what the agent does once you approve. Nobody sees anyone else’s inbox.

Routing to several people: in development Align Mobile: planned
Step 5 of 7 · Action

Each person takes one action, wherever they work

Nobody has to move into a new tool. The CEO taps Approve on the phone. The tech lead reassigns the review in the tracker. Or someone simply replies in whatever channel they use.

Align records every action on the same request and updates everyone’s devices, so all three see the same status without anyone reporting it.

One shared status across people: in development
Step 6 of 7 · Agent

Agents carry out what was approved

With both blockers cleared, the product manager approves the drafted reply. Agents send it, record 15 July as a promise and keep watching the ticket it depends on.

Every step is logged on Align Node.

Sending on your behalf: in development
Step 7 of 7 · The answer

The customer gets an answer that holds

The date is confirmed by the people who own each part, the same morning. No forwarding, no status meeting, no guessed dates.

Align keeps tracking the promise until it is delivered.

Back to overview
Customer request
Is July 15 confirmed?
Marketing spend locks on Thursday
Messages
A thread with three replies and no answer
Ticketing
ENG-482 has been in review for six days
Contract
Quote of 3 May, with a price clause
People
CEOPMTech lead
Travels through Align Relay
Who owes whatWhat changedApprovals
Stays where it is
Message contentDocuments
Product manager
DesktopMobile
Align Relay
Keeps every device in step
Tech lead
DesktopMobile
CEO
DesktopMobile
Your environment
Your team’s devices, unchanged
Align Node · the brain
On your hardware
Inside a desktop, or on an on-prem server
All reading and reasoning
Watching, triage and drafting
Sensitivity check
Sensitive stays local
Cloud model
Hardest calls, non-sensitive only
Cloud model
Not used
Align Node · the brain
In Align Cloud
Product manager
DesktopMobile
Tech lead
DesktopMobile
CEO
DesktopMobile
Align Relay
Phone notifications, no content
Align Node
One request
Three parts, three owners
Align Desktop · Product manager
AlignYou own the reply. It waits on the price and ENG-482.inbox, ticketing
ActionSend the drafted reply
AgentInbox Agent sends it and watches the thread
Align Desktop · Tech lead
AlignENG-482 in review six days. A promised date depends on it.ticketing
ActionReassign the review
AgentWatchdog nudges, then escalates in 48h
09:12
Align
AlignThe reply is blocked on your price approval, quote of 3 May
ActionApprove the price
AgentInbox Agent tells the PM
Align Mobile · CEO
09:12
Align
Price approval needed

Quote of 3 May.

Approve Approved
CEO taps Approve in Align Mobile
One A³ item
Is July 15 confirmed?
PriceWaitingApproved
ENG-482WaitingReassigned
ReplyWith PM
Same state on every device
Ticketing
In review
ENG-482
Reassigned
Tech lead moves it by hand
Any channel
CEO replies to the PM
“Price is confirmed.”
Counts the same as a tap
Align Desktop · Product manager
Drafted reply to Alex Chen

Hi Alex, July 15 holds. The last dependency closes this week, and I will confirm in writing by Wednesday. If anything moves, you will hear it from me first.

Approve and send Edit
Agent log · on Align Node
09:31
Inbox AgentReply sent to Alex Chen
09:31
Watchdog15 July recorded as a promise
09:32
WatchdogWatching ENG-482 until it closes
09:32
AlignItem closed for all three people
Sent 09:31
To Alex ChenSent
Re: Launch date confirmation, Checkout v3

Hi Alex, July 15 holds. The last dependency closes this week, and I will confirm in writing by Wednesday.

CEO
Confirmed the price
Tech lead
Cleared ENG-482
Product manager
Sent the reply
Promise15 July Tracked until delivered
1 / 7