OPNsense does not need a powerful computer. The official hardware guide defines three tiers: a minimum of a 1 GHz dual core CPU, 3 GB of RAM and a 4 GB SD or CF card; a reasonable setup with 4 GB of RAM and a 40 GB SSD; and a recommended setup with a 1.5 GHz multi core CPU, 8 GB of RAM and a 120 GB SSD. Which tier you actually need depends less on OPNsense itself and more on the services you plan to run on it, so this guide walks through each tier, explains what it can and cannot do, and helps you match your hardware to your connection and your plans.
The three official tiers at a glance
The sizing figures below come straight from the official OPNsense hardware documentation. They are not estimates from a forum post or a vendor brochure, and they are the same numbers the project itself uses when it describes what a new installation should look like.
| Tier | CPU | RAM | Install target |
|---|---|---|---|
| Minimum | 1 GHz dual core | 3 GB | SD or CF card, minimum 4 GB, using the nano image |
| Reasonable | 1 GHz dual core | 4 GB | 40 GB SSD |
| Recommended | 1.5 GHz multi core | 8 GB | 120 GB SSD |
Two details in that table are easy to miss. First, the minimum tier is tied to the nano image and removable flash media, which makes it a special case with real limitations (covered below). Second, the installer itself needs a minimum of 3 GB of RAM just to run, so a machine with less memory than that cannot complete a standard installation at all, no matter how light your intended workload is.
What the minimum tier can and cannot do
The official guide is precise about the minimum tier: it runs all standard features that do not need disk writes. Routing, NAT, the packet filter, DHCP, DNS and VPN endpoints all work fine at this level, because they live in memory and configuration rather than on the disk.
The features that fall outside the minimum tier are the ones that write to storage continuously. The documentation names two examples: a caching proxy, which stores web content on disk, and the IDS/IPS alert database, which records intrusion detection events for later review. If either of those is on your shopping list, the minimum tier is not for you, and neither is the nano image that goes with it. Our nano image guide explains those embedded limits in full.
There is also a practical comfort issue. A minimum spec box leaves very little headroom. The moment you add a few plugins, enable detailed logging or hand the firewall a busy network, you are working at the edge of what the hardware can do, with no room for the unexpected.
Match the tier to your connection speed and user count
The hardware guide pairs each tier with a rough throughput range and user count. These are sizing guides for typical mixed traffic, not guarantees, but they are the most honest starting point you will find because they come from the project itself.
| Connection speed | Typical users | Suggested tier |
|---|---|---|
| 11 to 150 Mbps | 10 to 30 | Minimum |
| 151 to 350 Mbps | 30 to 50 | Reasonable |
| 350 to 750+ Mbps | 50 to 150+ | Recommended |
Read the table in the direction of your plans, not your present. If your internet connection is scheduled for an upgrade, or the household or office is growing, sizing for the reasonable or recommended tier now is cheaper than replacing a firewall later. Equally, a single user on a modest connection gains nothing from oversizing: OPNsense will not route a 100 Mbps line any faster on a large machine than on a reasonable one.
One workload deserves a special mention because it breaks the pattern: heavy VPN use and intrusion detection both spend CPU time on every packet. If you intend to run either at full line rate, lean toward the recommended tier even if your user count looks small on paper.
Why RAM matters more than you might expect
Memory in a firewall is not just room for the operating system. The state table, which tracks every live connection passing through the box, lives in RAM, and the official guide notes that each state table entry needs about 1 kB of memory. A quiet home network holds a modest number of states. A busy network with many devices, torrents or long lived connections can hold a great many more, and every one of them is paid for in RAM.
On top of the state table, each service you enable takes its share: the intrusion detection engine, a proxy, reporting and any plugins you add. This is why the tiers step from 3 GB to 4 GB to 8 GB rather than stopping at "enough to boot". The recommended 8 GB is not there to make the base system faster; it is there so the base system plus everything you bolt onto it still fits comfortably.
- 3 GB RAM: the floor. Enough for the installer to run and for basic routing and firewall duties.
- 4 GB RAM: every feature at modest load, per the official guide. The sensible default for a full install.
- 8 GB RAM: the recommended tier, with headroom for IDS/IPS, reporting, plugins and growth.
Storage: SSD for real installs, cards only for nano
Notice how the tiers pair memory with storage. The minimum tier uses an SD or CF card of at least 4 GB because it is designed around the nano image, which runs from RAM disks and avoids writing logs to the card. The reasonable and recommended tiers both specify an SSD, at 40 GB and 120 GB respectively.
For a normal full installation, an SSD is the right choice for two reasons. First, a full install writes logs and keeps them across reboots, and that steady writing suits an SSD far better than a memory card. Second, the extra capacity is what features such as the IDS/IPS alert database and reporting history consume over time. You do not need a large or fast drive by desktop standards; you need a real one.
If your hardware only offers card storage, treat that as a signal to use the nano image and accept its limits, rather than forcing a full install onto media it was not sized for. If you are still choosing hardware, our guide to choosing a mini PC for OPNsense covers storage as part of the buying checklist.
CPU and architecture: amd64 only
OPNsense is published for the x86-64 architecture only, listed as amd64 on the download page. There are no 32 bit or ARM installer images, so an old 32 bit machine or a single board ARM computer cannot run it, regardless of how much memory it has. Any candidate machine must have a 64 bit x86 CPU.
Within that constraint, the clock speeds in the official tiers are modest: 1 GHz dual core at the lower tiers and 1.5 GHz multi core at the recommended tier. Modern low power CPUs in fanless appliances clear these bars easily. Where CPU choice starts to matter is, again, the extra workloads: encrypted VPN traffic and deep inspection are per packet costs, and they reward a stronger processor long before plain routing does.
Network cards: the quiet requirement
The official hardware guide recommends Intel network interfaces, and it points out that hardware compatibility follows FreeBSD, because all FreeBSD drivers are included in the OPNsense kernel. In practice this means two things. A machine whose network chips are well supported by FreeBSD will simply work, and Intel based ports are the safest bet when you have a choice.
You also need at least two network interfaces for a normal firewall layout, one for WAN and one for LAN. A single port machine can be made to work with VLANs and a managed switch, but that is an advanced arrangement, not a starting point. When you evaluate a candidate machine, count its ports before you admire its processor.
How your service list moves you between tiers
The tiers make the most sense when you read them against the services you actually intend to switch on. The base firewall is light; the add ons are where the resources go.
| Planned service | What it costs | Tier implication |
|---|---|---|
| Routing, NAT, firewall rules, DHCP, DNS | Very little beyond the base system | Any tier, including minimum |
| VPN server or site to site tunnels | CPU time on every encrypted packet | Reasonable; recommended if the tunnel must run at full line rate |
| IDS/IPS with Suricata | Memory for rules and inspection, disk for the alert database | Recommended, on an SSD install; not available at the minimum tier |
| Caching proxy | Continuous disk writes for cached content | Reasonable or higher, on an SSD; excluded at the minimum tier |
| Reporting and long log history | Steady disk space and writes over time | SSD tiers, with the 120 GB drive giving the most room |
| Several plugins at once | Each takes its own share of RAM | Recommended, for the headroom |
The pattern is consistent: anything that inspects traffic costs CPU and memory, and anything that remembers traffic costs disk. If your plans include both kinds, you are describing the recommended tier, whatever your user count says.
Reusing hardware you already own
Plenty of good OPNsense boxes start life as a retired desktop, a small office PC or a previous firewall. Reuse is perfectly sensible provided the machine passes the same checks as a new purchase. Confirm the CPU is 64 bit, count the RAM honestly (and remember the installer needs 3 GB before anything else gets a say), and check the storage: a spinning hard disk that came with an old PC will work, but the SSD tiers exist because an SSD is quieter, cooler and better suited to constant small writes.
The most common reason an old machine fails the test is its network interfaces. Many desktops have exactly one port. Adding a second, Intel based PCIe network card is a long standing and inexpensive fix, and it usually turns a marginal candidate into a good one. What you should not do is plan around a USB network adapter as a permanent WAN or LAN port if a card slot is available; treat USB adapters as a temporary measure.
Finally, weigh the electricity. A firewall runs around the clock, so an old tower that idles at high wattage can cost more over a couple of years than the low power appliance that replaces it. That is an argument about running costs, not capability: if the old machine meets the tiers, it will do the job.
A quick sizing checklist
- My CPU is 64 bit x86 (amd64). A 32 bit or ARM board will not work.
- I have at least 3 GB of RAM, because the installer itself needs that much to run.
- I am aiming for 4 GB of RAM and an SSD if I want every feature at modest load.
- I am aiming for 8 GB of RAM and a 120 GB SSD if I want IDS/IPS, reporting, plugins or a fast connection with many users.
- I am only considering SD or CF storage if I plan to use the nano image and accept its limits.
- My machine has at least two network ports, preferably Intel based.
- I have matched the tier to my connection speed and user count, including planned upgrades.
Common sizing mistakes
Buying for the base system and forgetting the services
The most frequent mistake is sizing for plain routing and then enabling intrusion detection, a caching proxy or heavy reporting afterwards. Those services are exactly what the higher tiers exist for. Decide your service list first, then pick the tier.
Treating the minimum as a recommendation
The minimum tier is a floor that keeps a light workload running, not a target. The official guide describes the recommended tier as the one that fits most use cases, and for a machine you intend to keep for years, that is the tier to measure against.
Ignoring the install target
RAM is only half of each tier. A machine with 8 GB of RAM and a tiny worn out card for storage is not a recommended tier system; it is a mismatch. Keep the memory and storage halves of the tier together.
The figures in this article are the official tiers from the OPNsense hardware documentation. Hardware that exceeds them is welcome but rarely necessary; hardware below the minimum, especially below 3 GB of RAM, will stop the installer before you can find out whether it might have coped.