Skip to main content
RelayOSSee pricing

From meeting → merged

Ship what your team decided.

RelayOS turns cited meeting decisions into approved work—and closes the same object when the pull request merges.

See the execution loopWatch the handoff
Human approvalOne identity to Done
Execution feed@northstar/activation
Live
  1. AM

    Alex Morgan@meeting · 09:41

    “Review activation telemetry and publish the decision before Friday.”
    Transcript 09:41:12 · Source attached

  2. RelayOS@relay · 09:42

    Replying to @meeting

    Proposed work · Review activation telemetry

    Waiting for a personApprove & create
  3. AM

    Alex Morgan@alex · 09:44

    Approved
    RLY-12 · IN PROGRESSReview activation telemetrySame evidence. Same owner. Canonical work.
  4. GH

    GitHub@delivery · 11:08

    product #238570 merged

    RLY-12 moved to Done. The original decision is closed.
4 events1 WorkObject0 copied tasks

The 12-second handoff

Follow one decision all the way to Done.

Every state change is visible. The source, approval, work, and delivery stay on one trace instead of splitting across four tools.

See the authority layer
RLY-12 / execution trace12 sec · loop
  1. 01Evidence
  2. 02Approval
  3. 03Work
  4. 04Delivery
A cited commitment becomes one approved WorkObject, then closes when delivery merges.

Human authority

AI drafts. People publish.

RelayOS can prepare the action, but it cannot silently create shared work. The exact source stays visible until a person approves the write.

  • Source visible before approval
  • Actor and timestamp recorded
  • No approval, no canonical write

Meeting evidence@source · 09:41

“Review activation telemetry and publish the decision before Friday.”

Transcript citation · Alex Morgan

Proposed action@relay · 96% confidence

Review activation telemetry this week

Nothing becomes shared work until you approve it.

Review requiredApprove & create

Guided activation

Learn the loop by running it.

No empty product tour. RelayOS guides you through 3 real actions using work your team actually intends to ship.

Plan guided activation
  1. 01
    @you00:40

    Create one real outcome

    Use work your team actually intends to ship.

    Next action unlocked
  2. 02
    @relay01:35

    Approve the cited decision

    Read the source before it becomes canonical work.

    Next action unlocked
  3. 03
    @github02:50

    Close it with a merge

    Delivery updates the same object you started with.

    Outcome delivered

B2B pricing

Start with one team. Keep the whole loop.

Every plan includes evidence → approval → work → delivery. Scale seats, not complexity.

Starter

For a founder turning decisions into product.

$30/ month
  • Up to 5 people
  • Cited action drafts
  • Approval before every write
Start with Starter

Team

Most popular

For one product team shipping every week.

$150/ month
  • Up to 15 people
  • GitHub delivery mapping
  • Guided team activation
Choose Team

Business

For several squads sharing one execution system.

$300/ month
  • Up to 30 people
  • Multi-team rollout
  • Quarterly workflow review
Choose Business
Annual$3,000/ year

Save $600 and include a founder-led activation workshop for your team.

Evaluate annual

THE EXECUTION SYSTEM FOR PRODUCT TEAMS

Keep the why. Ship the work.

Compare preview plans