Nicholas Crew Ferguson
I build the infrastructure nobody has to think about, which is ideal, because most people would rather not.
Engineer, open-source builder, and the person behind Atlas Crew. Based in Tampa Bay, walking into systems held together by folklore, fear, and one person's memory, then rebuilding them to run without me.
About Me
Who I am and how I got here. A decade of walking into broken infrastructure until the same pattern turned into a methodology.
Background
I've spent a decade walking into infrastructure nobody loved.
At Vispero, I was the first platform hire. The role existed because four acquired companies had four different build systems, four different release processes, and one shared problem: getting software out the door had become a slow-motion group exercise in suffering.
At A10, I inherited a SaaS platform with no infrastructure-as-code and per-customer VPCs casually burning six figures a month, because at some point someone decided the path to 100% security was giving every customer their own tiny isolated kingdom and simply accepting the financial consequences.
The pattern is usually the same: systems that were never really designed so much as assembled reactively, one disaster at a time, with layers of process, approvals, and strange little rituals added afterward so the people who should have prevented the disaster can point at something and say they addressed it. Eventually the whole thing calcifies into "the way we do things," and the team lives with it long enough to mistake survival for stability.
"Experienced" means you inherit the Whoville machine with no manual, no tour, and three different people saying, "I think that part is owned by another team." By week two, you're expected to know which lever ships the cupcakes, which lever starts the fire, and why the fire has its own checklist.
I absorb the context, map the machinery, separate the dangerous parts from the merely stupid ones, rebuild the platform, document what actually matters, and hand it off in a state where other people can operate it without needing a séance.
The infrastructure I build outlasts me. It keeps running in production long after I've moved on. That's not a side effect. That's the point.
Along the way, I started building open-source tools for the problems I kept running into: security testing, career intelligence, AI-augmented development, and the general problem of making complex systems usable by people who have other things to do. Those projects became real products: Synapse, Chimera, Crucible, Facet, and Cortex. Atlas Crew became the umbrella that ties them together.
Why Atlas Crew
Atlas Crew started as a consulting identity and grew into something larger: a home for the products, tools, and frameworks I build in the open.
Why "Atlas Crew"
The name is personal. My middle name is Crew. And my great-great uncle was Charles Atlas, the strongman who built an empire on the idea that anyone could become stronger than they thought possible.
Atlas holds up the world. Crew is the team that does the work. Infrastructure engineering is exactly that: carrying the weight so everyone else can move fast without thinking about what's underneath. The family connection wasn't planned, but it fits.
Everything under Atlas Crew ships with the same philosophy: build it to run without you, document it like you're leaving tomorrow, and open-source it so the next person doesn't have to start from zero.