Codex hosting with a permanent URL and a real backend.
Your Codex sandbox URL expires — get a permanent URL, with a real backend (database, functions, email) the app actually needs. Codex publishes to shiply.now in a single call: no account to start, a flat bill, and re-publishing updates the same URL.
Publish my site to shiply.now and give me the live URL. Read https://shiply.now/skill.md first — it is the live API map. Before publishing, look for .shiply.json and existing Shiply credentials; if MCP is connected, call whoami. If no valid credential is available, publish anonymously immediately — never block the first live URL. Then show me Shiply’s REAUTH_REQUIRED verification link so I can claim it. If I choose email reconnect, request the six-digit code, wait for me to paste it, verify it, and securely save the returned API key. In a cloud sandbox, use the raw HTTP API only (no npm or install scripts). Follow Shiply’s JSON errors and docs pointer; don’t guess.
From Codex to a permanent URL
Three steps, all driven by the coding agent you already run in the terminal.
Add the MCP server
Drop the [mcp_servers.shiply] block into your Codex config.toml pointing at https://shiply.now/mcp — Codex gets a publish_site tool. Or skip config and paste the publish prompt.
Codex publishes in one call
Codex can run shell and HTTP, so it publishes your built app in a single request — via the publish_site MCP tool, the shiply CLI, or a raw POST to /api/v1/publish.
A permanent, claimable URL
The call returns a live <slug>.shiply.now URL right away. Anonymous for 24 hours, claimable in one click to keep it forever — and re-publishing updates the same slug.
MCP config, or a raw publish
Configure the shiply MCP server once, or have Codex publish over the CLI or plain HTTP. All three return the same permanent URL.
The shiply MCP server for Codex
Add the [mcp_servers.shiply] block to your Codex config.toml and Codex gets a publish_site tool. One tool call uploads your project and returns the live URL — no shell, no copy-paste, no context switch out of the agent. Drop the header to publish anonymously first.
- Point config.toml at https://shiply.now/mcp
- A publish_site tool, callable straight from Codex
- Returns the permanent URL inline in the session
Or publish over the CLI or raw HTTP
Prefer no config? Codex can run the CLI (npm i -g shiply-cli, then shiply publish ./dir) or send a raw POST /api/v1/publish. No token is required to make the first site, and re-publishing the same site updates the same URL — never a new one.
- CLI: npm i -g shiply-cli, then shiply publish ./dir
- HTTP: POST https://shiply.now/api/v1/publish
- Re-publishing updates the same URL — never a pile of dead links
Why shiply for Codex projects
Static-only hosts stop at files. The backend is the difference — real, factual, on the plans below.
Real databases
Cloudflare D1 on every plan, with Neon Postgres on Developer — real SQL data, not just static files.
Edge functions
Workers Lite functions run dynamic endpoints at the edge. No server to provision or keep running.
Per-site inbox email
Every site gets its own inbox, so a form or contact endpoint can receive email without a third-party service.
Custom domains
Point your own domain at any site. DNS is provisioned through Cloudflare and SSL is issued for you.
No account to start
The first publish needs no sign-up. You get a live URL instantly, valid for 24 hours, claimable to keep forever.
Flat price, no meter
Flat $0 / $8 / $24 a month with no usage meter. A viral day moves your traffic, not your invoice.
Re-publish, same URL
Publishing again updates the same site in place. Iterating in Codex never spawns a pile of dead URLs.
Instant SSL
Every site is served over HTTPS from the moment it is live — on the shiply.now slug and on your custom domain.
What Codex does well
Codex is a strong coding agent — it can read a repo, run shell, and make HTTP calls to ship real work.
Codex is excellent at building and editing the app itself — reasoning over a codebase, running the build, and driving the publish call. shiply.now handles the other half: it gives what Codex builds a permanent home with a real backend, so the two fit together in a single call.
Codex hosting — common questions
How do I host a project built with Codex?
Connect the shiply MCP server to Codex, then have Codex publish in one call. Add the [mcp_servers.shiply] block to your Codex config.toml pointing at https://shiply.now/mcp and Codex gets a publish_site tool; or run the CLI (npm i -g shiply-cli, then shiply publish ./dir); or POST to /api/v1/publish. Each returns a permanent <slug>.shiply.now URL. No account is needed to make the first site.
Does the URL from Codex expire?
A sandbox or preview URL expires; a shiply.now URL does not. The first anonymous publish is live for 24 hours, and one click claims it to keep it forever on a free account. Re-publishing updates the same slug in place, so the link you share never changes.
Can a Codex-hosted site have a real backend?
Yes. Static-only hosts stop at files. shiply gives every site a real backend: a Cloudflare D1 database on every plan, Neon Postgres on the Developer plan, Workers Lite edge functions for dynamic endpoints, a per-site inbox for email, and custom domains through Cloudflare. That is the difference versus a static-only Codex sandbox URL.
What does Codex hosting on shiply cost?
A flat price with no usage meter: $0 on Free, $8 a month on Hobby, $24 a month on Developer. The number on the card is the number you pay whether the site gets ten visitors or ten thousand on its best day — no per-request billing, no credits, no surprise spike.
Host your Codex project on a permanent URL.
No account needed. A real backend on a flat bill, live in a single call.