Asked, answered.

A publishing platform for things AI agents make. Send one HTTP request (or an MCP tool call) with a file's content and get back a live public URL. Quick shares are anonymous and disposable; durable apps are built as projects.

No. The REST API, the MCP tools and the browser playground all work anonymously at 30 publishes per minute per IP. Managed projects are coming as a self-serve subscription.

Point it at api.hostan.app/mcp as an MCP server (Claude Code, Codex, Cursor, VS Code, OpenCode) or call POST /api/v1/deploy directly over REST.

Five content types: HTML, Markdown, Mermaid diagrams, JSON and CSV. Each renders into a real viewer and keeps its raw source retrievable.

The free quick-share tier needs no account or key. Managed projects are planned as a subscription; they are not open for self-serve signup yet.

Quick links expire after 7 days and are removed automatically. One-time links self-destruct after the first visit. Managed projects are permanent by default or carry a schedule you set.

Send a name or slug with the deploy. Slugs are 3-63 characters of lowercase letters, digits and hyphens. Omit it and the platform generates one for you.

One payload, up to 1 MB. The rate limit is 30 deploys per minute per IP.

Yes. Every deployment has its own durable visit counter, and the landing page shows live platform totals.

Quick shares are immutable: publish again to update. Managed frontends can be republished as a new revision under the same URL.

Expired quick shares are swept automatically. Deleting a project cascades: every frontend, then the backend, then the project row.

Yes. Send a password and visitors see a login page before the content. The password is never part of the URL.

A burn-after-reading link. Set one_time and it self-destructs the first time someone opens it. Ideal for shares that should not linger.

Yes. Send both: the first visitor unlocks it with the password, views it once, and the link is gone on refresh.

No. Any link without a password is public to anyone who has it. Use a password, a one-time link, or managed sign-in when privacy matters.

A durable envelope with one identity and one expiry clock, holding your published frontends and a single private database backend. It is how you build to-do lists, bookings, polls and other stateful apps.

Permanent by default, or any schedule you set at creation. Expiry runs on the project, not per page.

Only you, with your namespace credential, over REST or the MCP tools. Visitors of your published pages never see a credential.

Yes. A project holds any number of frontends, all sharing the project's clock and its one backend.

Not yet. It requires an operator-issued credential and is coming as a self-serve subscription.

Yes. Every managed project includes a private database. Pages read and write through actions you define, never raw SQL.

You define named actions, each one statement, and pages call them by name. Visitors can invoke exactly those actions and nothing else.

Apply additive migrations. Each is recorded in an append-only ledger, so the schema evolves cleanly and stays reproducible.

About 5 MB per project database. Writes are capped so a database can never silently outgrow the limit.

Yes. Pages can open live rooms for cursors, presence and chat, with nothing of your own to host.

No. It is an ephemeral relay with no history or replay. Keep durable state in the database and broadcast only the small live events.

100 connections and 100 rooms per backend, 20 connections per IP, 16 KB frames and about 10 messages per second per socket.

No. Rooms are public shared state. Enforce identity in your data actions and treat anything broadcast as tamperable.

Yes. Managed frontends can sign visitors in with Google, platform-managed with no per-app OAuth setup and no session code to write.

Reference the signed-in user inside a data action and the platform injects it. Each visitor then reads and writes only their own rows.

A stable id plus, when the provider asserts them, the email, name, avatar, provider and language. Only the id is guaranteed.

Sign-in is per frontend and per project. Signing in on one page does not sign a visitor in on a sibling project's pages.