Tidal Locking and the Orbital Mechanics of Vendor Lock-in

Thu, 25 Jun 2026 06:16:05 +0000

Mercury is tidally locked to the Sun — but not synchronously. It settled into a 3:2 spin-orbit resonance: captured, but still spinning. That distinction turns out to be the only realistic vendor strategy most engineering organizations have.

Mercury takes 59 Earth days to rotate once and 88 to orbit the Sun. Work out sunrise-to-sunrise and a single Mercury day lasts 176 Earth days — exactly two Mercury years. That isn't a quirk of astronomy. It's a clue, because the physics that locked Mercury is the same physics that locks an enterprise into its vendor stack.

The vendor doesn't chain you. It reshapes you.

Tidal locking begins with deformation. A planet's gravity isn't uniform across a moon's diameter — the near side feels a stronger pull than the far side. That gradient stretches the moon into a slight ellipsoid, and the bulge is the mechanism. The moon isn't chained in place; it's reshaped until its own structure enforces the lock.

Vendor lock-in works identically. An organization that adopts a major platform doesn't get chained to it — it gets reshaped by it. Staff certifications align with the vendor's curriculum. Data formats nest inside proprietary schemas. Runbooks, hiring profiles, and architecture diagrams all deform toward the platform's shape.

Nobody notices the lock forming, because the reshaping feels like optimization. You're getting better at using the tool. Your team is more efficient. The integration is tighter. All true — and that is exactly how tidal locking works. The deformation that traps you is indistinguishable from getting good at the thing.

1:1 vs. 3:2: the only escape that exists

Our Moon is in a 1:1 resonance — same face toward Earth forever. Total capture. Mercury is in 3:2: three rotations for every two orbits. Still captured by the Sun's gravity, but never fully frozen. It keeps rotating.

That's the realistic target for most teams. You will not "avoid" lock-in with a sufficiently clever abstraction layer — the gravity is real and the deformation is continuous. What you can engineer is a 3:2 resonance instead of 1:1: stay captured by the platform you depend on while preserving enough independent rotation that no single face is frozen toward it forever.

Concretely, preserved rotation looks like:

Portable data formats at the boundaries. Proprietary internals are fine; proprietary exports are the lock.
Skills that transfer. Train people on the underlying discipline, not only the vendor's console.
An exit you've actually rehearsed. A migration plan you've never run is a wish, not a resonance.
More than one gravitational source. A second small dependency keeps the system spinning.

The assumption is the bug

The lesson the orbital mechanics drives home is that capture is not a moral failure or a procurement mistake. It's the default state of any system under a strong, persistent gradient. The question is never "are we locked in?" — you are. The question is which resonance you're in, and whether you still rotate.

This post was originally published on the Vibe Agent Making blog, where I write about agent systems, engineering, and the strange places good metaphors come from.

Coder Legion - Recent posts tagged engineering-strategy

Tidal Locking and the Orbital Mechanics of Vendor Lock-in

The vendor doesn't chain you. It reshapes you.

1:1 vs. 3:2: the only escape that exists

The assumption is the bug