Your licenses, your Stripe, your data. We bring the stats and the updates.

Not yet, and we're not giving anyone access for now: there's only a waitlist. Join it and we'll let you know when the beta opens. The licensing system exists and Color Vivo uses it for its apps, but it still has to be made generic for third parties, and the installer, the central service and the English docs are still to come. There's no date: it depends on how many people sign up. The private beta would be with a few makers, free of charge, in exchange for your feedback.

No. Emails, IPs, devices and keys live in your Worker, in your account. The central service only receives the version, daily counts and health status. That's the core rule of the design.

Not us: 0% commission from us. Stripe charges you its fees directly. With Managed Payments (Stripe is the merchant of record and handles VAT), about 3.5% on top of the standard fee: roughly 5% + €0.25 in total for European cards. Without Managed Payments, only the standard fee (about 1.5% + €0.25) and you handle tax. Fees are indicative as of Oct 22, 2026.

Not in fees: charging through Managed Payments costs the same as a MoR or a bit more. What changes is who owns the customers and the payment account: here they're yours and you can leave whenever you want.

There will be a free tier: what runs in your Worker has no artificial limits. The central service will have paid plans; we'll publish prices before the beta opens. What won't change: 0% commission from us on sales.

Your customers notice nothing: the Worker keeps selling, activating and renewing. After a 30-day grace period you lose stats, alerts and new releases, and you'll see a banner in the admin. Security patches keep coming.

Your Worker doesn't depend on it to sell or validate. Without a connection to the central service nothing happens for 30 days; after that, you'll just see a notice in the admin.

That's the plan: with regular Checkout you only pay Stripe's standard fee and you handle tax (with or without Stripe Tax). Today the system uses Managed Payments, and regular mode is part of the remaining work.

Inside the stores, their rules require in-app purchase to unlock digital content, with exceptions in some countries. It works for the version you sell outside the store, or to unlock on desktop what was bought on your website.

On activation, your app gets a token signed with Ed25519. It ships with the public key and checks the token without a network connection; subscriptions expire with the token and renew in the background. The app never waits for the network to start.

Any: activating, renewing and validating is an HTTP API. SDKs would come first for C# and Swift, then JS/TS, Python, Kotlin/Java, PHP, Go and Rust/C++.

A little. You'll need Cloudflare and Stripe accounts, run the installer and integrate the SDK or the API into your product. The goal is for a maker to be selling within an hour without asking for help.

It runs in your account and you pay Cloudflare directly. The Workers free plan, which includes D1, is usually enough to start; if you grow, the Workers paid plan starts at $5 a month.

It's one of the ideas: an importer that runs in your Worker, reads your keys with your provider token and keeps them valid. It doesn't exist yet; if you need it, tell us in the form.

Because we want you to be able to read and change the code, but not let someone resell it as a service or remove the license check. ELv2 covers exactly that.

First we send you a link to confirm it; if you don't confirm within 30 days, we delete the sign-up. After that we only use it to tell you about the beta and the launch. We don't share it with anyone, and every email includes an unsubscribe link that deletes your data. Details in the privacy policy.