Codex

Ship Codex Projects Free — No Servers Needed

Install the Hatchable plugin, then ask Codex to deploy. You get a live URL and a database, free.

How to connect → Or sign up first

What happens next

Step 1

Install the Hatchable plugin

In the Codex app, open Plugins (in the CLI, run /plugins), search for Hatchable, and install it. Manual alternative: add [mcp_servers.hatchable] with url = "https://hatchable.com/mcp" to ~/.codex/config.toml.

Step 2

Sign in with OAuth

Codex opens a browser tab for Hatchable's OAuth. No account? You'll be signed up — free, no card.

Step 3

Ask Codex to deploy

Try: "Build a daily standup notes app and deploy it on Hatchable." Codex calls the right MCP tools — live URL in under a minute.

MCP URL. Only needed for the manual config fallback, the plugin sets this up for you
https://hatchable.com/mcp

What's on the free tier

  • Live URL at {slug}.hatchable.site the moment Codex calls deploy.
  • Postgres database, auth, file storage, scheduled jobs — wired in, no config.
  • Free forever for personal projects.
  • Custom domain? Builder plan, $12/mo flat. Codex can wire the DNS once you upgrade. Free projects stay on {slug}.hatchable.site.

Why pair Codex with Hatchable instead of letting Codex run code locally

Codex can execute code in its own sandbox, which is great for one-off scripts. For anything you want to share — a tool a friend uses, an internal dashboard, a public landing page — you need a real URL, a real database, and somewhere that survives the chat session ending.

Hatchable is that surface. Codex calls Hatchable\'s MCP tools (create_project, write_files, deploy, run_function) and what gets built persists at a live URL with real storage behind it.

Frequently asked

Plugin or manual MCP config?
The plugin, unless your setup blocks the directory. Both run the same server: Streamable HTTP, protocol version 2025-03-26, at https://hatchable.com/mcp. For manual config, run codex mcp login hatchable after adding the block.
Does Codex need an OpenAI API key for this?
Codex uses your OpenAI auth as usual — Hatchable just hosts what Codex builds. The MCP OAuth between Codex and Hatchable is separate from your OpenAI key.
Can I see my deployed project before going public?
Yes — every project is private by default. Ask Codex to run functions or inspect data on your private deploy, then promote to public when you're ready.
Will I get billed for Codex hosting?
Not by Hatchable for personal-project usage. OpenAI bills you for Codex itself as normal.
Can I export my project later?
Your code is standard Node + Postgres with no lock-in, and every deploy is a real git commit.

Ready to ship?

Install the Hatchable plugin, then ask Codex to deploy. You get a live URL and a database, free.

How to connect →