Smallware
Push to GitHub. It's live.
Smallware runs the same binary you run locally. Connect a repo and every push deploys. Resize machines, add replicas, expand regions, bring your domain, and turn on SSO from one dashboard.
deploy
$ pylon deploy --target cloud ✓ Build · 12s ✓ Schema synced ✓ Cutover · 0 errors → https://acme.smallware.run- Connect GitHub and every push to main deploys; PRs get preview environments
- Or run pylon deploy for air-gapped builds and CI without GitHub
- Resize RAM, add replicas, expand to US / EU / APAC / South America from the dashboard
- Custom domains + TLS, OIDC and SAML SSO, audit log, and one-click volume snapshots
How it works.
deploy
$ pylon deploy --target cloud ✓ Build · 12s ✓ Schema synced ✓ Cutover · 0 errors → https://acme.smallware.runThere's no special cloud build of your app. Smallware runs the identical runtime you run on localhost, so what passes in dev behaves in production. Connect a repo for push-to-deploy with preview environments per pull request, or cut releases manually with pylon deploy.
What you’d otherwise wire up.
Each line is a piece teams normally assemble for this one capability. On Pylon it is part of the runtime.
- A container registry and the pipeline that fills it
- Load balancers, TLS certificates, and DNS wiring
- A metrics stack to answer what request rates and errors are doing
- Preview environments stitched together out of CI steps
Build it on Pylon.
One framework for your schema, sync, auth, functions, realtime, and SSR. Free to start.