How a platform is priced and invoiced, and what the comp switch does.
Updated
Each platform has one billing row: a plan name, a monthly price, a status (trialing / active / past_due / comped), and Stripe customer/subscription pointers for collection. Platform invoices are generated per cycle and tracked per platform.
skip_payments is the deliberate way to carry a platform without charging it. Invoices are still generated — they land as skipped instead of being charged — because the paper trail is the point: a platform we carried for six months should be visible as such in the ledger, not absent from it. Comping and collecting are mutually exclusive by construction, so a comped platform can never sit in past_due and trigger dunning.
Platforms that use the managed deploy infrastructure (DigitalOcean apps for client sites) are billed the raw instance cost plus a small oscillation buffer (5%), and the platform dashboard's Servers page shows the same numbers the deploy slider quoted — the bill and the UI never disagree.
A white-label platform is typically priced as a build-and-integration engagement plus the ongoing platform subscription and usage. For current numbers, see the white-label offering page or talk to us — the docs deliberately don't freeze a price list.