All features

Deploy

Build location & caching

Choose where supported deployments build, reuse project caches and ship the result to its runtime. Your production server does not have to be your build machine.

Open the guide

How it works

For supported server deployments, build on the OpenShip controller or the destination. The controller can be an always-on server or your optional desktop app. Local source upload, Git clone location and build location are separate choices.

Warm project caches reuse dependency and framework work. Storage-aware cleanup reclaims idle caches while protecting active deployments and retained rollback artifacts. Available build paths depend on the workload and destination.

What you can do

  • Build where it fits

    Use controller-side builds to keep compilation off a small target server.

  • Warm caches

    Reuse dependency, framework and Docker build work across releases.

  • Storage-aware cleanup

    Reclaim idle cache space without treating running workloads as disposable.

Put it to work.

Start on OpenShip Cloud or deploy on your own infrastructure.