Drift.
Settings kept consistent
Catch "works here, breaks there" before launch.
One of fifteen tools the studio built for its own work. We build the same kind of app for clients, shaped around the job they need doing.
- Made for
- Stopping the test and live copies of a system drifting apart
- Shape
- Native Mac app
- Data
- Stays on the machine
- AI inside
- None: deliberately mechanical and predictable
What Drift does.
Most systems have different settings on a laptop, in testing and on the live site. When those copies drift apart, something works in one place and fails in another, often just before launch.
Drift compares every copy, flags missing or unsafe settings and fills gaps without overwriting existing values. It always takes a backup first.
This one is for technical teams: if you run a test copy of a system beside the live one, the differences get found on purpose rather than at launch.
Why we built Drift.
The difference between the laptop, test and live copies always takes a morning to find, and always on the morning you can least afford it.
Worse, some drift is dangerous: debugging left switched on in a live system, an empty database password nobody noticed. Drift exists to catch both kinds early.
How Drift earns its place in a working day.
Point it at a project
Every settings file is found automatically, and each copy is recognised for what it is: local, test, or live.
See them side by side
A comparison grid flags what's missing, what differs, and what looks unsafe, at a glance, not by eyeballing files.
Fix the gaps safely
Missing values are added (and only added, never overwritten) with a backup taken first, every time.
Check before launch
Nine safety checks catch dangerous settings on live systems, from debugging left on to blank passwords.
Launch mornings got calmer
The settings check is minutes of looking at a grid instead of a nervous read-through of files.
Unsafe settings are flagged
Fixed checks find dangerous live settings before a customer encounters the consequences.
Every fix is reversible
Backups before every write mean a wrong fix costs seconds, not an incident.
Made to fit the work it needs to do.
Drift is deliberately mechanical: no AI, the same answer every time. Its one design rule is that the preview always matches exactly what gets written; a tool that touches live settings has to be incapable of surprising you.
A security review of the app itself led to a round of hardening before we trusted it with client projects. We audit our own tools the way we audit client systems.
Could your business use something like this?
Tell us the job in plain English. We'll say what would solve it, what it would cost, and whether a desktop app is the right shape for it.