A church recently moved their offices from a shared office environment into their own dedicated space and I was asked to help design the infrastructure.

With the move, they needed their own infrastructure—Internet connection, firewall, wireless infrastructure, cameras, and proper segmentation. While the space isn't big enough to house their worship center, the new square footage allowed it to function as an office as well as a ministry center — hosting small groups, Bible studies, leadership meetings, and community gatherings.

Not a full worship center, but also not just an office either — That shaped the design.

The Stack

To keep management unified and simple, the stack was built around a consolidated Ubiquiti UniFi deployment:

  • Dream Machine Special Edition (UDM-SE) as the gateway and controller,
  • Pro Max 16 PoE (USW-Pro-Max-16-PoE) for switching and power distribution
  • U7 Pro Access Point for wireless coverage
  • G4 Dome cameras tied into Protect for surveillance.

The goal wasn’t brand loyalty. It was operational simplicity. Everything lives in one ecosystem, which keeps management clean and remote support realistic.

The Process

I sent links to the infrastructure gear to the leadership team at the church for approval and purchase. Once the parts list arrived, I asked Bradbury Productions to help me with cabling and rack mounting.

I created the VLANs and firewall rules and went back after Spectrum had finished installing their internet connection to finish up SSIDs, cameras, admin permissions for UniFi Protect and, made sure everything was working properly.

Why Not a Mesh System?

Modern consumer mesh systems are excellent — in homes. But this an office that hosts staff during the day and anywhere from 30 to 80 people days when it doubles as a ministry center. There are guest devices, streaming traffic, Zoom calls, and security cameras in the mix.

The network needed proper VLAN segmentation, clean firewall rules, PoE switching, and meaningful visibility into usage.

Is the Design Overkill?

An average weekday might see ten connected devices. A ministry night might see thirty or more.

The network was not designed for the quiet hour. It was designed for the busiest one.

We wanted wireless to be stable, it needed to handle variable client density and mixed device types. It also needed enough lifecycle runway to avoid feeling outdated in a couple of years. Nonprofits stretch infrastructure longer than most environments. That reality should shape the hardware decisions.

And because it also serves as a ministry center, expectations shift. Cameras, Segmentation and, Guest isolation are no longer optional.

We’re no longer designing for five employees; We’re designing for community access. That changes the risk profile. The infrastructure needs to quietly support ministry without becoming a source of friction or instability.

The goal was to build something dependable and scalable when they outgrow the current space.

When the church decides to move offices or move into a building that can house a full worship center, this infrastructure doesn’t become obsolete. The gateway, switching, cameras, and access points can all move with them. Additional APs or switches can be layered in as the footprint grows, but the core architecture remains intact. It’s not a temporary solution, it’s a foundation they can build on.

Remote Management

An important factor in this design is that I’m not full-time staff onsite.

If something needs attention, it has to be visible and manageable remotely. The system needed to provide live client visibility, bandwidth monitoring, firmware control, VLAN adjustments, and camera health checks without requiring someone to power-cycle equipment in a closet.

Conclusion

Moving from shared infrastructure to owning your own network isn’t just a technical shift, you're now responsible for your infrastructure and dictate how stable and reliable it is.

For a church office that now doubles as a ministry center, the goal wasn’t to build something impressive. It was to build something dependable — infrastructure that quietly supports people, gatherings, and community without drawing attention to itself.

When infrastructure aligns with mission, it disappears into the background.

And that’s exactly where it belongs.