Fair Usage Policy

Our Philosophy: Optimization, Not Monetization

The FUP exists to protect platform stability and infrastructure health—not to force upgrades, trap you into upsells, or hit you with surprise overcharges.

ConfigBee is designed to be a generous, collaborative partner in your growth. If your account ever crosses a policy threshold, we won’t automatically charge your card or shut off your services. Instead, our engineers will reach out to look at your integration, help you optimize your code, and work with you to find a fair path forward.

Fair Usage Limits Overview

ConfigBee uses this Fair Usage Policy (FUP) to protect platform stability, prevent infrastructure abuse, and keep unit economics healthy for everyone.

FUP limits are calculated directly from your MAVs (Monthly Active Visitors) and DUs (Deployment Units), both of which are provisioned by your pricing plan. These limits are driven by these specific quotas rather than live traffic counts, making them predictable from day one and letting them grow proportionally as your plan upgrades.

Limit Breakdown

Limit	Formula	Description
Staff Seats	DUs + (MAVs ÷ 100)	Number of internal users (Product Managers, developers, GTM teams) with ConfigBee dashboard access to manage configurations
Network Requests (per month)	MAVs × 10,000	Total CDN/backend requests
Network Traffic (GB per month)	MAVs ÷ 25	Data transferred in/out from the CDN/backend
Concurrent Connections	DUs × 2 + (MAVs ÷ 100)	Simultaneous client‑side and server‑side SSE streams
Projects	DUs	Total number of projects in the account
Environments	DUs	Total number of environments across all projects
Config Updates (per month)	DUs × 100	Total number of configuration updates. This includes any published changes triggered by operations like publish, add option/flag, update default values, environment creations, rollout creations, updates, etc.
Context Groups	DUs ÷ 5	Total number of Context groups across all projects. These groups are used to capture targeting-related context, such as User, City, Account, Organization, etc.
Stored Context Records	MAVs × 10	Total number of entity records stored across all Context groups (e.g., creating a record for “User 1” or “City Chennai”). Each record stores a configured set of attributes defined by that group. These records populate dashboard dropdowns and are fully searchable for easy, precise targeting setup
Target Lists	DUs	Total number of target lists across all projects. These lists are created based on a Context Group to manage groups of Context Records (which can be added or removed). They support optional overriding of flag and configuration option values, and can be actively utilized within rollouts for contextual targeting
Targets per List	DUs × 4	Total number of target items (Context Records) that can be added to a target list
Individual Personalizations	DUs × 4	Total number of individual personalization rules allowed. This enables overriding a feature flag or configuration option value for a specific individual Context Record

Plan Limits Overview

Limit	Free	Starter	Growth
Deployment Units (DUs)	10	25	100
Monthly Active Visitors (MAVs)	500	5 000	25 000
Staff Seats	15	75	350
Network Requests	5 M requests	50 M requests	250 M requests
Network Traffic (GB)	20 GB	200 GB	1 000 GB
Concurrent Connections	25	100	450
Projects	10	25	100
Environments	10	25	100
Config Updates	1 000	2 500	10 000
Context Groups	2	5	20
Stored Context Records	5 000	50 000	250 000
Target Lists	10	25	100
Targets per List	40	100	400
Individual Personalizations	40	100	400

The above are standard estimates based on the DUs and MAVs of our default pricing plans. Actuals may vary due to add-ons, promotional campaigns, Enterprise tiers, or custom contracts.

No Seat Tax

ConfigBee never gates internal company adoption. Staff seats are generously scaled via our FUP formula to allow zero per-seat charges for your genuine internal team—including your developers, PMs, QA, marketing, and customer success teammates.

Note: This FUP policy is strictly protected against misuse. It does not permit shared account access across multiple distinct companies, agencies managing separate client portfolios, or proxy account configurations.

The “No Automated Penalty” Guarantee

When a Fair Usage Policy threshold is reached, ConfigBee never automatically charges your credit card or suspends your services. Instead, our team initiates a consultative review to analyze your integration, identify caching optimizations, or discuss a alternative pricing plan or pricing model. The outcome is always a collaborative conversation—never a surprise invoice.

Please note, however, that service penalties or suspensions remain a last resort reserved strictly for clear system abuse, a total lack of cooperation, prolonged non-responsiveness, etc.

Engineered to Stay Within FUP

ConfigBee’s platform architecture and SDKs are built from the ground up to keep your request volume well within your FUP allocations. As long as official SDK best practices are followed, you generally don’t need to write defensive code — the following behaviors are built into every official SDK:

• Real-time updates via SSE. The SDK does not poll. Configuration changes are pushed to your application only when something changes on the platform. See the JavaScript, React, Flutter, Python, and OpenFeature Web SDK pages for each SDK’s real‑time update behavior.

• Local caching & offline handling. Configurations are cached locally on the device. On application relaunch, values are served from cache without waiting for the network.

• Auto-retry & multi‑cloud CDN failover. Network retries utilize smart, bounded, backoff-based scheduling. If a user experiences a transient network blip, the SDK ensures it generally does not generate a harmful request storm against the CDN/backend.

Don’t Build Your Own Polling Loop

The SDKs receive updates automatically via live streaming — you do not need to poll getFlag, getNumber, getText, or getJson on a timer. Reading a value always returns the latest known state, and the onUpdate callback is fired when that state changes. Building your own polling loop defeats the SDK’s built‑in caching and can drive your account toward the network request limit.

Proactive Traffic Waivers (Spike Waiver)

If you anticipate a major, short‑term traffic event — a Product Hunt launch, a press release, an influencer campaign, or a scheduled infrastructure stress test — you can request a proactive traffic waiver (internally called the “Spike Waiver”) in advance.

Approved waivers grant a steep discount or full waiver on temporary overage costs for the affected billing cycle. The scope of each waiver is discussed case‑by‑case with our team at the time of the request; it may include a co‑marketing component, but participation is always voluntary and never a condition of using the platform.

If you anticipate a traffic spike, request a waiver by emailing [email protected] with the subject “Spike Waiver Request”.

Requesting a Fair‑Use Review

If you’ve received a fair‑use review notification or believe your integration is approaching a limit, contact [email protected] with your Account ID and a brief description of your integration. Our engineering team will work with you to identify optimizations or discuss the right plan tier for your current scale.

Changes to This Policy

ConfigBee reserves the right to update these formulas as the platform evolves. If we ever lower a limit or tighten a policy, we will announce it on this page with at least 30 days’ notice before it takes effect. Adjustments that benefit you—such as removing a limit or increasing allocations—may be applied instantly and without prior notice.