Managed services
Zenifra managed services provide ready-to-use data and asynchronous processing capabilities without requiring you to operate the service yourself. Choose a profile, inspect the price catalog in Brazilian reais, and connect your application using the connection details provided by the platform.
Required permissions
| Action | Minimum scope |
|---|---|
| Create Valkey, Cache, or Queue | managed_service.create on organization:* |
| Read status | managed_service.status.read on managed_service:<project-id> |
| Read the masked connection | managed_service.connection.read on managed_service:<project-id> |
| Rotate credentials | managed_service.credentials.rotate on managed_service:<project-id> |
owner has full access. assistant, member, and organization API Keys need the corresponding grants.
Available capabilities
Video: creating a Valkey Cache on the Free profile, from the form to the running cache page.
- Valkey: Key Value for persistent data, Cache for temporary data, and Queue for asynchronous processing.
For relational databases, see PostgreSQL and MariaDB; for analytical data, see Analytics (ClickHouse).
Choose by use case
Use Key Value when data must remain available after restarts and form part of your application's state. Use Cache for temporary data that can be rebuilt and to improve response times. Use Queue when producers and consumers need to decouple message processing.
Each profile has its own plan family (db-* for Key Value, cache-* for Cache, and queue-* for Queue), with capacity, storage, high availability, and hourly, monthly, or yearly pricing. Cache has no durable storage or replicas; Key Value and Queue have one primary and two replicas starting with the Basic plan. Inspect the catalog before creating a project so you can compare the cost in BRL.
Next steps
Last updated on