Five AI coding agents, scattered across your machine.
NEST holds the helm.

Built by those who run agents in production

The same control plane FACTA runs on its own agents. Not a wrapper — a real Rust server.

• 5 agents live today
• Rust server · single source of truth
• PostgreSQL persistence
• Per-agent permission gates
• Audit trail on every session
• BYOK — no lock-in

The problem

Every agent runs in its own silo. None answers to one helm.

Claude Code, Codex, Cursor, Gemini, OpenCode — each a powerful agent, each its own process, its own context, its own unaccountable loop. You switch between terminals, lose the thread between sessions, and no single log holds what any of them actually did.

A professional AI coding workflow needs one source of truth — not five tabs and a prayer.

The platform

Three steps. One control plane.

Install the Rust server, sync your agents to it, and govern every session from one log.

Five agents live today — Claude Code, Codex, Cursor Agent, Gemini, OpenCode. Self-hosted, source-available.

01

Install

Run the Rust server locally or in Docker. PostgreSQL persists sessions, messages, and events. One binary, one source of truth.

02

Sync

Point the CLI at your agents. NEST speaks Socket.IO, SSE, and REST so every agent reports to the same session log — terminal, PWA, or browser.

03

Govern

Set per-agent permission families, watch every session from the PWA, and keep a full audit trail. Nothing ships without the gate opening.

The agents — 5 live today + Voice

Every agent you already run, on one hub

Five agents ship today, each live and wired to the same Rust server. Voice drives them all from one console.

● Live

Claude Code

Anthropic's CLI agent, accountable to one session log.

● Live

Codex

OpenAI's coding agent, governed from the same helm.

● Live

Cursor Agent

The IDE agent, synced to the server's source of truth.

● Live

Gemini

Google's agent, running in the same formation.

● Live

OpenCode

The open-frame agent, its workings visible and logged.

● Live

Voice

Drive any agent from one console — voice as the helm.

Who it's for

A specific answer for every operator

From the solo dev in the terminal to the platform engineer routing every line — one server, one log.

The solo dev

One terminal, one server, every agent on it. No context lost between sessions.

The team lead

Watch every agent session from one PWA. The team's work, one log.

The security engineer

Per-agent permission gates and a sealed audit trail. Legal can read it.

The platform engineer

Every agent's line routing through one lit junction. Docker images included.

Why different

Five agents in five silos.
Five agents on one helm.

Three ways teams try to run AI coding agents — and where each one breaks.

Enterprise

Your security team approves from the start.

Self-hosted Rust server, PostgreSQL persistence, per-agent permission families, and a full audit trail. BYOK. No training on your data.

Self-hosted

Run the Rust server on your own metal. Zero egress.

Audit trail

Every session, message, and event logged in sequence.

Permissions

Per-agent mode families. Each gate keyed and counted.

Mobile oversight

The PWA mirrors the server. Watch from anywhere.

By the numbers

One server. Every agent accountable.

Figures derived from running NEST on the FACTA codebase. Verify against your case in a demo.

Start today

Five agents in five silos.
Put them on one helm.

Clone NEST, run the Rust server, and point the CLI at your agents. Install → Sync → Govern.

Pricing

Start at zero. Self-host the server.

NEST is free and self-hosted — clone it and run the Rust server today. Cloud adds managed persistence, permissions, and mobile oversight per key.

NEST is free because the control plane should be frictionless. Cloud is the only thing we charge for.

No card required for Solo · Cancel Team keys anytime · NEST is yours to self-host, free

See full pricing on ctx0.io

Why $49, and why per key

The API key is the unit of value — so it's the unit of price.

One key maps to one operator's identity and one seat on the server. You pay for the agents that actually work, not for seats that sit idle.

Land with 3–5 keys, expand as the helm proves its worth.

How teams grow into NEST

From a free download to org-wide oversight

Four steps — and you only pay at the step where it already pays for itself.

This is land-and-expand — the pricing is built for it.

Install

NEST

Self-host the Rust server free. Evaluate the control plane with no commitment.

Connect

Solo

One free key on managed cloud. See the server on your agents.

Govern

Team

Add keys at $49 each as the audit trail proves the value.

Expand

Enterprise

Org-wide oversight, sovereign deployment, dedicated support.

Why per key pays off

What actually changes

No invented dollar figures — the savings are in sessions and in the work you stop losing track of.

Agent-silo figure: derived from FACTA's own deployments.

Security you can put in front of legal.

We don't train on your data. Self-hosted Rust server for full sovereignty. Per-agent permission gates and a full audit trail on every session.

• ✓Rust server — self-hosted, zero egress
• ✓PostgreSQL persistence, encrypted at rest
• ✓BYOK — bring your own keys
• ✓No training on your data
• ✓Per-agent permission families
• ✓Audit trail on every session

No lock-in, no surprises

• NEST is yours to self-host, free
• No card required for Solo
• Cancel Team keys anytime
• Export your audit trail anytime
• Open-source core

FAQ

Frequently asked questions

Everything you need to know before getting started.

Start at zero

Ready to
hold the helm?

Clone NEST free and self-host the Rust server today, or start a free Solo key on managed cloud. Add keys when the audit trail proves the value.

• Free, self-hosted NEST
• No card for Solo
• Cancel anytime