From Fork to Framework
How AOCyber's platform got built: the rewrites, the stacks that lost, and the ones that won. A seven-part engineering history with the reasoning kept in.
A build log rather than an argument. Seven parts on how the AOCyber platform went from a fork of someone else’s project to a framework of its own — and on the decisions that looked obvious in hindsight and were not obvious at the time.
Python and Svelte first. Rails almost won the backend. Go won it instead, and Flutter won the frontend. ConnectRPC and a shared library layer turned the result into something that pays for itself on each new product. The last part covers the tooling — Claude Code and DevFlow — that made the pace possible.
Each part keeps the reasoning, including the paths not taken.