Application configuration beyond your pipeline
Centralize configuration by application and environment. Use your CI/CD to fetch the values it needs, then choose how deeply to integrate.
Manage multiple applications with separate values for development, staging and production. Import existing .env files to get started.
Fetch configuration with credentials for the target application and environment. Keep application values in envbee when you switch CI/CD providers.
Assign profiles and environment permissions to manage who can read and update configuration.
Use Node.js, Python or .NET SDKs, or fetch configuration directly through the REST API.
Separate application configuration from deployment configuration
Keep database hosts, service URLs and application settings in envbee, organized by environment. Your pipeline keeps the credentials it needs to fetch those values, alongside its deployment configuration.
Use the API or an SDK in your deployment step, then pass the values to your application using its existing configuration mechanism. You can also fetch values when your application starts.
See the configuration flow or read your first variable.
Configuration that fits your application
- Import names and values from existing .env files.
- Manage string, number and boolean variables.
- Set different values for each environment.
- Export an environment’s values as a .env file.
Access controls and encryption support
Profiles and environment permissions control access to configuration. The API supports authentication with environment-specific credentials and HMAC signatures.
The SDKs support locally decrypting AES-256-GCM encrypted configuration values using a key supplied separately by your deployment or runtime environment.
SDKs and caching
Open-source SDKs are available for Node.js, Python and .NET. They can read individual values, fetch configuration in bulk and populate process environment variables.
SDK caches can provide previously fetched values if the API is unavailable. An initial successful fetch is required; cached values may be older than the configuration in envbee.
Optional hot reload through webhooks
Enable change notifications for selected variables and configure a webhook for the environment. Your application must handle those notifications and reload the configuration it uses. Hot reload is an optional integration, not a requirement for adopting envbee.
Learn how to handle configuration webhooks.
No vendor lock-in
Import and export .env files per environment. With deployment-time fetching, your application can continue reading its existing configuration format without calling envbee at runtime.
If you choose runtime SDK calls or webhook-driven reloads, those are integrations you would need to adapt when moving away. You can adopt envbee for deployment configuration first and add those capabilities only when useful.
Move your first application's config out of CI/CD.
Create an application, add staging and production, and connect your deployment with envbee credentials.