All features

Deploy

Static sites & background workers

Serve built static files directly at the edge, run web applications, or deploy background workers that do not need a public HTTP port.

Open the guide

How it works

On supported self-hosted paths, OpenShip extracts a static build into a retained release and serves it as files. A Docker build does not require keeping an application container running after publication. Cloud offers its supported static-hosting destinations.

Workers follow the deployment pipeline without requiring a web route. Choose containers or a supported host process, then use logs, health and resource settings for the selected runtime.

What you can do

  • Static-file delivery

    Publish assets without a persistent application process on supported targets.

  • Portless workers

    Run queue consumers and other long-lived background jobs.

  • Runtime choice

    Use containers or supervised host processes where the destination supports them.

Put it to work.

Start on OpenShip Cloud or deploy on your own infrastructure.