Limits & pricing
Feato applies limits to ensure platform stability, predictable performance, and fair usage across all projects.
Limits vary depending on the selected plan and are enforced at the project level.
All limits are explicit and enforced consistently. There are no hidden throttles or silent degradations.
Pricing model
Feato pricing is based on project usage rather than per-user or per-seat licensing.
This model allows teams to scale usage naturally without managing user counts or access tiers.
- Limits apply per project
- Environments are isolated
- SDK usage is included
For current plans and pricing details, refer to the pricing page.
Usage limits
Usage limits are designed to protect both the platform and connected applications.
Common limits include:
- Maximum number of feature flags per project
- Maximum number of connected clients
- Event throughput limits
When a limit is reached, Feato enforces it deterministically and without partial behavior.
Blocked projects
A project may become blocked if it exceeds plan limits or encounters billing issues.
When a project is blocked:
- Real-time updates are suspended
- Feature flags resolve to safe defaults
- No runtime errors are thrown in applications
Blocked projects are handled gracefully to ensure application stability in production environments.
SDK behavior under limits
Client SDKs are designed to handle limit-related scenarios safely and predictably.
- No crashes or unhandled exceptions
- Last known flag state is preserved
- Applications continue running normally
This behavior ensures that feature flags never become a single point of failure.
Monitoring and visibility
The Feato Console provides visibility into project usage and limit status.
Teams are notified before critical limits are reached, allowing proactive action.
Usage information is always visible and never hidden behind support requests.
Next steps
To learn more about using Feato effectively, explore: