What a launch does
Each step is safe to run again, is written to a log, and can be resumed. State lives in ~/.shipyard/projects/<name>/state.json and holds names and IDs, never secrets.
- Check the domain. Is it free, and what does it cost. Nothing is bought here.
- Register the domain and point it at DNS. Shows the price and waits for you to type "buy". Then creates the DNS zone and sets the nameservers.
- Create the GitHub repo. A private repository with the Next.js starter committed to it.
- Create the hosting project. A web service, a worker if you asked for one, and Postgres.
- Connect the repo. Every push to main builds and deploys.
- Add the domain. The bare domain and www, the DNS records for both, then waits for the HTTPS certificate.
- Set up email. Adds the sending domain, writes DKIM, SPF and DMARC to DNS, waits for verification, creates a sending-only key. Forwards hello@ to your inbox if you chose that.
- Set up payments. Products, prices and a welcome coupon from your pricing config, and the webhook endpoint on your live domain. Test mode.
- Create the analytics property. A Google Analytics 4 property and web stream; stores the measurement ID.
- Verify the domain for search. A DNS record proves ownership to Google, then the sitemap is submitted.
- Create error tracking and storage. A Sentry project and its DSN; a bucket and keys limited to that bucket.
- Generate the app's secrets. A session secret and an encryption key, random, kept in your keychain.
- Write the variables. Every key and ID goes into the hosting provider as environment variables. Nothing is written to the repo.
- Health check. The site over https, the database, a test email, a test Stripe webhook. Reports what works and what does not.
- Build prompt and summary. A prompt for your coding agent, the same text as CLAUDE.md and AGENTS.md in the repo, and a one-page summary with costs and teardown.
- Launch kit. Product Hunt and directory drafts, with screenshots of your live site, under /launch in the repo.
Waiting
Nameservers, certificates and email verification take real time. Shipyard polls and tells you what it is waiting for. If a wait times out nothing is lost: run apply again and it keeps waiting from the same step.
Going live with payments
Every launch starts with Stripe in test mode. When Stripe has verified your business, add a live key and run shipyard go-live yourproject. It asks first, then creates the same products, prices and webhook in live mode and swaps the keys on your host.