Skip to main content
Two public pages answer the operational questions a platform team asks before depending on a vendor: is it up, and is it safe. Both are maintained outside this documentation and linked here so you know where to look.

​
The Flexprice status page

status.flexprice.io shows live status and a 90-day uptime history for the two things your integration depends on: Incidents and scheduled maintenance are posted there with timelines. If every request from your side is failing at once, check it before debugging your code. The API also exposes a health endpoint you can poll from your own monitoring:
Ingestion is asynchronous. POST /events returns 202 as soon as the event is queued, so a healthy API and a delayed metering pipeline can coexist briefly. The architecture page describes the buffering that protects events during that window, and the freshness guarantees for balances and alerts.

​
Flexprice availability and latency commitments

Published targets for availability, ingestion latency, and query latency live on the architecture page. Enterprise agreements carry their own SLA terms.

​
The Flexprice trust centre

trust.flexprice.io holds the compliance reports and security documentation that procurement and security reviews ask for. Flexprice is SOC 2 Type II, ISO 27001, and GDPR compliant, with controls across product, data, network, application, endpoint, and corporate security. Request the SOC 2 report and policies through the trust centre. The public summary is at flexprice.io/security.

​
Data residency by region

Flexprice Cloud runs in two regions, and a tenant’s data stays in the region it was created in: For deployments that must keep data inside your own network, the community edition can be self-hosted.

​
Reporting a security issue

Send vulnerability reports to security@flexprice.io with reproduction steps. Flexprice acknowledges reports within three business days, works with good-faith researchers under a responsible disclosure policy, and credits reporters in public disclosures. The full policy, including what is out of scope, is in the SECURITY.md of the backend repository. Do not run automated scanners against Flexprice Cloud without permission, and do not test against other customers’ data.

​
Rotating a leaked credential

If an API key or webhook secret is exposed:
  1. Delete the key in the dashboard under Developers, or with DELETE /secrets/api/keys/{id}. It stops working immediately.
  2. Create a replacement and deploy it.
  3. Rotate the webhook signing secret from the endpoint’s page; deliveries carry both signatures during the grace period. See Signature verification.

status.flexprice.io

trust.flexprice.io