Deno hosting that runs your TypeScript exactly as you wrote it
Push your Deno source and Velixir builds it into a container image server-side, with no Dockerfile, no deno compile step, and no local Docker required. It runs on managed Kubernetes in the EU with autoscaling, zero-downtime rolling deploys, and one-click rollback.
Why deploy Deno on velixir
- Push TypeScript, run TypeScript. Velixir detects your deno.json, honors your version and deno task scripts, and builds everything server-side. There is no Dockerfile to write and no local build step to babysit.
- Fresh, Oak, and Hono deploy the same way. Islands-based SSR, long-lived WebSocket APIs, and background workers all run on managed Kubernetes with real autoscaling, not a constrained edge sandbox with cold starts and execution limits.
- Your npm: and jsr: imports just work. The build resolves remote URL, JSR, and npm specifiers during the server-side build, so you keep Deno's module graph instead of being locked into one vendor's proprietary runtime.
- Managed Postgres and Valkey billed hourly in EUR, with EU data residency and unmetered bandwidth (no egress fees). It is the database-next-to-your-app setup that edge-only Deno hosts and Deno KV cannot give you.
Works with your stack
Popular Deno frameworks and runtimes deploy as-is, no adapters.
Runtime versions
Pick your version and we pin the exact runtime for every build.
From Deno source to production in three steps
Push your source
Git push, velixir deploy, a dashboard upload, or a connected GitHub repo. No Dockerfile.
We build it server-side
Velixir detects Deno, installs dependencies, and builds a container image on our infrastructure.
It goes live
Managed Kubernetes runs it with autoscaling, zero-downtime rolling deploys, and one-click rollback.
Deno hosting FAQ
Which Deno versions does Velixir support?
Velixir runs the latest Deno and detects the version from your deno.json, so modern TypeScript and JavaScript work out of the box with no runtime flags to configure. Because the build reads your deno.json (and deno.lock), your tasks, imports, and compiler options are honored exactly as they run locally.
Do I need a Dockerfile or a deno compile step to deploy?
No. You push source (git push, the velixir CLI, a dashboard upload, or a connected GitHub repo) and Velixir builds it into a container image server-side, then pushes it to a private registry and runs it on managed Kubernetes. There is no Dockerfile, no build configuration, and no local Docker to install.
Can I deploy Fresh, Oak, or Hono apps?
Yes. Fresh islands and SSR, Oak and Hono HTTP servers, and WebSocket endpoints all deploy through the same pipeline every language uses. Your app just needs to listen on the port Velixir provides, and it gets autoscaling, zero-downtime rolling deploys, and instant one-click rollback.
I use Deno KV or need a real database. What are my options?
Velixir includes managed Postgres and Valkey (Redis-compatible), billed hourly in EUR and provisioned right next to your app in EU Central or NA East. For teams moving off Deno KV or edge-only hosting, that means a durable SQL database and cache with EU data residency, connected over your private network rather than a proprietary edge store.
Deploy your Deno app in under two minutes
Push your code and Velixir builds, publishes, and deploys it to the region you pick, EU Central or NA East, with managed Postgres and Valkey a click away. No Docker, no YAML, and your first month's on us, up to €14.99.
No credit card to sign up. Add a payment method only when you're ready to deploy.