Managed Hosting
Your whole sp00ky stack, deployed by one command. Database, scheduler, sync layer, backends, frontend. No Docker Compose, no Kubernetes, no tears.
Production hosting is where most side projects quietly die. You stand up a database, you wire up a worker, you figure out TLS, you forget the migration, you spend an evening on DNS. A week later you are still polishing the YAML. sp00ky Cloud skips the whole montage.
One file. One command. Everything your app needs, running for real.
One command, entire stack
spky cloud deploy reads your sp00ky.yml, builds your
backends, uploads the images, provisions the database and sync layer, runs your
migrations, starts your frontend, and wires up TLS. You watch the steps tick past.
Then you open your domain. It works.
Your backends can be written in anything that speaks HTTP, because we ship Docker images, not a proprietary runtime. Your frontend is whatever you want, served from the same project.
Scale with a flag
More traffic showed up? spky cloud scale --ssp 3. That is the ritual.
The sync layer grows horizontally, the rest stays put. Set a default in
sp00ky.yml and you will not have to think about it again.
Logs you actually want to read
spky cloud logs tails everything live. Filter by service, stack two
services in a split view, grep with a real regex on the server, or open an
interactive TUI with scroll, search, and a follow toggle. It feels like the logging
tool you always meant to build.
Drop a live status badge on your README while you are there. It is one markdown line.
Deploys that behave
Log in once with GitHub. For pipelines, generate an API key and point CI at it. Link
a GitHub repo with spky cloud link and pushes become deploys. Your
database gets backed up automatically, and you can roll the scheduler or the full
infra with a flag when a new version of sp00ky drops.
How it stacks up
sp00ky Cloud is a focused platform for sp00ky apps, not a general PaaS. Here is the honest picture against the usual names.
| What you want to do | sp00ky | Fly.io | Railway | Render | Vercel |
|---|---|---|---|---|---|
| Deploy db, sync layer, backends, frontend in one command | ✓ | ~ | ~ | ~ | ✕ |
| Run migrations automatically on every deploy | ✓ | ✕ | ✕ | ✕ | ✕ |
| Scale the sync layer with a single flag | ✓ | ~ | ~ | ~ | ✕ |
| Tail logs with regex, filters, and a TUI browser | ✓ | ✓ | ~ | ~ | ~ |
| Host apps built on any framework or language | ✕ | ✓ | ✓ | ✓ | ~ |
| Global edge, multi region out of the box | ✕ | ✓ | ~ | ~ | ✓ |
| Full autoscaling compute | ✕ | ✓ | ✓ | ✓ | ✓ |
| ✓ first class · ~ possible, with effort or caveats · ✕ not a goal | |||||
When to pick something else
If your app is not a sp00ky app, pick a general PaaS. Fly.io is excellent for global edge and autoscaling. Railway and Render are friendly Docker first platforms for any stack. Vercel is still the right answer for pure frontend and serverless workloads.
sp00ky Cloud is the right call when the thing you are shipping is a sp00ky project and you want the database, sync layer, scheduler, backend, and frontend to come up together, with migrations already applied, on a domain that already has TLS. For anything else, deploy where you like. We will not be offended.
Ready to build something amazing?
Full docs, install guide, and API reference — all in one place.
Read the docs