Skip to content

Introduction

pfCentral is a self-hosted console for a fleet of pfSense firewalls. You manage firewall rules, NAT, VPNs, interfaces, services and diagnostics for every firewall from one web UI or API. You do not log in to each firewall, and you do not open a port on any of them.

pfSense · bne pfSense · syd pfSense · mel NATS pfCentral server + UI + postgres outbound only bne syd mel outbound NATS pfCentral server + UI + postgres
  • MSPs and IT teams that run pfSense at many sites: branches, shops, clients, data centres.
  • Network admins who want one place to see which firewalls are online, and to make the same change on many of them.
  • Security teams that cannot expose firewall web GUIs or SSH to a central network.

You do not need to know NATS, Go or Kubernetes. The docs explain each new idea when you first meet it.

PromiseWhat it means for you
No open portsA small agent on each firewall dials out to the server. Firewalls behind NAT, CGNAT or a strict upstream router work.
Self-hostedThe server runs on your hardware or cloud. It works without internet access.
One consoleRules, aliases, NAT, VPN, DHCP, DNS, routing, packages and diagnostics for every firewall.
Teams and rolesOwner, admin, operator and viewer roles, enforced on every page and API call.
UI and APIEverything you can click, you can also script. The API explorer is built in.

The docs follow the order in which you meet pfCentral:

You need:

  • A Linux host or Kubernetes cluster that can run a container. A small VM is enough for a small fleet.
  • PostgreSQL. The quickstart starts one for you (PostgreSQL 17).
  • One or more firewalls on pfSense 2.7.0 or later (amd64). Each must reach the server on TCP port 24222, and on the web port once to enroll.

Ready? Read How pfCentral works for five minutes, or go straight to the Quickstart.