What is GoLive?
GoLive is an open-source Agent Skill plus a zero-dependency Node CLI for the step after an agent has built an app: putting it on real infrastructure. It detects what the app needs, writes a plan, waits for approval, applies it with your own provider logins, verifies what it can observe, records what it created and can tear it down again.
The alpha has live-tested journeys for hosting (Vercel, Netlify), databases (Supabase, Neon), DNS (Porkbun, GoDaddy), email (Resend), test-mode Stripe payments and Supabase auth. Other providers get a guided flow. It installs through npx skills add or the golive npm package and has been checked with Codex and Claude Code.
The repo is MIT, by a single developer, created in September 2026, with about 1,347 stars. The latest release is 0.1.0-alpha.9 (11 October 2026). The repo's listed homepage is trytofu.ai, a separate hosted service with paid plans; GoLive itself needs no account.
Is GoLive worth it?
GoLive is worth reading for its design even before using it. Nothing writes to a provider without a plan you have seen: apply refuses without the plan's id and --yes, and re-checks the plan before writing, so a changed config invalidates an old approval. DNS changes need --confirm-dns, deletions --confirm-destroy, and anything live, including a project's first production deploy, --confirm-live. A run stops at the first failed check rather than pushing on.
It is unusually candid about where those guards end. The flags are arguments the agent passes for you, and an agent already logged in to Vercel or Supabase can write there without any GoLive plan. Credentials are stored in plaintext at mode 0600 outside the repo, not in a keychain. Rollback is narrow, opt-in, and only re-points Netlify at a deployment GoLive itself recorded; the README says promotion and rollback are mock-covered, not live-validated.
Teardown is the part most deploy tools skip. golive teardown removes only resources it can prove it created, re-reads the zone and host afterwards, and lists what it could not remove, such as Supabase and Neon projects and the Resend domain, as a manual handoff. A drift check, golive status, compares current state with the recorded baseline on demand.
The limit is coverage. Six journeys are live-tested; the wider checklist is described as direction, not shipped work. With 92 commits from one author and an alpha version string, it suits a solo builder shipping a side project on Vercel and Supabase more than a team with an existing deployment pipeline.
Where it earns its place
A designer who built a booking app with Claude Code
Put it on a real domain with a database and email
Ask the agent to use the golive skill; it plans Vercel hosting, a Supabase database, Porkbun DNS and Resend email, then waits for approval. GoLive is free; Vercel, Supabase and the domain bill as usual.
An indie developer testing a paid SaaS idea
Wire up Stripe and auth without leaving test mode
Run the payments and Supabase auth journeys in test mode, then use golive teardown when the experiment ends and follow the handoff list for the projects it cannot delete.
A small agency handing a site to a client
Record what was provisioned and hand it over
Use the ownership document and golive handoff to give the client a list of resources and accounts, and run golive status later to spot drift.
Before you commit
- Setup
- Node 20+, Git and a skill-capable agent; npx skills add https://github.com/mikehasa/golive-skill --skill golive --global, or npx golive@alpha install. Checked with Codex and Claude Code; other clients unverified.
- Integrations
- Live-tested: Vercel, Netlify, Supabase, Neon, Porkbun, GoDaddy, Resend, Stripe test mode and Supabase auth. Other providers get a guided flow using their official tools and docs.
- Data and privacy
- No GoLive account, backend or product telemetry. Credentials are read in-process and never printed, stored in plaintext at mode 0600 outside the repo. MIT licence.
- Cost at scale
- No GoLive fee. Costs are your providers' own plans; GoLive does not change them.
- Limits
- Alpha; six journeys live-tested; rollback only on Netlify and not live-validated; Vercel has no read of what production serves; Supabase and Neon projects must be deleted by hand.
What’s good
- Plan, approve, apply, verify, with separate flags for DNS, deletes and live changes
- Teardown removes only what it created and lists leftovers
- Uses your own provider accounts; no telemetry
- States clearly what is live-tested versus mock-covered
What’s not
- Alpha, single maintainer
- Only six provider journeys live-tested
- Credentials stored in plaintext (mode 0600)
- Rollback only on Netlify and not live-validated
Best for
Solo builders whose coding agent made an app on a common stack and who want it live on their own Vercel or Netlify, Supabase or Neon and domain accounts.
GoLive alternatives
GoLive: common questions
- Is GoLive worth it?
- A deploy skill with unusually careful guard rails, still an alpha with one author and only a handful of providers tested live. We rate it 3.6 out of 5.
- How much does GoLive cost?
- Free and open source (MIT). Hosting, database, domain and email costs are billed by your own providers.
- What are the downsides of GoLive?
- Alpha, single maintainer; only six provider journeys live-tested; credentials stored in plaintext (mode 0600); rollback only on Netlify and not live-validated.
- Who is GoLive best for?
- Solo builders whose coding agent made an app on a common stack and who want it live on their own Vercel or Netlify, Supabase or Neon and domain accounts.
- How much does GoLive cost for a team or in production?
- No GoLive fee. Costs are your providers' own plans; GoLive does not change them.
- Is GoLive safe for company data?
- No GoLive account, backend or product telemetry. Credentials are read in-process and never printed, stored in plaintext at mode 0600 outside the repo. MIT licence.
- What are the best GoLive alternatives?
- The closest alternatives we have reviewed are InsForge, Agent Skills (Addy Osmani) and Superpowers.
Answers checked Oct 31, 2026.