Five sections.
Everything you need to ship.

Hit /sites and either fork a marketplace template or paste a GitHub URL into the import field. The first edit lands on a preview build inside 15 seconds; the second commits back to your repo with an attribution line citing the operator who edited.

You don't need a credit card to start. Free tier is BYOK on your own keys, capped at 50 vibe-edits / day and 5 published sites. See /pricing for the capability matrix.

Three load-bearing questions answered in full on the pricing page and the SLA: (1) BYOK means model calls hit your provider account directly, we never proxy. (2) Mid-cycle upgrades prorate immediately; downgrades take effect at cycle end. (3) Service credits auto-apply to next cycle's MRR when monthly uptime misses the contracted target.

The 14-day Pro/Team refund window is no-questions. After that, we credit for billing errors and SLA misses but never claw back usage you already had.

From /account → Integrations, click Install GitHub App. You'll be taken to GitHub's authorization screen — grant access to either all repositories or a selection. The callback returns you to the platform with the installation ID stamped to your operator profile.

Once installed, any site you import from one of those repos commits edits back as the Experience Platform bot, with the human operator name on the commit body. Push protection rules and required reviews are respected — the bot opens PRs when direct push is disallowed.

Coming soon: per-repo install scoping, multi-org switching, and fine-grained permission downgrade.

BYOK is the default on every tier. Drop your Anthropic, OpenAI, OpenRouter, or AI Gateway key into /byok and the platform's agent uses it for every model call on your account. Cost lands on your provider invoice, audit lands in your provider log.

Keys are encrypted at rest (Supabase column-level), never written to logs, and never shared across tenants. Rotating a key takes effect on the next request — there's no cache warmup.

Coming soon: per-project key scoping, key-health dashboard, and shared team keys on Enterprise.

Custom domains are configured per-site from the publish drawer. Add a CNAME record pointing to cname.magicbornstudios.com and the platform issues a TLS certificate (via Vercel) within ~30 seconds. Apex domains use the A-record form documented in the publish drawer once you start the flow.

Coming soon: full DNS walkthrough with screenshots for the top registrars (Namecheap, Cloudflare, GoDaddy, Route 53), wildcard subdomain handling, and the Enterprise vanity-CA flow.