Hatchback
Self-hosted workspace and app platform

The workspace your team can build on.

Hatchback gives everyone pages and tables to work in, and a safe place to host the small apps they vibe-code with Claude, Codex or any other agent. Apps get backends, secrets and connectors too, so nobody needs a GitHub account, a Vercel project or a Firebase key. It all runs on your own servers.

Vendors / Ledgerline

LedgerlineName · title

OwnerPKPriya Kapoorperson
StatusIn reviewselect
Renews2026-12-01date
Annual$48,000number · USD

Seat count dropped after the reorg. Finance wants a usage check before we sign the renewal. The app below reads seat logins from the Seats table.

Renewal checkapp · live
TeamSeatsActive 30dFlag
Finance4037
Operations5521Under 50%
Support2524
uses Vendors · readuses Seats · readuses Renewals · write
Using is working on content. Build changes structure, and hides every row's values while you do. Example space
The model

A page is one row, seen through a layout.

In Hatchback, pages and tables hold the same rows. Open a row and it's a page with a title, properties and a body. Look at many and it's a table you can sort, filter and edit like a spreadsheet. There's nothing to sync because there's only one copy.

NameStatusRenews
FieldkitSigned2027-03-14
LedgerlineIn review2026-12-01
ParcelpostNot started2027-01-20
Vendors, as a table view

Ledgerline

StatusIn review
Renews2026-12-01

Seat count dropped after the reorg. Finance wants a usage check before we sign.

The same row, as a page

Writes like a docs tool

Markdown shortcuts, a slash menu, mixed bullets and numbers, Tab to indent. Every shortcut is listed in the app with ⌘/.

Works like a spreadsheet

Tables have a keyboard grid, typed columns, and pages nested inside pages.

Shows where things live

The sidebar shows every page under its owner, so you always know where a new page goes.

Shares across spaces

Share a page, table or app with another team's space. It appears in their sidebar, and edits stay in one place.

Apps

Vibe-code without the stranger danger.

Someone on your team describes what they need to the coding agent they already use. The agent learns how to build for Hatchback from its connector, writes the app, and it shows up in the sidebar next to everything else. Its data stays in ordinary tables your team can open and edit.

  1. STEP 1

    Describe it

    Ask Claude, Codex or any agent connected to the space for the tool you need.

  2. STEP 2

    The agent builds it

    It reads the Hatchback connector (MCP) to learn the platform, then writes the app's source. Hatchback hosts the source.

  3. STEP 3

    Try it on sample data

    Every release opens first in a preview space: a copy of your tables' structure with its own data.

  4. STEP 4

    Make live

    Approve what it uses, then make it live. People see it in the sidebar right away.

  • It runs in a sandbox. Apps load in a sandboxed frame with no direct network access. Every outside call goes through Hatchback, using connectors you approve.
  • It only reaches what it declares. Each app lists the tables, columns, connectors and secrets it uses. You approve that list before it goes live.
  • You can audit it. Hatchback records who made each release, which code is live, and every change the app made, in the space's history.
  • There's nothing to set up. No repository, hosting account, build pipeline, database or keys. The agent gets everything through the connector.
Workers

Backends, without another account.

Apps can run small backend jobs, much like a Cloudflare Worker or a Firebase function. The connector teaches agents to use them the way they'd use Vercel or Firebase, so the code they write looks familiar.

Workers

Run on a schedule, on a request, or whenever a row in a table changes. Each worker acts as its app, with only the access you approved.

Secrets

Store API keys and credentials encrypted on your server. Apps and workers use them by name and never see the value in the browser.

Connectors

Reach Slack, Stripe, Salesforce, your own APIs and any HTTP service through Hatchback. You approve each one, and every call is logged.

One place to audit

Every run, every outside call and every change a worker makes lands in the space's history, next to the people's edits.

Self-hosting

On your servers, with your keys and your bucket.

On one machine, Hatchback needs nothing but a disk. On managed services, point it at your Postgres and your object storage and it keeps your spaces, files and app sources there. You install signed versions, upgrade when you choose, and back up to storage you own. People using it only ever see Hatchback, never the database underneath.

AWS

Install with Terraform. Backups go to your S3 bucket, keys stay in your KMS, and RDS Postgres is supported.

Google Cloud

Run on Compute Engine with Cloud Storage for backups and files, and Cloud SQL for Postgres.

Any VPS or Linux box

Debian or Ubuntu on a single disk, reachable through Cloudflare Tunnel, backing up to any bucket.

Bring your own AI

No AI bill from us.

Hatchback doesn't include a model and never will. Your people use the agents and providers you already pay for, connected to their space through the Hatchback connector.

Claude CodeCodexCursorOpenRouterany MCP client
Migration

Bring your workspace with you.

Import a team space from the docs tool you use today. Pages, databases, properties, nesting and links come across as Hatchback pages and tables, so your team keeps working on day one and can start building apps on what's already there.

  • Pages keep their shape. Headings, lists, to-dos, code, callouts and nested pages arrive as they were.
  • Databases become tables. Columns keep their types, and select options keep their colors.
  • Links still work. Mentions and links between pages point to the imported copies.
Early access

Hatchback is in early access.

If your engineers are tired of being the only people who can ship a tool, write to us. We'll set it up on your infrastructure with you.

hello@gethatchback.com Email us