Terms

The deal, in plain words

These terms cover your use of LaunchFlag at launchflag.dev, the SDK, and the MCP server. Using any of them means you accept what is below. Last updated 7 September 2026.

Your account

You need an account to create flags. Keep your keys and sign-in to yourself: anything done with your keys counts as done by you. Tell us at contact@launchflag.dev if a key leaks and we will help you rotate it. You must be old enough to enter a contract where you live, and you are responsible for anyone you invite into your project.

What you can build with it

Anything legal. Ship features dark, roll them out, turn them off. Use it in production, in a commercial product, for a client.

What you cannot do: resell LaunchFlag as your own feature-flag service, attack the API or work around rate limits, or use the service to break the law or someone else's rights. If you do, we can suspend the account, and we will tell you why.

Plans and price

Free costs nothing and stays free: one project, one person, two environments, and three days of audit history. Pro is $12 a month or $115 a year. Launch is $29 a month or $278 a year and gives you three projects. Every paid plan has unlimited seats, so the price does not move when your team grows.

The trial runs 14 days with no card. When it ends you drop to Free rather than getting locked out. Your flags keep serving either way. Prices can change, but not on a plan you are already paying for without a month of notice by email.

Billing and cancellation

Dodo Payments is the merchant of record. They take the payment, issue the invoice, and handle tax, so your contract for the transaction is with them and the card never touches our servers. Plans renew automatically until you cancel.

Cancel whenever you like, from the Billing tab. There is no refund and no proration: cancelling stops the next charge, it does not claw back the current one. You keep the paid plan until the end of the period you already paid for. Where your local consumer law gives you a refund right, that law applies.

Uptime

We do not promise an uptime percentage, and we would rather say so than print a number we have not earned yet. Live checks are on the status page.

This matters less than it usually would. Flags are evaluated inside your own process against config the SDK already holds, so if LaunchFlag goes down your app keeps serving the last configuration it fetched. An outage here stops you changing a flag. It does not take your app down.

Who owns what

Your flags, your config, your code, and your users' data are yours. We store and process them to run the service, and nothing else. See the privacy page for what that means in detail.

LaunchFlag itself, the name and the site, stay ours. The SDK and MCP packages on npm are covered by their own licence in the repository.

Ending it

Delete your project whenever you want and its data goes with it. We can close an account for the reasons under “What you can build with it”, or if a payment fails and stays unpaid. If we ever shut LaunchFlag down we will give you 30 days' notice by email, and your flags stay readable over the API for that whole window so you can take them with you.

Liability

LaunchFlag is provided as it is. We do not warrant it will be uninterrupted or error free. If we are liable to you for something, our total liability is capped at what you paid us in the 12 months before it happened, and we are not liable for lost profits or lost data. Some places do not allow that cap, so where the law says otherwise, the law wins.

Flags decide what your code does. Test the branch you are turning on, the same as any other change you ship.

Changes

We can update these terms. If a change actually affects you we will email you at least 30 days before it takes effect, and the date at the top will change. Carrying on using LaunchFlag after that means you accept the new version.

Contact

Questions about any of this? Email contact@launchflag.dev.