# Static sites & background workers

URL: https://openship.io/features/static-sites-workers

Give each workload the runtime it needs.

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

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.

## 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.

[Read the guide](https://openship.io/docs/architecture/runtime-model)
