Question 1

What are Client Sessions?

Accepted Answer

Each instantiation of a client SDK creates a client session. The session extends for as long as the same SDK client instance is used regardless of the number of calls to initialize or updateContext.

In the case of web browser SDKs, where each page load creates a new client instance, the SDKs cache the session identifier in localStorage. As long as localStorage is not cleared, the client session will extend for up to 6 hours.

Free and Pay as you go both include 40K client sessions a month at no cost. The count resets at the start of each billing cycle.

Question 2

What are Service Connection Hours?

Accepted Answer

Service connections are persistent and long-lived connections initiated from server side SDKs. We bill based on service connection hours, meaning the cumulative number of hours server SDKs have been connected or persistently polling.

Free and Pay as you go both include 3,200 service connection hours a month at no cost. We consider 800 hours to be a generous monthly budget for a single server continuously connected plus a buffer of hours to account for temporary scaling up during brief traffic spikes and deployments.

For example, the 3,200 free hours cover 4 concurrent servers continuously connected through the month, with a buffer for temporary traffic spikes.

If you configure your server SDK to use polling instead of streaming, each polling request is accounted as 5 minutes of usage for billing. The default polling interval is 5 minutes, matching the same usage rate as a streaming connection.

Question 3

What happens when I reach my spending limit?

Accepted Answer

A hard spending limit is optional on Pay as you go. You set it as a dollar amount in the Billing section of the dashboard, and your bill never goes past it in a month.

You won't be caught by surprise. When your usage is on track to go over the limit, you get an alert at 70% and another at 90% of it, and one more if the limit is reached. You can also add up to 5 spend alerts of your own at any dollar amounts, each with a priority from medium to critical.

When spend reaches the limit, service stops until the monthly billing cycle resets: configs are no longer evaluated and each config returns the in-code default value passed to the SDK. Without a hard limit, your flags keep working whatever your usage, and it is billed at the Pay as you go rates.

Question 4

Is JSON Schema validation included for free?

Accepted Answer

Yes. Both Free and Pay as you go can validate JSON config values against a JSON schema. JSON values are validated against the schema whenever you save the schema itself, update targeting rules, or update experiment variations. A value that does not validate against the schema never reaches your applications.

Validating the provided schema itself, and validating JSON against a schema are two of the most resource intensive operations we run. In order to protect our systems from abuse, Free has an hourly fair-use budget of 20 schema changes and 300 value validations per organization. Each save of targeting rules and experiment variations for a JSON schema-validated config counts as one validation. If you reach the budget, the dashboard tells you when it resets, and your configs keep serving their current values in the meantime.

Pay as you go has no hourly budget on JSON Schema validation. Both options share the same limits on the schema itself: 32 KB per schema, 50 levels of nesting, 1,000 enum items, and 32 regular expression patterns of up to 512 characters each.

Question 5

Can I switch from Free to Pay as you go?

Accepted Answer

Yes. Adding a payment method in the Billing section of the dashboard moves your organization to Pay as you go right away, with no interruption in service. The free allowance still applies, so you pay nothing until your usage goes past it.

If an organization on Free goes over the allowance, it has a 7-day grace period to add a payment method for Pay as you go before service is interrupted. After that, for any usage above the allowance, configs are no longer evaluated and each config returns the in-code default value passed to the SDK until the monthly billing cycle resets.

	Client sessions	Service connection hours	Admin API requests
Monthly usage
Included free	FreeFirst 40K	FreeFirst 3,200 hours	FreeFirst 10K
Tier 1	$0.80 / 10K40K to 500K	$5.00 / 1,000 h3,200 to 8,000 hours	$0.50 / 10K10K to 50K
Tier 2	$0.60 / 10K500K to 2.5M	$4.00 / 1,000 h8,000 to 24K hours	$0.40 / 10K50K to 300K
Tier 3	$0.40 / 10K2.5M to 10M	$3.00 / 1,000 h24K to 80K hours	$0.30 / 10K300K to 1M
Beyond	$0.35 / 10KOver 10M	$2.50 / 1,000 hOver 80K hours	$0.25 / 10KOver 1M

Start free. Pay only for what you use.

Pay as you go rates

Estimate your monthly bill

You stay in control of spend

FAQs

Ready to ship confidently?