ROOM TO EXPERIMENT
Every PR gets
a place of its own.
A full, live environment for every idea. Share a link, test the whole stack, and get feedback before you merge.
Explore preview environments Your next deployment starts here Make room for
Make room for
your next idea.
You build the good stuff. We’ll get it live.
Every pull request, its own world. Every merge,
a way forward. All on infrastructure you control.
Self-hosted · Git-native · Yours to control
BUILT FOR THE WAY YOU BUILD.Meet your new workflow ↓
YOUR STACK.
RIGHT AT HOME.
RIGHT AT HOME.
GitHub
Docker
⎈Kubernetes
PostgreSQL
Your CLI
MORE BUILDING. LESS EVERYTHING ELSE.
Small pushes.
Big possibilities.
The space to experiment. The confidence to ship.
The platform that connects the two.
Every PR gets
REALISTIC BY DESIGN
Real-world data.
A world of its own.
Restore a production snapshot into isolated Postgres. Scrub credentials, run your migrations, and test beyond an empty database.
Get to know your data flowPush. Preview. Repeat.
New commits rebuild your preview. Its database persists across pushes, so your testing picks up where you left off.
A boundary for every branch.
Separate namespaces, resource quotas, and network policies keep experiments contained on your cluster.
Close the PR. Clear the space.
Automatic teardown and expiry-based cleanup keep yesterday’s experiments from becoming tomorrow’s chores.
LESS FRICTION. MORE FORWARD.
A workflow that
gets out of your way.
From your first push to your next release.
The Git workflow you know, with the
infrastructure work taken care of.
THE PREVIEW STAGE
Review the real thing. Together.
Give your team a working app with its own database. Every push updates the preview, so feedback happens on the code you actually plan to ship.
Make it your workflowatlas / previewDEMO
❯ 6ev deploy atlas 42
Postgres snapshot restored + security-scrubbed
Branch migrations applied
web + api healthy · preview ready
Preview is ready
Readyatlas-pr-42.6ev.netBUILT FOR DEVELOPERS. AND THEIR AGENTS.
MCP · in previewGive your agent
somewhere real to work.
From a fresh environment to the log line that explains a failure. Give your agent a way to test, investigate, and verify against your actual stack.
Git-driven previews are available now. Deployment MCP is in preview.
atlas / agent sessionILLUSTRATIVE WORKFLOW
Spin up a working environment for PR #42.
An agent opens a pull request on a registered project. 6ev builds its apps and provisions an isolated preview. An authorized CLI session can also deploy an open PR.
6ev CLI
6ev deploy atlas 42A whole stack, ready for review
web + api · isolated Postgres atlas-pr-42.6ev.net
Project configuration determines which services, database setup, and migrations run.
PRODUCTION CONTEXT
Your stack, in isolation.
Your Dockerfiles, production manifests, and branch migrations. Add a scrubbed production database snapshot when your project calls for one.
PREVIEW + PRODUCTION
Evidence you can trace.
Follow the commit and deployment attempt from status to logs. Verify a new attempt after a fix, without mistaking an older success for today’s result.
SCOPED MCP ACCESS
Visibility, on your terms.
The MCP preview uses OAuth consent and revocable read access. Agents inspect redacted deployment evidence; Git and CLI credentials govern changes.
THE PLATFORM IS YOURS.
A little less ops.
All of the control.
Developer experience shouldn’t come at the cost of ownership. 6ev runs on your Kubernetes infrastructure, with the tools and deployment logic you already use.
- Your Dockerfiles. Your app manifests.
- Your secrets, managed from one console.
- Your deploy scripts, on approved production targets.
- Console or CLI. Work your way.
A FEW THINGS, CLEARED UP.
Good questions.
Straight answers.
What is 6ev?+
6ev is a self-hosted deployment platform for teams running on Kubernetes. Register your repository and configure its apps once, then pull requests get live preview environments and pushes to the default branch can trigger production deployments.
Is this just a frontend preview?+
No. A preview can include your frontend, API, background services, and an isolated Postgres database. 6ev builds the apps you configure using your existing Dockerfiles and Kubernetes manifests.
What happens to my production data?+
When configured, previews restore a production snapshot into their own Postgres instance and run your security scrub and branch migrations. Credential scrubbing is mandatory in that flow. Personal-data anonymization is project-specific and must be configured before sharing previews with a wider audience.
Can I keep my existing infrastructure?+
Yes. 6ev is self-hosted on Kubernetes and reuses your app manifests. Production runs your repository’s configured deploy script on approved cluster targets. Your infrastructure and deployment logic stay under your control.
Can an agent create and debug an environment?+
An agent can open a pull request on a registered project or use an authorized 6ev CLI session to deploy an open PR. The deployment MCP lists preview and production deployments, inspects an exact attempt’s outcome, and reads bounded, redacted deployment-job logs. With separately granted preview or production configuration access, an agent can also update saved environment variables and secrets for future deployments. The agent fixes code through your normal repository workflow and checks the new attempt after a push. MCP itself cannot start, retry, or cancel a deployment.
What happens when a pull request closes?+
6ev tears down the preview namespace and runs your configured cleanup hook for external resources. An expiry-based janitor also cleans up stale environments, so forgotten branches don’t need to become permanent infrastructure.
LESS BETWEEN YOU AND LIVE.
Your next idea
looks good from here.
Let’s build it A little more momentum. A lot more possibility.