The Manifesto
Why we believe skilled IT labor is becoming a utility
Electricity used to require a person standing next to a generator. Now it arrives through a wall socket, metered by the hour. Skilled IT labor is on the same trajectory.
System, database, and network administration have historically resisted automation for one simple reason: the hardware was physical. You couldn't script a server rack. But that constraint is gone. Servers, routers, and switches have been reduced to JSON — infrastructure-as-code, API-driven, fully addressable by software. The last barrier standing between these jobs and full automation was never the skill involved. It was the hardware.
This has happened before. Lamplighters, telegraph operators, and NASA's human computers — the people who once performed complex calculations by hand — all disappeared not because their work stopped mattering, but because a new process could do it faster, cheaper, and without fatigue. The knowledge they carried didn't vanish. It got encoded into something that could run without them.
That's what's happening to system and database administration now. The role isn't disappearing because it was unimportant — it's disappearing because the knowledge behind it can finally be codified: ITIL-aligned, risk-mitigated, cost-contained, and applied consistently regardless of vendor or platform.
Replayable is that codification.
Instead of hiring and managing a team of administrators, you flip a switch. What used to require a hundred-person team of top-tier system and database administrators — provisioning, patching, tuning, compliance, incident response — runs as premium automation inside your existing infrastructure, at a fraction of the cost and without the headcount overhead.
The knowledge doesn't disappear. It gets replayed, consistently, every time — the same best-practice judgment a senior DBA would apply, without needing that DBA on staff.
This starts with Oracle — the deepest, most operationally demanding environment to automate — and extends outward from there. The same codified judgment is built to move across engines and platforms, because the labor being replaced was never Oracle-specific. It was the discipline itself. See our Oracle-to-AWS migration roadmap for where that expansion is headed next.
This isn't a new idea for us, just a bigger frame for one we already hold. Read our Three Laws of Automation for the operating rules this manifesto implies in practice.
Want to see the codification, not just the argument? Explore the technology, or watch the demo. Contact us if you'd like to talk it through.