Publishing & shipping
Put a build in front of people — on us, on your own server, or in an app store.
Three ways to go live
| Route | Best for | What you need |
|---|---|---|
| Publish | Getting something in front of people immediately | Nothing — you get an address on our domain |
| Deploy | Running it on a domain and server you own | Your own server and SFTP details |
| Ship to store | Apps, games and extensions people install | Your own developer account for that store |
Publish
The fastest route: press Publish on a finished build and it gets a public address on our domain. Use it to show someone, to test demand, or as the home for something small. Republishing updates it in place, and the publish history lets you roll back.
Deploy to your own server
Deploy copies the built files to a server you control, over SFTP. You save the destination once per domain — host, user, credentials and the path to write into — and afterwards deploying is one click.
Every deploy keeps the previous version on your host, so you can put it back if a release goes wrong. The history is listed per domain, with a one-click restore.
Shipping to app stores
You ship with your own developer account, so the listing belongs to you and the revenue goes to you. Save each store's credentials once in Settings → App stores, then use Ship on a finished build.
| Store | For | What it needs |
|---|---|---|
| Google Play | Android apps and games | A service-account key with release and store-presence permission |
| Chrome Web Store | Browser extensions | Either the classic OAuth trio or a service account with your publisher id |
| Firefox Add-ons | Browser extensions | An API key pair |
| Microsoft Store | Windows apps | Partner Center credentials, entered in the Ship dialog |
| itch.io | Games | An API key and your username — create the game page first |
| Steam | Games | Your Steamworks login and app id |
Where a store's API allows it, the listing text, screenshots and privacy page are prepared and pushed for you. Some steps are gated by the stores themselves and can only be done by you in their console — creating the app record, declaring app content, and the first rollout.
Digital goods inside store apps
If your app sells digital goods, store policy requires the store's own billing, so Stripe is deliberately not built into store apps. Payments through Stripe are for the web.