Soft launch: what it means, soft launch vs hard launch, and how to run one

Cambridge Dictionary labels soft launch a business term and defines it as "an occasion when a product, service, or business is made available or opened for the first time, but only to a limited number of people at first." Unity's glossary, written for app and game developers, adds the marketing side: "A soft launch refers to the common strategy of releasing a product ahead of its scheduled launch with little or no marketing push." Unity describes soft launches as "usually planned as 'rehearsals' for a full launch."

So a soft launch has two parts: a limited audience, and little or no promotion. The product is real and in use. It just has not been announced to everyone yet.

The same idea goes by other names:

• Soft opening. Wikipedia's entry treats the two as one thing ("A soft launch, also known as a soft opening") and applies it to a brick and mortar business that opens before its grand opening "to test its capacity and train its staff."
• Beta, preview, early access. Software companies often use these labels for the same stage. GitHub called Copilot's a "technical preview", Google called Gmail's a "preview release", and Supercell says "soft launch" for games released in selected countries.

The dating meaning. Merriam-Webster's slang entry defines soft launch as "an act of hinting about a new romance on social media," for example a photo in which someone's hand appears with no mention of who it belongs to, and a hard launch as "an emphatic public declaration of romantic involvement." It adds that this sense "is an extension of the earlier use of soft launch, in which a business will first offer their product (such as access to a web site, or a restaurant) to a limited number of people." The rest of this post is about that earlier, business use.

Cambridge defines a hard launch as "an occasion when a new product or service is made available to the public, not just a limited number of people, in a way that is intended to attract a lot of attention." Wikipedia notes that it is also known as a "grand opening" or "full launch." The difference comes down to audience and noise: a soft launch limits both, and a hard launch wants as much of both as it can get.

Aspect	Soft launch	Hard launch
Who can get it	"only to a limited number of people at first"	"the public, not just a limited number of people"
Marketing push	Little to none	Large, upfront
Early user growth	Slow, then ramps up	Spikes, then stabilizes
Main risk	Delayed revenue and growth	Wasted spend on an unpolished product
Best for	Testing, fixing bugs, tuning before scale	Products already validated and polished

The first row quotes Cambridge Dictionary's two definitions. The other four rows come from the comparison in Unity's glossary.

Two things the table does not show:

• They are usually stages, not rivals. A soft launch is normally followed by a hard launch of the same product, which is why Unity calls it a rehearsal.
• Some products open wide on day one. When Meta announced Threads on July 5, 2023, the same post said: "We're rolling out Threads today in more than 100 countries for iOS and Android."

Unity states the trade-off plainly. Hard launches "can offer immediate revenue" but "apps with unsuccessful hard launches can exhaust marketing budgets before optimizing for ROI, user experience, or retention." The cost of a soft launch is time: growth and revenue wait while you learn.

Three reasons come up in the sources:

1. To find problems while few people are looking. Merriam-Webster describes the business soft launch as "a way of building excitement and also identifying and fixing problems before opening to the general public." Unity says a limited release "can help a company check and fix things like bugs or user reactions before a full, official launch," and that "real-world users are often the best way to identify bugs, glitches, or problem points in the experience."
2. To learn who the product is for. Unity names "user data and app performance data" as the most important parts of an app soft launch. The first shows who is actually interested.
3. To avoid betting everything on one day. In a Y Combinator Startup School talk, Kat Mañalac, who introduces herself in it as a partner at Y Combinator, says "most people think about launching as something that you get one shot at," and warns: "if you're like most startups, you will launch something, no one will care." Her advice is to treat launching "as something you can continually do": a silent launch (a simple landing page), a friends and family launch, a launch to strangers, launches in online communities, and a "request for access launch" with a waitlist.

A soft launch needs a gate: something that decides who gets in. These are the common ones, with limits from the official documentation as of October 2026.

Invites, waitlists and capped previews. People ask for access and you let them in over time. Bluesky wrote that it "used invite codes to help us manage growth while we built features like moderation tooling, custom feeds, and more" before it opened sign-ups. GitHub capped Copilot's "technical preview": "The number of spots for the technical preview is limited." In the YC talk, Mañalac describes how Magic, an on-demand personal assistant, "launched a waitlist, and they also gave people ways to skip the line."

A friendly community. In the same talk, Mañalac says companies going through Y Combinator have the option of launching on YC's internal platform before they launch publicly, which she calls "a fairly low-risk way to launch because it's not totally public, but there is enough of an audience there to get some feedback."

App store test tracks. Apple's TestFlight lets you add up to 100 internal testers from your development team and invite up to 10,000 external testers, by email or with a public link. A build can be tested for up to 90 days. Google Play has three kinds of test: internal testing (up to 100 testers), closed testing (testers you list by email address or Google Groups) and open testing, where "Anyone can join" and the test version is visible on Google Play.

Google makes a small soft launch mandatory for some developers. Personal Play Console accounts created after November 13, 2023 "must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days" before they can apply for production access.

Selected countries. Both stores let you release in some countries and not others. Apple's App Store Connect offers "Specific Countries or Regions" as an availability choice, out of the 175 countries or regions where the App Store is available, and Google Play lets you "target your release in each track to users in specific countries." Supercell's Squad Busters, below, started in eight countries.

A percentage of users, for updates only. Apple's phased release sends an update to a random sample of users with automatic updates over 7 days, starting at 1%. Google Play's staged rollouts reach "only a percentage of your users, which you can increase over time," but "can only be used for app updates, not when publishing an app for the first time." Outside the app stores, the same idea is called a canary release: "slowly rolling out the change to a small subset of users before rolling it out to the entire infrastructure," in the definition on martinfowler.com. These soft launch a new version, not a new product.

Pre-registration and pre-orders are related but different: they collect interest before anyone can use the product. Google Play pre-registration campaigns "can only last 90 days, after which you need to launch your app to production."

The table near the end of this post lines the main options up.

These are limited releases described in the companies' own announcements.

Product	Limited stage	What came next
Gmail	April 1, 2004: Google said it was "testing a preview release of Gmail" and that "a handful of users" would begin that day	July 7, 2009: Google removed the beta label, noting Gmail "has worn the beta tag more than five years"
GitHub Copilot	June 29, 2021: "technical preview" with a limited number of spots	June 21, 2022: "generally available to all developers"
Bluesky	Invite only: "For the past year, we used invite codes to help us manage growth"	February 6, 2024: "Now, we're ready for anyone to join"
Squad Busters (Supercell)	April 23, 2024 (announced April 8): soft launch on iOS and Android in Canada, Mexico, Spain, Denmark, Norway, Sweden, Finland and Singapore, following two beta tests	May 29, 2024: global launch. October 30, 2025: Supercell announced it was ending development
Everdale (Supercell)	Autumn 2020: early alpha published under a different name. August 23, 2021: announced as "now in soft launch in select regions"	October 3, 2022: Supercell announced it was ending development, with servers to be turned off on October 31

What the examples show:

• There is no standard length. Squad Busters went from its April 23 soft launch date to its May 29 global launch in about five weeks. Copilot's technical preview and Bluesky's invite period each ran about a year, and Gmail kept its beta label for more than five years.
• Limited does not have to mean tiny. GitHub reported "more than 1.2 million developers in our technical preview," and Bluesky's opening post invited readers to "Join more than three million people."
• A soft launch can end with the product being stopped. Supercell says on its new games page: "We've also killed more games than we can neatly explain on a webpage."
• A short soft launch is not a guarantee either. When Supercell ended Squad Busters, it wrote that the team had wanted to "learn directly from a global audience instead of waiting years in a limited release," and then: "What we learned was that we had got it wrong." The post does not say a longer soft launch would have changed the result.

This checklist is our own synthesis of the sources above, not an official standard.

1. Write down what you need to learn. One or two questions (does signup work end to end, do people come back, will anyone pay) and what answer would make you delay or change course.
2. Choose the gate. An invite list, a waitlist, a store test track, selected countries, or a percentage rollout for updates. Pick the smallest one that can answer your questions.
3. Start with people you know, then move on. Friends and family are a fine first step, but Mañalac's advice is to "get out of that family and friends circuit as fast as you can."
4. Make feedback one step. Google Play asks you to "Provide a feedback URL or email address to collect feedback from testers." A web app needs its own equivalent, such as a visible email address or a short form.
5. Decide what search engines should see. A soft launch on a public URL is not private. Google's documentation says that with a noindex rule it "will drop that page entirely from Google Search results," but only if the page is not blocked by robots.txt, because otherwise "the crawler will never see the noindex rule." Leave your landing page indexable if you want people to find the waitlist.
6. Watch the crashes and the inbox, and keep a record. Google's advice for staged rollouts fits any soft launch: "closely monitor crash reports and user feedback." Developers in its required closed test "must summarize your testing feedback when applying for production access."
7. Widen in steps. More invites, more countries, a larger percentage. Fix what each step exposes before the next one.
8. Set an end. Pick a date or a threshold after which you go public, change course or stop, so the limited release does not drift.
9. Remember that limited is not hidden. On Google Play, "Users receiving the staged rollout can leave public reviews," and Apple notes that apps in phased release "can be manually downloaded from the App Store by anyone at any time." Limited is quieter, not invisible.

Going public is when you turn the attention on: an announcement, community posts, press if you have it, and listings.

• Community posts need a product people can use. Hacker News is the clearest case. Its Show HN guidelines say "If your work isn't ready for users to try out, please don't do a Show HN," list sign-up pages as off topic, and add "Don't post landing pages or fundraisers." A waitlist belongs to the soft launch stage, not to a Show HN. Our post on how to post a Show HN covers the rules in full.
• Listings outlast launch day. A directory listing stays up after the announcement fades, though not every listing is worth having. Our post on directory backlinks covers what Google says about them and how to check the link you actually got.
• Keep launching. Mañalac's point is that a launch is not a single day: "assuming you ship new products and new features, you are never going to be not launching."

VibeLaunch, the site publishing this post, works on the listings part. Its homepage describes the service as verified directory submissions for new products.

What we could not verify. No source we read gives a standard length for a soft launch; the examples above run from about five weeks (Squad Busters) to a beta label kept for more than five years (Gmail). We found no primary source comparing how often soft launched and hard launched products succeed, so this post gives no success rates. We left out examples where we could not read the company's own announcement on October 5, 2026. We could not confirm the date of Kat Mañalac's talk or her current role from Y Combinator's site, and the companies she names may work differently now. Apple's and Google's limits change, so check the linked pages before you plan around a number.

How this post was put together. We did not run a soft launch for this article. On October 5, 2026 we read the dictionary entries, Unity's glossary, Apple's and Google's developer documentation, the talk transcript on Y Combinator's site, and the companies' own announcements. Every quote comes from a page in the source list below.