Supported stacks

Deno hosting
on Shipped.

Deploy your Deno service with its runtime choices intact. Give it a domain, connect its data, and ship updates from your agent.

Deploy your Deno application as a service

Package the Deno runtime and the application entry point in a container, then run it as a web service. Keep the dependency and configuration files that make the project reproducible. Shipped handles starting the service and routing visitors to the address your application listens on.

Make permissions deliberate

Deno runtime permissions control what an application can access. Grant the network, environment, and file access your production code actually needs. Supply connection strings and tokens through Shipped secrets, then check that the runtime permissions allow the application to read and use those specific settings.

Connect APIs, jobs, and application data

Use Deno for an HTTP API, a scheduled integration, or a worker that processes app events. Connect PostgreSQL or object storage where data must outlive a process. Separate environments let you test permissions and external integrations before deploying the same workflow with production credentials.

A little more detail

Questions about Deno?

Do I have to use a Deno-specific hosting service?

No. A Deno application can run as a regular server process in a suitable container. Include the runtime and start command the app needs and deploy it as a Shipped web service or worker.

Where do Deno permissions belong?

Declare the required permissions in your production command or runtime configuration. Environment values supplied by Shipped do not override Deno permission checks.

From your workspace to the web

Ready to ship your app?

Start shipping