Built an app with Claude?
Share it.
You made something with AI, now it’s stuck on your screen. Backlit puts it on a live link with sign-in and saved data, set up by your assistant in the same chat. No servers, no setup. The AI builds it; Backlit just hosts it.
Built for the apps you build with Claude & ChatGPT
The moment
You built it. Now how do others use it?
It happens every time: the app works on your screen, and the next thing you ask is “how do I get my partner / my team / my customers to actually use this?” That’s the wall: hosting, a login, somewhere to save the data. Backlit is the answer your assistant reaches for, without you leaving the conversation.
How it works
Three steps to shared
Connect the MCP server
Point Claude or ChatGPT at Backlit’s MCP server, one URL, nothing to install. Now your assistant can publish for you, right in the chat.
https://mcp.backlit.run/mcp Build it like you already do
Keep talking to your assistant. Start something new or bring an app you already made, and Backlit wires sign-in and per-user data into it as you go.
window.backlit.auth.user() Get a link to share
Ask your assistant to publish it. It goes live on its own link with the right people on the allowlist. Send it to your family, your team, or your customers.
→ bright-ledger.backlit.run Prefer to click? The same thing is available in the console. But the headline flow is simple: ask your assistant, get a link.
The distinction
Built with AI, hosted by Backlit
Two different jobs. The AI builds your app; Backlit is the home it lives in once it's built. Backlit isn't another AI bolted into your app, thinking on every visit. Nothing AI runs in the live app. That's what keeps it fast, private, durable, and $2.50 a month, not a per-visit AI bill.
Security
The hard part, handled
Apps built fast with AI keep getting hacked, almost always at the login. Backlit owns that part: sign-in, an allowlist, per-user data isolation, and private-by-default access are built into the platform, not left for you to hand-roll. You focus on the app; we've got the hard, risky bit covered.
Features
Everything a glow needs to shine
Lens: sign-in, handled
Magic link, Google, and Microsoft sign-in. Allow exact emails or a whole domain. Private by default.
window.backlit.auth.user() Ember: saved data
Shared state, per-user silos (isolated by email), and a write-only store for form captures. Region-pinned.
window.backlit.userdata.get(k) Public glows
Flip a glow public and it opens to anyone, no sign-in, an anonymous session minted on first visit.
auth_mode: public Deploy + rollback
Every publish is an immutable version. Roll back to any prior version with one call. No downtime.
POST /v1/glows/{id}/rollback Two regions
Served from Australia and the US. Your users’ data is pinned to one region and never crosses.
region: au · us Prism: custom domains
Free glows get a friendly adjective-noun address. Paid plans unlock a custom subdomain or your own domain.
yourname.backlit.run Your data, both ways
Put data in. Get it back out.
Your app saves data, and because it's reachable through Backlit's MCP, you can query it straight from Claude: ask for a summary, export it to a spreadsheet, or push it into Notion, in plain language. Most hosts hand you a database to query yourself. Backlit closes the loop.
Pricing
Start free. Stay cheap.
Ship a private app for free on Spark. Brand it and grow your allowlist on Beam at $2.50/mo. Go public and scale on Flood. Add storage by the pack with Amp.
For AI agents
Agents deploy without asking
Backlit is built for both surfaces. A documented MCP server and REST deploy API let AI agents discover the platform, create glows, push HTML, and manage allowlists, entirely on a user’s behalf. See the agent surface →
A private, invite-only beta
Backlit is currently in a closed beta with a small group of builders. Public sign-up is coming soon. In the meantime, the blog has the full story.