Every change runs as a signed, owner-approved plan — from a PR preview or the dashboard — and your providers' credentials never leave your own infrastructure.
Automate pull-request previews in GitHub Actions, or plan environments in the control plane and let your runner apply them—Docker, your laptop, or any CI that can poll.
GitHub Actions
A pull request opens. A full preview appears.
Neon, Upstash Redis, Vercel Hosting, Stripe, and a GitHub environment for each PR.
1
PR opened
#481 · feat/checkout
2
Services provisioned
DB, Redis, deploy, webhook
3
Preview URL ready
pr-481.preview.example
4
Automatic cleanup
Expires in 7 days
Sample · PR #481feat/checkout
Ready
Neon branchReady
Upstash RedisReady
Vercel HostingReady
Stripe webhookReady
https://pr-481.preview.example
Cleanup in 7 daysSample data
Optional: view the signed plan behind this preview
Each step has a clear input and a tangible output.
1
Describe
BlueprintNamed environment template
List the services each preview needs and how their outputs connect. Every new environment gets its own copy from just a name.
2
Review
Proposed changesEd25519-signed plan
Owners see exactly what will be created, attached, or deleted—and approve it—before anything runs.
3
Apply
Signed planLive preview resources
Your runner verifies the Ed25519 signature, checks each adapter’s SHA-256, and executes with credentials only it holds—never sent to EnvTie.dev.
4
Retire
Expiry or destroyProvider cleanup verified
Environments expire on schedule. Destroy is checked against each provider so nothing lingers on your bill.
Security and control
We never store credentials or tokens
Provider keys stay on your runners. EnvTie.dev stores resource IDs and Ed25519-signed plans—not secrets—and runners pin adapters by SHA-256.
What EnvTie.dev stores
Workspace, project, and member names
Blueprints, with secret-shaped values rejected
Provider resource IDs and status
Ed25519-signed plans and the activity log
What we never store
Provider API keys and tokens
Database passwords and connection strings
Webhook signing secrets
Generated .env files
Technical evidence: Ed25519 plans and SHA-256 adapters
Every change is an Ed25519-signed plan bound to your workspace. Runners refuse anything unsigned, expired, or tampered with, and verify each adapter binary against its pinned SHA-256 before execution. The control plane never stores provider credentials or tokens and rejects secret-shaped blueprint fields before they are saved.
Official adapters cover common preview stacks. Custom providers use a small JSON protocol—bring what you already run.
No credentials or tokens stored
Provider API keys and tokens never leave your runners. The control plane keeps resource IDs only and rejects secret-shaped blueprint fields.
Ed25519-signed plans
Every change is an immutable Ed25519-signed plan bound to your workspace. Runners refuse anything unsigned, expired, or tampered with.
Automatic expiry
Set a lifetime per blueprint. Expired previews are destroyed for you, and protected environments need typed confirmation.
SHA-256–pinned adapters
A GitHub Action, a distroless Docker image, or a single CLI binary. Runners verify each adapter’s SHA-256 before execution.
Adapters for your stack
Neon, Upstash Redis and Vector, Stripe, Sentry, Mailtrap, Resend, Vercel Hosting and Blob, and GitHub out of the box, plus a small JSON protocol for your own.
Built for teams
Invite teammates by email, separate owners from members, and see every approval and change in the activity log.
Pricing
Start free, upgrade when your team does
Free
For individuals trying EnvTie.dev.
$0/ month
3 active environments
1 runner
3 members
All built-in and custom adapters
Signed plans and owner approval
Automatic expiry with verified destroy
Activity log
Team
For teams running previews on every pull request.
$49/ month
25 active environments
5 runners
20 members
Everything in Free
25 active environments
Runners in GitHub Actions, Docker, or CLI
Email support
Business
For organizations with many projects and strict review.
$199/ month
Unlimited active environments
Unlimited runners
Unlimited members
Everything in Team
Priority support
Provider resources (Neon, Upstash, Vercel, Stripe, etc.) are billed separately by those providers; tier limits here count EnvTie environments only.
No. EnvTie.dev does not store provider credentials or tokens. Runners read them from their own environment and send back only sanitized resource identifiers. Blueprints containing secret-shaped values are rejected before they are stored. Plans are Ed25519-signed; adapters are verified by SHA-256.
What counts as an active environment?
Any environment that has been planned and not yet destroyed. When an environment is destroyed, manually or by expiry, it stops counting toward your subscription tier.
What happens when an environment expires?
EnvTie.dev queues a signed destroy plan. The next time your runner polls, it deletes the managed resources, keeps referenced ones, and reports back.
Can I self-host EnvTie.dev?
The customer-side CLI, runner, adapters, SDK, and contracts are open source under Apache-2.0 in github.com/coddicat/envtie-core. Contact us about hosted-control-plane deployment.
Can I change or cancel my subscription?
Any time, from Billing in the dashboard. Upgrades take effect immediately with prorated charges; cancellations apply at the end of the billing period.
Founder
Rodion Shlomo Solomonyk
Founder of EnvTie.dev
Co-Founder & CTO at Click Clarity AI. Hands-on across software engineering, architecture, DevOps, and scalable distributed systems—fintech, cybersecurity, and SaaS.