shiprr.
Log in Create account

Limits

Shiprr has a few important operating limits you should plan around when sizing apps, tuning builds, and choosing deployment settings.

Runtime resource ranges#

  • Replicas — 1 to 50
  • CPU — 1,000 to 20,000 MHz per replica
  • Memory — 512 MB to 16 GB per replica

New apps start at 1,000 MHz and 512 MB per replica. That is a baseline for lighter workloads. Heavier apps usually need more room, especially when they use SSR, background processing, or larger in-memory caches.

Build limits#

  • Builder capacity — Dedicated builder capacity with 4 CPU and 10 GiB memory
  • Build timeout — 25 minutes per build
  • Included build usage — First 50 build minutes per month are free

If your build approaches the timeout, reduce install work, optimize the build pipeline, or split heavy work into smaller steps.

Regions#

Shiprr currently supports eu, us, oc, and asia. Region selection is a placement preference. The platform may fall back to another configured region when the preferred region has no capacity.

Build support#

Shiprr supports source builds from connected GitHub and GitLab repositories. Custom Dockerfiles and prebuilt container image deploys are not supported yet.

Storage limits#

App replicas do not get persistent disk. The filesystem is ephemeral and should not be used for durable application data.

Billing thresholds#

  • Egress — First 100 GB per month is included
  • Wallet funding — Runtime affordability depends on a positive billed-owner balance

Operational guidance#

  • If you need more capacity, scale replicas first, then CPU/RAM.
  • If your app writes state to disk, move that state to external storage.
  • If builds are unstable near the timeout, treat that as a deployment risk rather than a normal condition.