An environment for every branch. Live before the review starts.

Name: VeilStream
Brand: VeilStream

Open a pull request or push a branch. Get a URL to a dedicated preview environment running that code, with production-like data.

Get started View quickstart

Fits your existing stack

GitHub
Docker Compose
Postgres
Cursor
Claude
MCP

Keep your repository, Compose file, and database. VeilStream connects them.

From branch to usable environment

1 Push code
VeilStream detects the branch or pull request and reads your existing Docker Compose file.
2 Get an environment
Your services are built and deployed into an isolated environment with a unique URL.
3 With safe data
Use production-shaped data with data rules applied, so people and agents get realistic data without unrestricted production access.

Git branch Docker Compose Environment Safe data Human / AI agent

Production-like data without production-like risk

VeilStream sits between your environments and Postgres. Define what each role can see once, and the same rules apply to developers, applications, support users, and AI agents.

Production Postgres

VeilStream

Preview masked

Support limited

AI agent synthetic

public.customers Application

id	email	ssn	plan

Mask columns
Replace values
Hide columns
Filter rows
Issue temporary credentials
Record queries

Built for developers and coding agents

Coding agents need more than a repository. They need a running application, realistic data, credentials, logs, and a way to verify their work.

VeilStream gives each agent an isolated environment and temporary, governed access to the data it needs.

MCP · PR 184 Ready

Claude / Cursor
      │
     MCP
      │
      ▼
PR environment
 ├─ web
 ├─ api
 ├─ worker
 └─ Postgres access
       ↓
   VeilStream rules

What you no longer have to build

Define the rules once. VeilStream applies them everywhere.

Preview environment orchestration
Per-branch URLs
Preview database provisioning
Data sanitization pipelines
Database access controls for agents
Temporary database credentials
Environment lifecycle cleanup
Custom MCP deployment tooling

No duplicate database infrastructure

Use your existing Postgres. VeilStream controls what each environment or caller can access.

No manual database scrubbing

Generate sanitized snapshots using the same access rules you already defined.

No permanent agent credentials

Give AI agents temporary, scoped database access that expires automatically.

Fast
Branch to environment in minutes.
Compatible
Uses your existing Docker Compose and Postgres.
Governed
One set of data rules for applications, developers, support, and agents.
Disposable
Create environments automatically and destroy them when the PR merges.

Go deeper

Quickstart Connect a repository and create your first environment.
MCP server Give Cursor and Claude an environment and temporary data access.
Data rules Mask, hide, replace, and filter — then snapshot as a user.
Pricing First $20/month free. Pay for compute while environments run.
About Why we built VeilStream, and who is behind it.

FAQ

How does pricing work?

Usage-based. The first $20/month is free, with no credit card required. You pay for compute while preview environments run, plus metered database usage. When an environment is destroyed, compute billing stops. See pricing.

Is VeilStream hosted Postgres?

No. Use the Postgres you already have. VeilStream controls what each environment or caller can access. Credentials and data stay in your network by default.

Do I have to change my Compose file?

No. VeilStream turns your existing Docker Compose file into an isolated environment. Keep the repository, Compose file, and database you already run.

Can an AI agent use the environment without seeing real values?

Yes. Give the agent temporary database access under the same data rules you use for people. Access expires automatically, and you can revoke it.

Where does preview data come from?

Sanitized snapshots use the same access rules you already defined, so preview data is production-shaped without unrestricted production access.

What is an environment versus a deployment?

An environment is the live preview — the URL, services, and lifecycle. A deployment is one build of that environment, with logs and status. You mostly care whether the environment is ready. Detail lives in the docs.

Give every branch a real environment.

Connect your repository and Docker Compose file. Your next pull request gets an isolated environment with governed, production-like data.

Get started Read the quickstart