Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

VeilStream

Per-Branch Preview Environments

Details

External ID
46874014
Source
HN
Company
—
Product
VeilStream
Website domain
veilstream.com
Launched
Feb. 3, 2026
Cohort
—
Upvotes
6
Upvotes percentile
0.28099730458221023
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

# Show HN: VeilStream - Per-Branch Preview Environments## Optionally with sanitized production dataI've been building VeilStream to solve a problem I kept running into: Rigorous evaluation of changes, such that they won't break production is hard. Staging is shared and often broken. Pulling to local setups are a pain. So PRs get a quick code skim and a "LGTM." VeilStream spins up isolated preview environments from your `docker-compose.yml`, (optionally) complete with a sanitized snapshot of your production database.## What happens when you open PR #2471. GitHub webhook hits our API2. We pull your branch and parse your compose file3. Kubernetes manifests render from your compose services (and applied to our cluster)4. A fresh namespace gets created with your containers5. Optionally, postgres containers are seeded with your data6. Health checks pass, you get a stable URL: `https://<unique-string>.env.veilstreamapp.com`7. that link is commented back on any open PRs from that branchTotal time from push to working environment: about 2 minutes.### The reviewer experienceYour teammate clicks the link. They're using your app with real data structure, real relationships, real edge cases—but emails are fake, SSNs are masked, and PII never leaves your production boundary.No shared staging. No "wait, who's testing on staging right now?" No stepping on each other's test data. No risk to prod.### When PR #247 gets merged or closedThe namespace, containers, and database are automatically destroyed. Nothing lingers.## What it's not- Not serverless/edge - this is for apps that run containers- Not a Vercel competitor - we're focused on the full stack from a docker-compose perspective- Not a database replication tool - the proxy works like a man-in-the-middle, not on the WAL## MCP Server for AI AgentsWe built an MCP server so Claude Code, Cursor, and other AI coding agents can deploy preview environments directly. Your agent can spin up an environment, run tests against it, and tear it down—all without leaving your editor.## Tech Stack- Backend: Go (API + reconciler)- Frontend: React + TypeScript- Infrastructure: Kubernetes, with dynamic namespace provisioning- Database proxy: Custom Go proxy that interfaces with a database, and exposes the standard psql wire protocol, mimicing a server## Links- Landing page: https://www.veilstream.com- Application: https://app.veilstream.com- Example project: https://github.com/veilstream/example-music-company- Demo video: https://www.linkedin.com/posts/jonessteven_i-have-only-made-...- Docs: https://docs.veilstream.comHappy to answer questions.Also: htaccess-style password protection is available for your preview environments.

Enrichment

Theme
database infrastructure and developer tools
Vertical
Horizontal
Function
Dev tools
Audience
Developer
AI stance
Not AI
Project type
Commercial product
Normalized one-liner
preview environments for branches
Manually corrected
False

Could you build this?

Partial While orchestrating Docker Compose and spinning up ephemeral environments via webhooks is standard, reliably snapshotting production Postgres with deterministic, foreign-key-preserving PII masking and fine-grained proxy credentials requires complex data infrastructure.

What it would actually take: Building VeilStream requires an infrastructure orchestrator (Docker/Kubernetes) to dynamically spin up per-branch container stacks, coupled with a Postgres proxy or wire-protocol parser (like pgproto) for on-the-fly MCP query gating. The hardest engineering challenge is building the database sanitization engine, which must parse relational schemas, maintain referential integrity across masked columns, and rapidly clone multi-gigabyte databases via copy-on-write storage (like ZFS or EBS snapshots). This demands senior DevOps and database systems expertise.

Discussion

No comments on this launch.

Competitors

Other products that read as similar to this one — 45 launches clear the similarity bar, closest 8 shown.

Attention rank: #40 of 46 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 96 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a dev tools tool for Sales yet.