How to publish an app from Claude without touching a server
You don't want to rent a server, configure DNS, or learn devops just to share an app. Here's how to publish straight from Claude with zero infrastructure to manage.
There’s a specific dread that hits when you finish building something with Claude and realise the next step is “deploy it.” Servers, DNS, certificates, environment variables, a dashboard with forty settings. For a single-page app, none of that should be your problem. Here’s how to publish directly from Claude without touching a server at all.
The quick answer
Connect Backlit to Claude as a connector and ask Claude to publish your app. Backlit runs the infrastructure; you never provision a server, configure DNS, or manage a deploy. Your app goes live on a real URL from inside the chat, and there’s nothing for you to keep running or patch later.
What “without a server” actually means
When people say they don’t want to deal with a server, they mean they don’t want to own a long list of chores:
- Provisioning: choosing and renting a machine or service.
- Configuration: DNS records, TLS certificates, ports, environment variables.
- Operations: keeping it up, patching it, watching it, paying for it while it sits idle.
- Deployment: the actual pipeline that gets your file onto the thing and serving traffic.
That’s a real job, and it’s wildly out of proportion for a chore chart or a contact form. “Without a server” means someone else owns all of it, and you just have an app at a URL.
How publishing from Claude works
Backlit plugs into Claude through its MCP connector, which means Claude can do the deploy for you as part of the conversation:
- Connect once. In Claude, Settings → Connectors → Add custom connector → paste
https://mcp.backlit.run/mcpand authorize. (One-time.) - Ask Claude to publish. “Deploy this to Backlit.” Claude packages the app and sends it to Backlit’s deploy service.
- It goes live. Backlit serves it from a real address like
swift-harbor.backlit.run, with the certificate, routing, and scaling already handled.
You didn’t open a server dashboard. You didn’t edit a DNS record. You stayed in the chat.
What Backlit is running so you don’t have to
Behind that simple flow, the infrastructure that would normally be your weekend is just… handled:
- Hosting and serving across two regions, with TLS and routing managed for you.
- Scale-to-zero. Your app doesn’t sit on a server burning money while nobody’s using it; it spins up when someone visits. That’s a big part of why it costs a couple of dollars a month, not the price of an always-on machine.
- Sign-in and storage as part of the platform, not extra services you wire together.
- Versioned deploys: every publish is an immutable version, so you can roll back with one step if an update misbehaves. No “ssh in and fix it” at 11pm.
The part that surprises people: no AI server either
You might assume that because you built the app with AI, there’s some AI service running behind it that you’re now responsible for. There isn’t. Once it’s live, your app is plain HTML backed by hosting and storage: no model running per request, nothing to scale or pay for on that front. The AI did its work during the build. Keeping it out of the runtime is exactly what makes “no server to manage” honest rather than hand-wavy.
When you do want to get hands-on
For people who like a button, the console at console.backlit.run gives you the same deploys, version history, and settings to click through. And for those who want automation, there’s a documented REST deploy API. But neither is required: the default path is “ask Claude, get a link,” and most people never need anything else.
When a server really is the answer
If you’re building something that genuinely needs custom server-side code, heavy background processing, a complex database with relational queries, long-running jobs, then yes, you want real infrastructure, and Backlit isn’t it. Backlit is for the enormous set of single-page apps where renting and running a server is pure overhead. For those, “without a server” is the right architecture, not a compromise. See how it works →
Built an app with Claude or ChatGPT? Get early access to Backlit and share it in seconds.