Concepts
Environments and MACs
Separate rollout risk by environment and understand how Monthly Active Contexts are counted for planning and budgeting.
Environment isolation
Each environment evaluates flags independently and now has three keys: server, mobile, and client. That separation is what lets you test in development or staging without affecting production behavior.
Treat all three keys like credentials. Development, staging, and production should each use their own configured secrets so traffic cannot leak across boundaries or payload types.
Monthly Active Contexts
A Monthly Active Context, or MAC, is a unique context that requests feature flags from Zenmanage. The same context can request flags many times without increasing the count again for the same measurement window.
For monthly plans, MACs reset on the first of each month. For annual plans, the public pricing guidance describes MAC usage as the count of any used contexts over the preceding 30 days.
Planning guidance
- Use separate environments for pre-production validation and live traffic.
- Do not create unnecessary synthetic contexts in tests that run against real environments.
- Keep identifiers stable so the same actor does not look like a new MAC every time it evaluates.
- Review pricing guidance when modeling rollout traffic for large consumer applications or high-cardinality service fleets.
Next step
Take the next integration step in your own stack.
Start with the quickstart that matches your runtime, then return to the reference pages when you need exact request and payload details.