A preview your AI can actually use. Prod-like data. Scoped access. 

$ git push origin feat/tax-round
→ pr-184.env.veilstreamapp.com   Ready

We run your Docker Compose as a live URL. Each preview gets a database from a sanitized snapshot — not a live slice of production. The same data rules apply to developers, apps, support, and coding agents.

Get started View quickstart

First $20/month free. No credit card.

Works with

Built in British Columbia by Steve Jones and John Oram

From a customer

With VeilStream, we nearly doubled our sprint velocity. From 10 points to 19, and we sleep better at night.

Erik Dahl CTO, Parrot (YC F25)

Give AI agents temporary, scoped database access

Cursor and Claude get the live URL, logs, and Postgres credentials over MCP — not a repo checkout. Access expires after 60 minutes. The same data rules apply as for people. Queries can be recorded; you can revoke access.

  • Running app, not a checkout Live URL, logs, and services from the branch.
  • Credentials expire Temporary Postgres access, 60 minutes, then it is revoked.
  • Same rules as humans Mask, hide, replace, filter — with recorded queries.
MCP · PR 184 Ready 
Claude / Cursor
      │
     MCP
      │
      ▼
PR environment
 ├─ web
 ├─ api
 ├─ worker
 └─ Postgres access
       ↓
   VeilStream rules
       ↓
   Credential expires (60m)

Production-like data without production-like risk

Preview data is not a live proxy of production. We host a database from a sanitized snapshot of your Postgres. Define data rules once; they apply to developers, applications, support users, and AI agents.

public.customers AI agent
id email ssn plan

From branch to usable environment

Git push to a URL and a snapshot database.

  1. 1 Push code

    VeilStream detects the branch or pull request and reads your existing Docker Compose file.

  2. 2 We build and host it

    Your Compose services are built and run as temporary containers, isolated, with a unique URL. When the environment is destroyed, they go away.

  3. 3 With a snapshot database

    We host a preview database from a sanitized snapshot — refresh it nightly if you want. Copy-on-write makes each environment look like its own instance without copying the full dataset.

Git branch Build containers Live URL Snapshot DB Human / AI agent

How this is different

Vercel and Render give you a URL. Neon gives you a database branch. Codespaces gives you a cloud IDE. VeilStream gives each branch a URL and a sanitized database, with rules that apply to people and agents.

Capability comparison of VeilStream, Vercel, Render, Neon branching, and GitHub Codespaces
Capability VeilStream Vercel Render Neon branching Codespaces
Live preview URL from git Yes Yes Yes No Cloud IDE, not a shareable preview
Runs Docker Compose Yes — multi-service Frontend / serverless Dockerfiles No In the workspace
Preview database from your data Sanitized snapshot Optional add-on Copy of a Render database Copy-on-write branch You wire it
Sanitization / column rules Yes No No No No
Temporary agent DB credentials MCP, expires No No No No
You keep production Postgres Yes Yes Yes Neon is the database Yes

What you no longer have to build

Define the rules once. VeilStream applies them everywhere.

No shared staging database

Each preview gets its own copy-on-write instance from a sanitized snapshot.

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.

Product facts

Go deeper

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.

Do you actually run my Docker Compose?

Yes. We build the services from your Compose file and host them as temporary containers. When the environment is destroyed, they go away.

Do you host a preview database, or only proxy production?

We host a preview database from a sanitized snapshot of your data — not a live rewrite of production on the wire, and not a replacement for the Postgres you already run. You can refresh that snapshot nightly. Copy-on-write gives each environment its own instance without duplicating the full dataset.

Do I have to change my Compose file?

No. VeilStream turns your existing Docker Compose file into isolated containers. Keep the repository and Compose file 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.

How is this different from Vercel, Render, or Neon?

Those tools each cover part of the problem — a preview URL, a Docker host, or a database branch. VeilStream combines a live URL with a sanitized snapshot database and the same access rules for people and agents. See the comparison.

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.

A preview your AI can actually use.

Connect your repository and Docker Compose. Your next pull request gets a live URL, a sanitized database, and scoped access for people and agents.

First $20/month free. No credit card.

Get started Read the quickstart