Skip to content

Read your usage and billing

Everything about what FortressFlag costs you lives in two owner-only screens: Usage (what you’re using) and Billing (what you’re paying). Here’s how to read both.

You’ll need to be the organization’s Owner — these screens aren’t visible to other roles.

Admin → Usage shows three things:

  • Devices this period — your distinct monthly-active devices for the current calendar month (UTC). This is the number billing is based on. It only ever counts distinct devices: poll frequency doesn’t move it.
  • Twelve months of history — how the count has trended.
  • Daily real-vs-simulator request ratios — how much of your traffic comes from sim_ identities (simulators, emulators, automated browsers). Simulators are served flags but never billed; this chart is where a misconfigured build that’s claiming to be one — or failing to — becomes visible.

Trials include 1,000 monthly-active devices and never expire by time. If you grow past the tier, enforcement arrives in stages — a banner first, a read-only dashboard after 14 days, defaults for over-limit devices after 28 — and your first 1,000 devices keep real values throughout. Buying clears every stage instantly, which is why the Buy button still works from a read-only dashboard.

Admin → Billing is where money changes hands, and none of it happens on our pages:

  • “Buy more devices” opens Stripe’s hosted Checkout. Your card details go to Stripe; FortressFlag never sees or stores anything payment-shaped. The plan flips the moment Stripe confirms.
  • “Manage billing” opens Stripe’s Customer Portal — update your card, download invoices, or cancel, all in one place.

Invoicing is metered monthly, anchored to the same UTC calendar months as the Usage screen, so the invoice period and the meter always agree. What crosses to Stripe is your device count — never device identifiers.

If you cancel, the subscription’s end returns you to the trial tier, and the same staged enforcement applies from there — nothing shuts off abruptly.