---
title: "Unlimited Environments"
description: "Every Git branch is a full gateway environment. Test changes in isolation without the cost or complexity of managing multiple clusters."
canonicalUrl: "https://zuplo.com/features/unlimited-environments"
pageType: "feature"
tag: "Developer Workflow"
docsHref: "https://zuplo.com/docs/articles/environments"
---

# Unlimited Development Environments

> Every Git branch is a full gateway environment. Test changes in isolation without the cost or complexity of managing multiple clusters.

## Key Benefits

- **Branch = Environment** — Create a new preview environment instantly by pushing a branch. No infrastructure provisioning, no extra cost.
- **Isolated Testing** — Each environment is fully isolated — test breaking changes without affecting production.
- **Included in All Plans** — Unlimited environments are included in every Zuplo plan, including the free tier. No per-environment fees.

## Instant Preview Environments

![Instant Preview Environments](https://zuplo.com/images/features/unlimited-environments-1.svg)

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.

## Environment-Specific Configuration

![Environment-Specific Configuration](https://zuplo.com/images/features/unlimited-environments-2.svg)

Each 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.

## Promote Through Environments

![Promote Through Environments](https://zuplo.com/images/features/unlimited-environments-3.svg)

Zuplo's promotion workflow lets you move a tested configuration from staging to production with a single action, maintaining environment parity and reducing deployment risk.

## FAQ

**Are there limits on the number of environments?**

No. Zuplo offers unlimited environments on all plans. You can have development, staging, production, and unlimited feature branch environments simultaneously.

**Do environments share resources?**

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.

**How do I manage environment-specific secrets?**

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.

**Can I delete environments when I'm done?**

Yes. Preview environments are automatically cleaned up when the corresponding branch is deleted, or you can manually delete them from the portal.

## Learn More

- [Docs](https://zuplo.com/docs/articles/environments)