What Ensemble does not do
Ensemble turns every change into a running copy of your real app, with its services and data, at a private link anyone on the team can open. It doesn't replace your CI, your issue tracker, your production host or your coding agent. Engineers keep localhost and their editor. Ensemble fits between the tools you have.
Every new tool asks a team to change something. Before you evaluate Ensemble, here's what it won't ask you to change.
Ensemble is not CI
Ensemble doesn't build, test or gate your code. Your tests, checks and merge requirements stay in the pipeline you already run. When a change is ready, Ensemble opens a pull request, and your CI treats it like any other. A preview is for seeing a change, not for deciding whether it's safe to merge.
Ensemble is not an issue tracker
Ensemble doesn't hold your backlog. Linear is a way into Ensemble: a ticket can become a branch and a running preview, with the link posted back on the issue. But prioritization, cycles and status stay in Linear. There's no Jira integration at launch.
Ensemble is not production hosting
Ensemble previews aren't production. They run on seed data, sleep when idle, and exist to review changes before they merge. Your production app stays on the host you use today, whether that's Vercel, Railway, Render, AWS or anything else.
Ensemble is not a coding agent you have to switch to
Your agent stays Claude Code, Cursor or whatever you use now. Ensemble runs what it writes: every branch gets its own running copy of the app, so several agents can work at once without sharing one localhost, and you review a link, not just a diff. It also gives the agent codebase and product context over MCP. Developers keep their editor, their model and their workflow, and they keep localhost too.
Ensemble does not publish public demo URLs by default
Every preview is private by default, behind an Ensemble login. People outside your team get expiring share links. Public mode exists for demos, and someone has to turn it on for a specific preview.
What Ensemble does replace
Ensemble replaces three things:
- The "can you pull my branch?" loop. Every change has a link. Reviewers click it.
- Local setup for non-engineers. PMs, designers and founders make and see changes in the browser, without cloning a repo or installing a database.
- One localhost for every agent. Agents working on different branches each get their own running copy of the app, instead of taking turns on one machine.
If those are problems your team has, see what Ensemble is and how PMs ship a change without local setup.
FAQ
Is Ensemble an AI coding agent?
No. Ensemble runs what your coding agent writes and gives everyone a link to the result. It also gives the agent context about the codebase and product. Your agent still writes the code.
Does Ensemble host production apps?
No. Ensemble previews are for building and reviewing changes. Production stays on your current host.
Can we keep our staging environment?
Yes. Many teams keep staging for integration testing and use previews for individual changes. See preview environments vs staging.
Does Ensemble replace our CI pipeline?
No. Pull requests go through your existing CI and code review before anything merges.