About
BrightNet Technologies is a single-operator consultancy — not a brand name over a rotating bench of subcontractors. That's a deliberate choice, not a limitation.
Most small and mid-sized organizations don't need a full IT department — they need a handful of things done correctly: a network that stays up, a security posture that holds up to scrutiny, and a backup plan that actually works when it's tested. What they usually get instead is whichever combination of a managed-services contract, an overworked internal generalist, and inherited configuration nobody fully understands.
BrightNet was started to close that gap directly. Two decades of managing enterprise and nonprofit IT environments — including the kind of always-on infrastructure that broadcast and media operations depend on — went into the discipline behind how engagements here are run: assess before designing, design before building, and document everything well enough that the organization never depends on one person's memory of it, including mine.
Alongside consulting, I teach information systems at the college level — partly because explaining a concept clearly to a room of students is one of the fastest ways to find the gaps in your own understanding of it.
The experience BrightNet's engagements are built on.
Hands-on management of networking, virtualization, and security for organizations where downtime isn't an abstraction — including always-on broadcast and media environments.
Day-to-day responsibility for the infrastructure decisions this site talks about — network design, security hardening, and disaster recovery — not just advising on them from the outside.
Teaching networking and systems coursework at the college level, keeping both the fundamentals and the explanations sharp.
Graduate business education layered onto a technical career, with a dual undergraduate business background from Kennesaw State University.
Four commitments that don't change based on the size of the engagement.
The person who assesses the environment is the person who designs the fix and the person who implements it — not three different people reading the same file.
Redundancy, tooling, and process get recommended where the risk justifies the cost — not as a default upsell built into every proposal.
A backup job that's never been restored isn't a backup plan. Claims about what a system will do under failure get verified before they're relied on.
Diagrams, configurations, and credentials are handed off in full. An engagement that ends shouldn't leave you locked out of your own environment.
A short call to understand what's running today and where the real risk sits — no obligation to continue past that.
