Trailswitch is built by one developer.
It exists so you can run the one service you are changing on your machine, keep everything else on QA, and never edit appsettings to do it.
The problem
On a microservice team you rarely run the whole system yourself. One or two services run on your machine while you change them, and the rest live in a shared QA environment. When a response looks wrong, the question is always the same: is it my code, or is it the environment?
Testing a local change against the rest usually means editing base URLs in config, restarting, and remembering to undo it. Trailswitch puts one proxy in front of your services so each service can point at your machine or at QA on its own, with a click. Every request is captured along the way, and any of them can be replayed against QA and diffed when local and QA disagree.
How it is built
It is a desktop app for Windows today, with macOS and Linux coming. Requests you capture are stored on your own PC and leave it only when you export them, replay them, or let an AI model you connected read them.
Where it is today
Trailswitch is in early access. There is no public download yet. If you want to try it, send a line about your setup through the contact form and I will get back to you.