A neon launch-control lounge with a martini glass, olive toothpick, and launch schedule on the table.
Pre-launch platform · Mildly NSFW

Now you are
the master.

The pre-launch platform that gets your beta out—and tells you when it’s ready to go all the way.

Get on the key waitlistExplore the API
We put out. You go live. ✦ We put out. You go live. ✦ We put out. You go live. ✦ We put out. You go live. ✦
For the before-times

The product you wish your boss let you use at your day job.

Master Beta is the short-lived control room between “we’re building it” and “we’re shipping it.” Alpha signups, waitlists, feedback, invite waves, and one very honest answer to: are we ready?

Turnstile protectedCORS-first APITiny hosted databaseCSV handoff
Your place or mine?

Come a little closer.

Some products need more than a global “on.” Master Beta lets them ask whether a ZIP can use a feature, open the real local experience where it is ready, and offer a clear invitation where it is not.

ZIP-based accessHonest “not here yet”Aggregate launch interest

EventFed uses this to open a local calendar without redeploying the whole product. The calendar owns its content and experience; Master Beta simply knows when that place is ready.

Weekly launch readiness email

What’s stopping you?

●●●

STORYLORE · WEEK 06

Your beta is close. Here’s what needs your attention before launch.

HOLD — 3 BLOCKERS

WHAT’S BLOCKING LAUNCH

  • Engagement: 39% activation; target is 45%.
  • Features: 2 launch-critical features still need to ship.
  • Reliability: 1 open bug blocks the core writing flow.
39%activation · need 45%
2features left to build
1launch-blocking bug
61active beta testers

Next move: Invite 20 more qualified testers after the writing-flow bug is fixed. We’ll check back next week.

One endpoint

It’s not hard.

Unless you want it to be. Put a protected alpha form on your site in a few lines, then let Master Beta keep the receipts.

Open the REST playground
POST https://masterbeta.dev/v1/submit

{
  "siteKey": "mb_pub_...",
  "form": "alpha",
  "email": "ada@example.com",
  "turnstileToken": "..."
}

201 { "status": "waitlisted" }
When the moment comes

All green.
Go make it official, Tiger.

Export the evidence, hand the right people to production, and retire the beta. A good pre-launch platform knows when to leave.

Request a keyMeet the API

You’ve spent your life trying to get in. Master Beta is for getting out… of beta. Obviously.

Keys open in waves

Come a little closer to launch.

Tell us what you are preparing to launch. We will invite a small number of teams as capacity opens, with preference for people willing to shape the product with us.

The signup widget

Paste it. Let it ask.

One email field begins the signup. Master Beta fetches any configured questions, then opens a short follow-up popup after the email is accepted.

What needs to be set up first?
  1. Create a Cloudflare Turnstile widget for the exact production hostname and copy its public site key into data-turnstile-key.
  2. Ask Master Beta to provision your site and form. You will receive a browser-safe mb_pub_… site key and choose the form slug.
  3. Give Master Beta the exact HTTPS origin where the widget will run, for example https://example.com. Browser requests are allowed only from that origin.
  4. Add the form, honeypot, Turnstile mount, and script below. Master Beta handles the consent-aware follow-up questions and server-side Turnstile verification.
<form class="master-beta-form" data-site-key="mb_pub_…" data-turnstile-key="0x4AAAA…" data-source-site="yourdomain.com">
  <label>Email <input name="email" type="email" required></label>
  <label class="mb-honeypot">Leave blank <input name="website" tabindex="-1" autocomplete="off"></label>
  <div data-turnstile></div>
  <button type="submit">Sign up for beta</button>
  <p data-status role="status" aria-live="polite"></p>
</form>
<script src="https://masterbeta.dev/v1/widget.js" defer></script>