Deploy overview
What it is, what it isn't, where it fits.
Deploy is our PaaS — think Vercel/Railway/Render. Push code, we build it, run it in a container, give you a URL. Custom domains, TLS, env vars, attached databases — the works.
What it does
- Builds from a Git repo — push to GitHub, deploy fires automatically.
- Detects the framework — Next.js, Astro, SvelteKit, Vite, Express, Django, FastAPI, Flask, Rails, etc. Sets the right build + start commands.
- Runs in a container — isolated, with CPU/RAM caps per tier.
- Routes via Traefik — auto subdomain (
<slug>.apps.suzko.net), custom domains with auto-TLS. - Attaches services — provision a managed Postgres, Redis, MySQL, MongoDB, RabbitMQ etc. in one click; connection string injected as an env var.
What it isn't
- Not bare-metal hosting — no SSH into the container, no custom kernel. Use VPS if you need root.
- Not for static sites that don't need a runtime — Web Hosting is cheaper for that. Deploy is for actual processes (server, API, worker).
- Not Kubernetes — we run containers, not pods. Each project is one runtime by default, scale-out coming.
Pricing tiers
- Free tier — for demos. One project, low resources, auto-cleans in 24h.
- Hobby — $5/mo, persistent project, modest resources.
- Pro / Team — usage-based on container hours + memory-GB-hours.
Live usage at /tools/deploy/usage. You can cap monthly spend in settings.
Getting started
Quick start walks through the GitHub → URL path in 3 minutes.