Branch = Environment
Create a new preview environment instantly by pushing a branch. No infrastructure provisioning, no extra cost.
Every Git branch is a full gateway environment. Test changes in isolation without the cost or complexity of managing multiple clusters.
Create a new preview environment instantly by pushing a branch. No infrastructure provisioning, no extra cost.
Each environment is fully isolated — test breaking changes without affecting production.
Unlimited environments are included in every Zuplo plan, including the free tier. No per-environment fees.
Every branch in your connected Git repository gets its own Zuplo preview environment with a unique URL. Create it in seconds by pushing code — no cluster setup, no Helm charts, no waiting.
Learn more in the docsEach environment can have different environment variables (backend URLs, secrets, feature flags) while sharing the same policy code. Manage environment config securely through Zuplo's portal or CI/CD.
Learn more in the docsZuplo's promotion workflow lets you move a tested configuration from staging to production with a single action, maintaining environment parity and reducing deployment risk.
Learn more in the docsCommon questions about Unlimited Environments.
No. Zuplo offers unlimited environments on all plans. You can have development, staging, production, and unlimited feature branch environments simultaneously.
No. Each environment is isolated with its own edge deployment, rate limit counters, and API key storage. Changes in one environment don't affect others.
Zuplo's environment variables are scoped per environment. Set different values for your staging backend URL vs. production, and Zuplo injects the correct value at deploy time.
Yes. Preview environments are automatically cleaned up when the corresponding branch is deleted, or you can manually delete them from the portal.
Join thousands of developers who trust Zuplo to secure, scale, and monetize their APIs.