Skip to main content
This guide explains how the current Servbase billing lifecycle works from the customer’s point of view.

Renewal model

Servbase currently uses manual renewal. That means:
  • there is no automatic recurring renewal behavior
  • you settle billing from the Billing area when required

Early payment behavior

If you pay before expiry, the platform extends from your current subscription end date rather than resetting from the payment timestamp.

Pending invoice reuse

When possible, the platform reuses an existing unpaid pending invoice for the same intent instead of generating duplicates.

Overdue timeline

Current enforcement timing:
  • day 0: subscription expires and becomes overdue
  • day 1 overdue: applications are paused and public serving is blocked
  • day 3 overdue: applications are deleted if payment is still unsettled

What pause means

When an app is paused because of overdue billing:
  • deploy is blocked
  • rebuild is blocked
  • restart is blocked

Add-ons

Add-ons are capacity extensions for an active base plan. If the base plan is inactive, add-on capacity is not applied.

After payment

If payment is settled before deletion enforcement finishes:
  • the account can return to good standing
  • paused apps can be restored
If the apps were already deleted after the enforcement window, payment does not automatically rebuild them.