Connect Backlit as an MCP connector, then ask your assistant to publish the app. Backlit hosts it on its own link with sign-in and saved data, and hands you a URL to share with the people you choose, all without leaving the chat.

Most AI-built apps run only on your screen. Backlit puts your HTML app online on a real link, adds a sign-in allowlist so only the right people can open it, and stores the data they enter. Share the link and they can use it.

You don’t write any auth code. Backlit’s Lens layer gives every private app magic-link, Google, and Microsoft sign-in, gated by an allowlist of emails or a domain pattern. Your app reads the signed-in user with window.backlit.auth.user().

Yes. Backlit’s Ember storage gives each app four stores, all region-pinned and reachable from your HTML with no backend: shared data everyone reads, a private per-user silo isolated by email, a shared collection any signed-in person can post to and read, and a write-only store for form captures that only an admin reads back.

Yes. Each glow has three roles: a viewer reads and can submit, a member also writes the shared data, and an admin manages submissions and moderates posts. Alongside each person’s private silo, there is a shared collection any signed-in user can post to and everyone can read, editable only by its author or an admin. That covers comment walls, team boards, and community posts, with no backend.

Those are build pipelines that host files. You still wire up your own auth and backend, and there’s no saved data. Backlit hosts a finished HTML app, one page or several, with sign-in and storage already attached, and your assistant sets it up for you. No build step. Those platforms give you more to configure, and that flexibility is work you do yourself. Backlit gives you less to run.

Almost never. Building the app with AI and running AI inside the finished app are two different things. Backlit hosts the result of the first and stays out of the second: nothing AI runs in the live app, which is what keeps it fast, private, and $2.50/month. You build with AI; Backlit hosts it.

Each app gets its own storage and each user their own silo. Data is pinned to a region you choose, Australia or the US, and never replicated across regions.

HTML apps with sign-in and saved data, one page or several. On the personal side, people build wedding games with a digital guest book, personalised birthday games, quizzes for a couple or the family, and shared habit trackers. For work, it’s client spreadsheets turned into real apps, team noticeboards, price lists and event schedules, and sign-up forms that collect responses. Extra pages are fine, and they all share the same sign-in and data. What sits outside it is apps that need their own server, a relational database, or AI running at runtime.

That is still Backlit. A glow can be several HTML pages that share one sign-in and one data store, so a second or third page does not mean adding a backend or a build step. The line Backlit does not cross is a custom server or a relational database, not the number of pages.

It is once the access layer is handled, which is exactly the part fast-built apps get wrong. Backlit provides real sign-in, an allowlist, per-user data isolation, and private-by-default access, so authentication and access control live in the platform instead of being hand-rolled in your app.

Yes. Your app’s data is reachable through Backlit’s MCP, so you can query or export it straight from Claude in plain language: summarise this week’s submissions, export the orders to a spreadsheet, or push new signups into Notion.

No. You own the HTML and can host it anywhere. Your data is reachable through the MCP, so you can query or export it at any time. If you ever move on, you take both the app and its data with you.