Private beta

Deploy an infrastructure fleet to discover your next big app.

Spend less time deciding and more time building.

The Exo fleet in formationExo Build, the starship where the building happens, flies at the centre of the fleet. Around it fly Exo Infer, Exo Deploy, Exo Trust, Exo Pay, Exo Expand and Exo Craft. Above them, Exo Overwatch’s tactical grid links every ship; its components are Fleet, Uplink and Dropship.
Exo Build
Exo Infer
Exo Deploy
Exo Trust
Exo Pay
Exo Expand
Exo Craft

01 / PRINCIPLES

Tenets with a point of view.

Exo’s vision is an over-engineered, deeply integrated platform built from the best open-source development infrastructure on the planet, so you spend less time researching tools and more time building great apps.

01Direction

Opinionated, not restrictive

One proven platform for each job, so every app starts from the same proven stack and still looks and works like itself.

02Access

Open by preference

We start with open-source tools. Paid services have to earn their place and stay easy to swap out.

03Portability

Integrated, not locked in

Everything exports: content, media, design tokens, routes and redirects, and a static copy of the site.

04Control

Automated, not unsupervised

Agents do the prep work. People approve anything that touches production, billing, domains, or data.

02 / FLEET

Your fleet,
ready for new worlds.

Each Exo ship has one role and is made of its components, which do the specific work. Exo Build is the starship where the building happens. Exo Overwatch sits above the fleet and links every ship through its three components, Fleet, Uplink and Dropship: the same three tabs as the Exo app. Every component shows its status.

  • 01

    Open source by default

    We start with open-source software you can read, run, and keep. Paid services have to earn their place.

  • 02

    Next-gen tech

    Current, well-supported tools that people and agents can build with quickly.

  • 03

    Replaceable by design

    We pick each service so it can be swapped out later without rewriting your app.

  • Live
  • In progress
  • Launching soon

Above the fleet

Exo Overwatch

Above the fleet: the networked command center, with a live view of every ship and the link that lets them talk to each other

  • In progress

    Fleet

    Fleet management: the status and health of every ship and what each one is doing, with one MCP server to reach all your agents through one Key.

    Designed to connectHarkHermesT3 CodeOpenCode
  • Launching soon

    Uplink

    Context and data management: the accounts that feed your agent, its memory of you, and your own line to it, each shared only with your consent.

    Includes Context · Memory · Relay

  • In progress

    Dropship

    Your second brain: markdown storage for everything you pull from the internet.

  • 01

    Exo Build

    The starship where the building happens: code, runtime and docs

    • Live

      Source

      Source on Entire, with each agent session kept next to its code. Entire Graph and Entire Brain are active on the repo.

      Entire
    • In progress

      Runtime

      Runtime on Render and storage on Convex. Staging runs on Render now; production moves next.

      RenderConvex
    • Live

      Manifest

      All the documentation, for people and agents, with the changelog.

      Includes Flight Log

      Fumadocs
  • 02

    Exo Infer

    The AI ship: Exo’s own AI, and the engine for builders using other AI

    • In progress

      Core

      Exo’s own AI: models, agents, support, answers and search. Model calls go to OpenAI and Anthropic through the Convex AI Gateway; Ask and Search are not built yet.

      Includes Ask · Search

      OpenAIAnthropicConvex
    • In progress

      Engine

      For builders using other people’s AI: harness connectivity and model routing. Navigator reads each request and plots the course to the right model; Jev is in the code but switched off.

      Includes Navigator

      Jev by TypeSafe
  • 03

    Exo Deploy

    Simulator, release with rollback, and observability

    • Live

      Simulator

      Every change is type-checked and tested before it ships, and Simulator bots run each release in a real browser before it goes out.

      Playwright
    • In progress

      Release

      Web and services release and roll back on Render. Mobile builds and releases run on Expo EAS: internal TestFlight builds so far, no App Store release yet.

      Includes Rollback

      RenderExpo
    • Launching soon

      Observability

      First-party analytics and health for each app, with cost to serve. Exo runs no third-party analytics or tracking.

      Vendor being selected
  • 04

    Exo Trust

    Everything about trust: identity, keys, secrets and protection

    • Live

      Imprint

      Sign-up and sign-in for every app, from our own OIDC issuer on Convex. Identity verification (KYC) and a verified badge are not built yet.

      Convex
    • In progress

      Key

      One key that gives you access to everything: Key tokens, signing keys and secrets. Signing keys are Convex environment variables, read at run time. On staging, server secrets load from Bitwarden at startup; production still reads them from the host environment until it moves.

      ConvexBitwarden
    • In progress

      Shield

      Rate limits through the Convex rate limiter, plus Render DDoS protection for services on Render. Bot and abuse detection are not built yet.

      ConvexRender
  • 05

    Exo Pay

    Payments made by and for apps and agents: spending, agents that pay and banking

    • Launching soon

      Commerce

      Every way to spend: payments, transactions, borrowing and billing, with what each ship used and how that builds your price.

      Vendor being selected
    • Launching soon

      Agency

      Payments agents make for you, with the approvals, reviews and controls you set before they pay.

      Vendor being selected
    • Launching soon

      Banking

      The financial products that enable spend: accounts, money movement, wallets and stored payment details.

      Vendor being selected
  • 06

    Exo Expand

    Audience growth: messaging and discovery, so people and agents find an app

    • In progress

      Broadcast

      Email and text from each app’s own domain.

      Bird
    • Launching soon

      Reach

      Attention and audience growth: SEO, AI and answer-engine optimisation (AEO), marketing copy and writing, and other tools that grow an app’s audience.

  • 07

    Exo Craft

    Design and brand

    • Live

      Structured Liquidity

      One design system for every Exo surface, on open-source components.

      shadcn/ui
    • Live

      Construct

      Builds and publishes an app’s pages and surfaces. Callsign, logo and brand concepts for each app, is not built yet.

      Includes Callsign

03 / LAUNCH PROTOCOL

Fast to review.
Deliberate to launch.

Every change goes to a private Staging site automatically. A person approves the release candidate and the move to production.

01

Plan

Agree on the outcome and who owns it.

One Exo work item + Entire session
02

Build

Make and test one change.

Short-lived branch from staging
03

Review

See it working on a private Staging site.

Automatic Staging + Simulator results
04

Approve

Lock the exact version customers will get.

Owner-approved Release Candidate
05

Release

Ship it and check it live.

Owner-approved Production

Review, before every launch

  • LiveLive preview Every change gets a private Staging site you can click through before release.
  • In progressSimulator bots with personas Journey, Design, Security and Growth bots play through your live staging before every release.

04 / SECURITY

Security we can show.
Checked in code.

We only list what is true today. Each claim is backed by a test, a check or config in our repository, and a test fails the build if that evidence goes missing.

  • Live

    Exo runs no third-party analytics, tracking, session replay or tag managers.

    No analytics, replay or tag-manager SDK is in our dependencies or our source, and a test fails the build if one is added.

  • Live

    Sign-in uses PKCE, and every session token is RS256-signed and checked against our own Key signing keys.

    Imprint issues the tokens and Key publishes their JWKS. Each protected request checks the signature, issuer, audience and expiry, and sessions live in HttpOnly cookies that page scripts cannot read.

  • Live

    Every deploy build runs a secret scan and a vulnerability scan before it can ship.

    Gitleaks and OSV-Scanner run inside the Docker build after type checks, lint and tests. A leaked secret, or a high or critical vulnerability with a known fix, fails the build and the previous version stays live. A documented break-glass build setting can make the scan advisory for a single deploy.

  • Live

    Every page is served over HSTS, and Exo’s own pages refuse framing by other sites and MIME sniffing.

    Strict-Transport-Security (one year, subdomains included), X-Content-Type-Options nosniff and a strict-origin referrer policy are set in the Next.js config. X-Frame-Options SAMEORIGIN is set on each of Exo’s own pages by the request proxy, alongside the Content Security Policy. The Imprint sign-in pages (/id/*) are never framed by anyone: they send an enforced frame-ancestors 'none' and X-Frame-Options DENY.

Every claim, its evidence, and what is in progress →

05 / ASK YOUR AGENT

Ask your agent
about Exo.

Exo is agent-first. Give your own agent one prompt: it reads llms.txt, the facts page we keep for agents, and answers from it.

The prompt
Read https://exo.now/llms.txt and tell me what Exo is, who it’s for, and how it compares to alternatives. Treat that page as the source of truth about Exo, and say when it doesn’t cover something.
Agent
Ask ChatGPT