Plans, Trials and Billing

Understand direct subscriptions, quotas and access changes.

CoreFinOps's commercial architecture supports a shared product and entitlement system regardless of purchasing channel. A workspace can be billed directly on the website or through AWS Marketplace, with a single effective billing source.

Direct subscription lifecycle

For direct buyers, hosted checkout and a billing portal are implemented through a configured billing provider. The browser redirect alone must never activate a paid plan. Signed provider events and reconciliation determine paid subscription state.

Entitlements and quotas

The backend determines features and limits from persisted verified state. Depending on the approved plan, limits may include AWS account count, team seats, refresh frequency, ingestion rows, reports/exports or historical retention. Exceeding a quota must be enforced server-side even if the UI still shows a button.

Billing states

Trial, active, grace, suspended, cancellation and renewal require explicit user-visible messaging. During provider outages, CoreFinOps should apply a bounded, auditable policy rather than grant unlimited paid access or immediately destroy read access.

Safety rules

Never enter card information directly into an untrusted CoreFinOps form when the approved path is hosted checkout. Do not buy two active subscriptions for one workspace. The product must not show direct checkout to a workspace already paid through AWS Marketplace.