Municipal IT resource
Technical answers for public Wi-Fi that stays out of your way.
A practical FAQ for the network, security, operations, and compliance questions that matter before a public-access network moves forward.
A clear technical path
Public connectivity can be a civic service, not another burden on an already stretched team.
Use this guide to address the questions that sit behind the approval process, then move into a focused technical review with the people who run the service.
01
Architecture and staff impact
- Does this touch our internal network?
- No. CivicConnect is deployed as a physically and logically isolated overlay, with dedicated VLANs or VRF, separate public IP space, and no routing into the municipal LAN. It requires one Layer 2 handoff at the point of presence or a 1G-plus backhaul circuit.
- What does our team actually have to do?
- The initial work is a 60-minute design review and approval of mounting locations. Ongoing work is viewing the dashboard, plus an optional 15-minute monthly operations review. Provisioning, RADIUS, patching, and RF tuning are managed by Anaptyx CivicConnect.
- How is support handled?
- Tier 1 through Tier 3 support is included. Public users reach the helpdesk through the splash page, while the municipal NOC has a separate line. The service includes 24/7 monitoring, with a target acknowledgement under 15 minutes and a target restoration time under four hours.
02
Security and privacy
- What is the security model?
- The public network uses WPA3-Enterprise or OWE for open access, client isolation, Layer 2 and Layer 3 access controls, edge IDS and IPS, and automatic CVE patching within 48 hours. Logs can be forwarded to a SIEM through syslog when requested.
- How are privacy, CALEA, and content filtering handled?
- The service retains no personally identifiable information beyond anonymized session logs needed for BEAD. DNSFilter adds DNS-layer threat protection, public-setting content controls, and useful activity visibility. CIPA-compliant DNS filtering is included, and a CALEA-ready intercept point is available when required. Municipal traffic is not inspected.
03
Hardware and infrastructure
- Who owns the hardware and how is it refreshed?
- Anaptyx CivicConnect owns the hardware during the term, including Wi-Fi 6E outdoor access points, cabinets, UPS equipment, and mounting. A five-year refresh cycle is included, with RMA spares stocked within 50 miles of the city.
- What does installation require from the city?
- The service uses existing streetlight and traffic poles where appropriate, with an average draw below 45 watts per access point. Anaptyx CivicConnect provides PE-stamped drawings and coordinates with the utility. Most sites do not require a new electrical service.
04
Ten-year BEAD accountability
- What reporting is covered?
- Quarterly support includes FCC Broadband Data Collection availability, verified speed and latency testing, uptime reporting, low-cost plan availability logs, Letter of Credit evidence, and Build America, Buy America documentation for hardware.
- What happens if there is an audit?
- Anaptyx CivicConnect maintains immutable 10-year logs in WORM storage and contractually indemnifies for compliance-documentation failures attributable to its service.
- What happens after the BEAD term?
- At year 10, the city receives a quitclaim to installed infrastructure at no cost, together with as-builts and administrative credentials. The city can also renew managed service at a reduced rate.
For the technical review
Bring the difficult questions. We will bring the operating detail.
Start with one location, a technical review, and the conditions your team needs before it can sign off.