The developer experience you already love — Git deploys, rollback, previews, managed databases, and logs and metrics — on a cloud you can self-host.
Push to deploy. Framework detection covers Next.js, Vite, SvelteKit and more; a monorepo with several apps needs a root directory.
Every build is an immutable, content-addressed deployment. Nothing mutates in place, and you can delete a deployment you no longer need.
Promote any earlier deployment back to production to recover from a bad release.
Every pull request on a connected GitHub repository gets its own live URL, so you can review real running code before you merge.
Bring your own domain with managed DNS and automatic TLS. Wildcard subdomains for previews come standard.
Per-environment variables, scoped to build, runtime or both. Sensitive values are encrypted at rest.
Production stays warm and previews scale to zero when idle, with no servers to manage.
Ship anything with a Dockerfile. Long-running services and custom runtimes deploy alongside your functions.
Managed Postgres, Redis and SQLite databases for your projects. Each database runs on a single host node.
Schedule jobs with cron and run multi-step workflows, with a console to inspect, cancel and replay runs. Each cron job runs on a single node.
Request logs and metrics for your deployments, polled from the dashboard. See requests, errors and cold-start timings.
Experimental. Team members unlock protected previews with a linkable ring-signature proof: the serving node learns that some member signed, not which one.
Requests reach the node that runs your deployment: platform DNS favours it, and a request that lands on another node is forwarded. If the coordinating node is lost, a standby takes over.
Connect a repository and push. shadw detects supported frameworks, builds an immutable deployment, and serves it — no servers to provision.
Get the deploy experience you love on a cloud you can self-host. The hosted service uses Clerk, Stripe and Vercel DNS.