# VeilStream

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

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:** https://console.veilstream.com

**Quickstart:** https://docs.veilstream.com/docs/quickstart

**Install:** `curl -fsSL https://cli.veilstream.com | bash`

This page is the markdown version of https://www.veilstream.com/. For the full documentation corpus, use https://docs.veilstream.com/llms.txt.

## Story

Push a branch → VeilStream creates a live preview environment → it gets safe, production-like data → humans and AI agents can use it.

Keep your repository, Docker Compose file, and Postgres. VeilStream connects them.

## How it works

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

## Safe data

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.

One source database. Different views by role:

- **Application** — production shape, secrets masked or hidden
- **Developer** — production-like values that are already sanitized
- **Support** — enough to help a customer
- **AI agent** — stand-in values, temporary access that expires

Rules can mask columns, replace values, hide columns, filter rows, issue temporary credentials, and record queries.

## 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, over MCP.

## What you no longer have to build

- 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. No manual database scrubbing. No permanent agent credentials. Define the rules once; VeilStream applies them everywhere.

## 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. Details: https://pricing.veilstream.com/

**Is VeilStream hosted Postgres?**
No. Use the Postgres you already have. VeilStream controls what each environment or caller can access.

**Do I have to change my Compose file?**
No. VeilStream turns your existing Docker Compose file into an isolated environment.

**Can an AI agent use the environment without seeing real values?**
Yes. Temporary, scoped access under the same data rules, then it expires.

**What is an environment versus a deployment?**
An environment is the live preview. A deployment is one build of that environment. Detail: https://docs.veilstream.com/docs/concepts

## Links

- Homepage: https://www.veilstream.com/
- About: https://www.veilstream.com/about
- Docs: https://docs.veilstream.com/
- Docs for LLMs: https://docs.veilstream.com/llms.txt
- Quickstart: https://docs.veilstream.com/docs/quickstart
- MCP: https://docs.veilstream.com/docs/mcp/usage
- Pricing: https://pricing.veilstream.com/
- Console: https://console.veilstream.com/
- GitHub: https://github.com/veilstream