Engineering depth, from the plant to the architecture.
We’re an experienced network engineering practice. We bring carrier-grade experience across the whole network stack to every engagement, and the engineer who scopes the work stays with it through handover.
Too many architects have never pulled cable, and it shows: they design networks that punish the people who do. We built Subiaco Networks after working the full stack ourselves, from outside plant and the switch room to the NOC, the tower and the architecture review. The drawings reflect it. So do the migrations.
Gabriel Moreno
Founder & Principal Network Architect
I’ve spent more than twenty years on AT&T and Verizon networks, in MTSO operations, outside and inside plant planning, Tier 2 NOC leadership, and network engineering. Most recently I engineered backhaul and transport for a Verizon Wireless market in California: router migrations, 5G capacity turn-ups, backhaul upgrades, acceptance testing and monitoring recovery.
I’m a lifelong learner, on the job and off it: six engineering disciplines, graduate coursework in information systems, and a philosophy degree that trained me to reason from first principles. For you, that means two things. Every design ships with its reasoning written down, and my time as adjunct faculty at Reedley College means I’m practiced at explaining a network to the people who have to run it. By the time I hand it over, your team doesn’t just have a working network. They understand it.
I started Subiaco Networks so operators can get that depth without a full-time hire, from the engineer who actually does the work. When you reach out, the reply comes from me.
Gabriel Moreno, Founder & Principal Network Architect
Every layer, worked from the inside.
The difference between a consultancy that draws diagrams and a practice that has been on the other end of them, at 3 a.m., during a maintenance window, with traffic on the line.
Design & consulting.
Architecture · automation · orchestration · teaching
Designs informed by every layer below, with Linux, Python and Bash depth that lets a small practice operate like a much larger one. The practice that became Subiaco Networks.
Platform & systems engineering.
Nokia SR OS · Ciena · Ericsson · Juniper MX960 · Telcordia audits
Deep, hands-on time on carrier platforms: failure modes, upgrade paths, and how each platform’s internals shape what the network can actually do.
Cutover & turn-up.
Router migrations · RAN turn-up · microwave & fiber backhaul · on-call
We executed cutovers in maintenance windows, turned up 5G capacity, upgraded backhaul, and proved circuits with RFC 2544 and Y.1564 before accepting them.
Switch room & NOC.
MTSO operations · 5ESS · DMS-100 · SS7 · Tier 2 NOC lead
We kept voice switches and signaling healthy, led NOC escalations, and learned how networks actually fail under live load.
Outside & inside plant.
Fiber · copper · central office · OSP/ISP planning
We planned the plant, lit circuits, and learned that documentation saves you at 3 a.m. and that nothing beats labels on the patch panel.
Subiaco, below the lake.
Subiaco is a town in the hills east of Rome. Its Latin name, Sublaqueum, means “below the lake”: Roman engineers dammed the Aniene river there, and under Trajan those lakes became settling reservoirs for the Anio Novus, one of the aqueducts that carried water to the city.
Centuries later, in 1464, the monastery of Santa Scolastica at Subiaco housed the first printing press in Italy.
Infrastructure and information, carried a long way, built to last. It’s a good name for a network practice. The globe in our mark is lit at the surface and deepens below it, because most of the work that keeps a network running lives where customers never see it.
Six principles, no exceptions.
If it isn’t written down, it didn’t happen.
Every design ships with the HLD, LLD, IP plan and runbook. The next engineer needs to read it and know what to do.
Proven, then production.
Baselines before the change, validation after it, and acceptance tests with raw data. We model failure before we trust success.
The right gear, not our favorite gear.
Nokia, Ciena, Ericsson, Cisco, Juniper, open source. Recommendations match the requirements, not a partnership tier.
If it’s done twice, it gets a script.
Python, Bash, Ansible, NETCONF, Git. Repeatable, reviewable, reversible.
The 5ESS still routes calls.
Migration plans honor what’s running. We don’t rip out what works just because it’s old; we plan the orderly handoff.
The engineer who scopes it does the work.
No handoff from the person who scoped the work to a junior team. The person on the scoping call is the person in the maintenance window.
The platforms we work on.
Vendor and former-employer names describe experience only and don’t imply endorsement or partnership.
Let’s talkBring us in early. Or bring us in when it’s broken.
Either way, we show up the same. Pick a package or ask for something custom.
Get in touch