shiprr.
Log in Create account

Billing

Shiprr uses a wallet-style billing model. Fund the wallet, let usage deduct from it, and optionally enable auto-recharge to keep apps running.

What you pay for#

  • Runtime — CPU and RAM while replicas are running.
  • Build minutes — Build time after the included monthly free tier.
  • Egress — Outbound traffic after the included allowance.

Wallet and top-ups#

New accounts receive €5 welcome credit. Add more funds from the billing page in the dashboard. Wallet balance is then consumed by runtime, egress, and build charges over time.

Auto-recharge#

Auto-recharge lets Shiprr top up your wallet automatically when it drops below a threshold. Set both the threshold and top-up amount in the billing settings if you want the platform to keep the wallet funded.

Build minutes#

The first 50 build minutes per month are free. Build usage beyond that is charged per minute and appears in billing history. Build minutes are measured from actual build runtime. First builds can take longer while caches warm up, and later builds are often faster when dependencies and layers are reused.

Negative balance behavior#

Running and scaling apps requires a positive billed-owner balance. If the billed owner stays negative, Shiprr can stop running apps after a 72-hour grace period. Keep the wallet funded or enable auto-recharge if you want to avoid interruptions.

Where to review usage#

The billing dashboard shows wallet activity, runtime usage, build usage, payment history, and monthly summaries. Use it to understand which apps and builds are generating cost.