Launching today
EnvTie
Real resources for every PR preview, destroyed on merge
3 followers
Real resources for every PR preview, destroyed on merge
3 followers
EnvTie provisions the external SaaS resources your app depends on for every environment. How it works: • Opening a PR produces a plan — an exact, reviewable list of what will be created. The plan is cryptographically signed and approved by the owner before anything runs. • A runner that lives in YOUR infrastructure executes the plan. Your providers' credentials never reach EnvTie's servers. • Close the PR, and every resource is destroyed — Leftovers surface as residuals.





Launch Team

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted
Hi Product Hunt
I'm Rodion, the maker of EnvTie. I built it because of an archaeology problem every team I worked on had: preview environments are easy to create and almost never cleaned up. Dead Neon branches, forgotten Redis instances, Stripe test objects and Sentry projects from PRs merged months ago — still alive, sometimes still billing.
The existing tools solve the "deploy the app" half. I wanted the other half: the external services the app depends on, provisioned per pull request from one blueprint — and, more importantly, provably destroyed when the PR closes. In EnvTie, "destroyed" means the runner deletes the resource and then reads it back from the provider's API. If it's still there, you see a residual, not a green checkmark you have to trust.
Two design decisions I'm most stubborn about:
Your credentials never come to us. The runner runs in your infrastructure and reads provider keys locally. EnvTie's hosted side only ever sees plans, statuses and resource IDs — never secret values.
Nothing runs unsigned. Every change executes as a plan that is signed and approved by the workspace owner first — so an AI agent or a CI job can propose environments, but a human-approved, verifiable document is what actually executes.
The core is open source (Apache-2.0) — the part that runs in your infrastructure is the part you can audit. The hosted product is what I charge for.
EnvTie has been live for a few weeks, so this is early and I know it. I'd genuinely love feedback: which provider should the next adapter be (Supabase is the current frontrunner), and what would make you trust — or not trust — a tool like this next to your infrastructure?
Free tier is live at envtie.dev. Full 6-minute walkthrough (setup → preview → verified teardown) is in the gallery.
Thanks for looking,
Rodion