Forgeon Docs

Documentation, guides, and patterns to help you build on Forgeon — from your first deploy to running serious infrastructure.

Billing overview

How Forgeon billing works across plans, usage, and credits.

Last updated: 2026-03-17

Forgeon billing combines plan tiers with usage‑based charges.

Billing overview

What you pay for

  • Plan (subscription tier)
  • Usage (runtime + database)
  • Add‑ons (marketplace or extras)

Billing flow in one glance

  1. Plan assignment determines baseline limits/features.
  2. Runtime/DB usage events are recorded continuously.
  3. Usage is rolled up into billable metrics.
  4. Credits are applied according to policy.
  5. Final invoice is generated for the cycle.

Where to see it

  • Settings → Billing plan
  • Settings → Billing usage
  • Settings → Credits

How invoices are generated

  1. Usage is rolled up hourly
  2. Plan + usage are combined into a monthly invoice
  3. Credits (if available) are applied

Practical controls you should enable

  • Low-balance credit alerts.
  • Usage threshold alerts for high-cost metrics.
  • Clear tenant ownership for plan changes.
  • Monthly invoice review checklist for finance/admin.

Troubleshooting

Usage looks empty

  • Wait for rollups to complete (hourly).
  • Confirm events are being ingested from deployment/runtime services.

Plan changed but limits unchanged

  • Check active plan assignment and policy snapshot refresh.
  • Verify tenant context is correct in dashboard session.

See also