Start another worktree without rebuilding your local setup.
Small engineering teams running parallel agents against a stateful local stack.
This is an early product concept currently being validated. The product is not yet available.
The problem
Each checkout needs its own ports, database state and services. Cleaning up is another manual job.
What happens today
Maintain shell hooks, copy environment files and allocate ports by hand.
What I’m exploring
I’m exploring a tool that would offer: a repeatable recipe for one supported local stack that creates and removes branch-specific services.
- Keep branch services separate
- Reuse a working setup recipe
- Clean up resources with the checkout
These are proposed outcomes. There is no launch date yet.
Proposed early-access price
Would this save you enough time to be worth paying for? That’s what I’m testing.
$39 / month
No payment is collected. No subscription starts.
Would you use this?
If this is a problem you deal with, tell me a little about your workflow. Joining is an expression of interest. It does not start a subscription.
Please keep client details, credentials and confidential information out of your answers.
If your current tools already handle this, say so.
I want to understand what’s missing before I build anything. Your answers help me decide whether this deserves a next step. — Kai
Optional click and scroll mapping. No form contents, recordings or mouse trails. Basic page and signup funnel events are recorded separately.