Billing (Openship Cloud)

Monthly managed servers

Each managed Cloud server has its own subscription. A monthly plan covers the purchased CPU, RAM and disk for the full paid period. There is no second compute-credit allowance and no compute top-up to keep a paid monthly server running. CPU is shared capacity, not exclusive physical cores.

The pricing page and GET /api/billing/plans publish the current offers. Choose Custom to set CPU, RAM and disk and review a monthly quote before checkout. Custom uses the same managed-server subscription and payment flow. A server can have at most 12 vCPU. Enterprise terms are available through sales. An account without a plan has no included Cloud compute.

Openship owns retail prices. Oblien verifies resource availability, payment and paid-through coverage. Renewals retain saved terms; changes to the public catalog do not alter a purchased contract. Existing metered subscriptions are not converted automatically and continue to show their saved allowance in Billing.

Sharing your server

Apps and source builds share the server's CPU, RAM and disk. A project can use the full available capacity; the operating system, builds and other projects also need room. Container limits do not reserve another VM or disk. Image-only installs do not create a source builder, and undeployed drafts do not use service slots. There is no monthly build-time cap on these monthly offers.

The server page separates purchased capacity from measured CPU, memory and disk usage, including a project disk breakdown. An unknown measurement stays unknown. A provisioned disk size is not the amount of data stored on it. Add another subscribed server when you need a separate resource pool.

Every server plan includes unlimited team members without a per-seat charge.

Coverage and separate services

Overview shows the billing mode, coverage status and paid-through date. Usage shows recorded resource usage; monthly servers show CPU time instead of compute-credit spend. A recorded usage comparison uses the contract's saved PAYG rates. It is not a promised cash saving or a new charge for monthly compute.

Monthly servers include managed internet transfer. Billing shows the provider's available allowance (or Unlimited) and usage for the current period. This covers Git clones, package downloads and other managed internet traffic; public app-route traffic and backups are separate. Exhausting transfer cannot end a confirmed paid month of CPU and RAM.

The Prepaid PAYG pricing preview shows Openship resource tiers separately from credit packages. Tier 1, Tier 2 and Tier 3 describe the combined CPU, RAM, storage and server limits for a PAYG pool. The tier tabs show the credit purchase threshold and the pool's capacity. These numbers stay fixed while you configure a server. Credit purchases unlock tiers; spending credits does not lower an unlocked tier. Selecting a tier or package in the preview does not grant it.

Customize CPU, RAM and storage to estimate one server's hourly cost at full CPU usage. Servers share the tier's pool allowance. If a configuration exceeds the selected pool, the preview keeps your inputs and offers a larger tier that fits when available. The credit card shows which tier the selected package would unlock. Resource rates and the credit conversion come from the provider's published catalog: active CPU time, reserved RAM time, and retained provisioned storage.

CPU time is measured in vCPU-hours, separately from elapsed time online. Four allocated vCPUs averaging 25% activity consume one vCPU-hour in one elapsed hour. Two such hosts consume two vCPU-hours during that same hour. The estimator shows the configured server's hourly resource usage at full CPU activity. Lower CPU activity reduces CPU usage; reserved RAM and storage continue to accrue usage. The estimate leads with dollars per hour and the equivalent credit deduction, with a visible CPU, RAM and storage breakdown. Open Balance estimate for the duration range from 100% CPU activity to idle CPU, including RAM and storage at both ends. These are usage scenarios, not a guaranteed number of days or a required monthly deposit.

PAYG estimates use the published resource rates throughout the displayed period. Balance duration is prepaid funds divided by usage cost; monthly host prices do not set a ceiling on the estimate. Optional proxy transfer, taxes and storage retained after compute ends are separate. Purchases are not available yet. Selecting PAYG does not switch an existing monthly server, buy credits or debit a wallet.

Managing your plan

Choose the managed server to inspect its own billing. Get server starts a separate subscription; it does not replace the selected server's plan. New customers see plan selection without empty usage or payment-history tabs.

Choose Review change to see Oblien's amount due now, prorated adjustment, effective date and the projects that may restart. Upgrades apply after confirmed payment. Resource reductions and billing-mode changes wait for renewal, even when their retail price is higher. The returned preview is authoritative. Usage and already purchased top-ups remain attached to their existing terms.

Pending changes stay visible in the subscription card. Complete payment there, or cancel a pending change when allowed. Cancel a pending change before stopping or resuming renewal. Retries use the same financial operation.

After payment, the shared server worker applies the approved resources and restarts affected projects. If the server changed since review, Apply plan capacity asks for a fresh restart confirmation. An existing disk can grow but cannot shrink in place. Choose Custom to keep the disk while reducing CPU or RAM, or migrate to a smaller server.

First subscriptions use hosted checkout. The return page checks the specific payment and provider fulfillment; a successful browser redirect does not grant coverage. Pending, refunded and failed payments remain distinct. Choosing a preset on the public Pricing page opens Cloud checkout for that plan after sign-in. You do not need to select it again. If an offer is no longer available, Cloud shows the current plans instead. Refreshing or retrying that purchase reuses its server and payment attempt.

If a checkout was left open, Pending payments in the Billing header lets you resume its original payment or cancel an unpaid checkout. Cloud uses the provider’s checkout cancellation capability, with capacity-quote cancellation retained for older provider deployments. This remains available before a server has a paid plan. A pending cancellation keeps the purchase tracked until confirmed; a payment that completes meanwhile opens its verification status instead of another checkout. Confirmed cancellation or expiry lets you choose a new plan and remove an unused, unpaid server. If cancellation cannot be verified, refresh the payment status. If this payment has no supported cancellation, complete it or wait for expiry before selecting another plan; removing its local record would leave its payment link active.

Cancellation and retained storage

Canceling renewal keeps the current paid period. You can resume renewal before it ends. Compute stops after coverage expires unless renewal is confirmed; a manual suspension can also stop a server during a paid period.

Cancellation does not delete data. The provider's initial tariff retains disks for at least 30 days with no automatic deletion. Retained provisioned storage is billed at the saved rate after compute coverage ends, until those disks are actually deleted. The minimum retention review date does not stop those charges. Billing shows the contract's retention terms and any amount due. Contact support if a storage payment needs attention.

Credit warnings and recovery

Credit warnings apply to saved metered subscriptions, not monthly capacity contracts. When applicable, a compact notice in the bottom corner identifies the server and can be opened or dismissed. Top-ups increase that subscription's metered allowance without increasing its CPU, RAM or disk limits.

A top-up cannot restart an ended or past-due subscription. Restore its payment first. Checkout waits for provider confirmation before showing new credits. The warning refreshes when you return to the dashboard and every minute while visible. Notifications follow the user's preferences; email needs a verified address and a working mail connection.

See the billing API for the operations behind these screens.