Skip to main content

Appliance-Free SASE for MSPs: What It Means and What to Ask

Published on:
.
4 min read

Short answer: appliance-free SASE means the MSP doesn't ship a vendor box to each client. Security runs as software on equipment the client already has (a firewall, a server or virtual machine, a cloud instance) or as an agent on each device, and it's managed from a cloud console with no management server to run. For small clients that removes hardware cost and site visits. The other half of the question is where traffic gets inspected: locally, or after a trip to the vendor's cloud.

What does "appliance-free" mean?​

It can mean two different things, and it's worth asking which one a vendor means:

  1. No dedicated security appliance at the client. The security software runs on hardware the client already owns, in a virtual machine, in the cloud, or on the endpoints.
  2. No management appliance. The console is a cloud service, so there's no management server for you to patch, back up, or size.

Appliance-free doesn't mean "nothing runs at the client". Something still inspects the traffic: the client's existing gateway, a VM, or the agent on each laptop. What changes is that you don't buy, ship, rack, or replace a vendor box.

Why does it matter for MSPs with small clients?​

  • No hardware margin to fund. A 10-user client rarely justifies a dedicated appliance and its refresh cycle.
  • No shipping or truck rolls. Onboarding is remote: install the software, enroll the devices, apply the client's policy.
  • Faster changes. Adding a site or a remote worker means installing software, not ordering a box.
  • Fewer things to own. No appliance firmware to track per client and no RMA process.

PoP-based vs local enforcement​

Removing the box at the client raises a second question: if the traffic isn't inspected on site, where is it inspected?

PoP-based architecturesLocal enforcement
Where traffic is inspectedIn the vendor's cloud points of presence (PoPs)On the client's gateway, VM, cloud instance, or device
Added latencyA PoP round trip, typically 20 to 300msInspection time on the device only
Where the client's traffic goesThrough the vendor's cloudStays on the client's network or device
If the vendor's cloud has troubleInspection depends on reaching the PoPInspection doesn't depend on reaching a PoP; ask what still needs the cloud (management, updates, reporting)
What runs at the clientUsually a lightweight connector or agentThe security software itself

Neither is free of trade-offs. Local enforcement needs enough CPU on the device that runs it; PoP-based designs need nothing much on site but add the trip and send traffic through someone else's infrastructure, which matters to clients with data residency requirements.

What to ask a vendor​

  1. Does it run on hardware my clients already have? Which operating systems and firewalls?
  2. Is there a management server or appliance, or is the console a cloud service?
  3. Where is traffic inspected: on site, on the device, or in your PoPs?
  4. How much latency does inspection add, and how was that measured?
  5. Is there an agent for laptops off the office network? Which operating systems?
  6. What keeps enforcing if your cloud is unreachable?
  7. Where are logs and reports stored, and can I choose the region?
  8. Can I manage all clients from one multi-tenant console? (See What is multi-tenant firewall management?)
  9. What's the per-client minimum, and how is it licensed across clients? (See How MSPs bundle and price SASE)

How Zenarmor handles this​

Zenarmor is one app that deploys on a gateway, in the cloud, or on an endpoint. It runs on OPNsense, OpenWRT, FreeBSD, and Linux, on bare metal or virtual, and installs as a plugin on OPNsense, so MSPs can use firewalls and servers their clients already have. Endpoint agents cover Windows, macOS, and Linux. To size the device it runs on, see the hardware requirements.

Security is enforced locally at the point of connection, without re-routing traffic through a vendor's cloud. Inspection adds about 0.2ms. If Zenconsole can't be reached, gateways and endpoints keep enforcing their last policy locally until it sends a change. Every deployment is managed from Zenconsole, a cloud-based, multi-tenant console with no dedicated management appliance, and you can choose the region where reporting data is stored. See deployment options, Zenarmor for MSPs, or How MSPs should choose a SASE platform.

FAQ​

What is appliance-free SASE? SASE that doesn't need a dedicated vendor appliance at each site. Security runs as software on existing gateways, servers, cloud instances, or endpoints, and it's managed from a cloud console without a management server.

Is appliance-free SASE the same as cloud SASE? Not always. Cloud SASE often means traffic is inspected in the vendor's points of presence. Appliance-free can also mean the software runs locally on the client's own equipment, so traffic is inspected on site.

Does appliance-free SASE need any hardware at the client? It needs somewhere to run: the client's existing firewall or server, a virtual machine, a cloud instance, or an agent on each device. It doesn't need a new vendor box.

How much latency does PoP-based SASE add? A round trip to a point of presence typically adds 20 to 300ms, depending on how far the user is from the nearest PoP. Local enforcement avoids that trip.

Why do MSPs prefer appliance-free SASE for small clients? It removes hardware cost, shipping, and site visits, so onboarding a small client is a remote job and the per-client cost stays low.

What should MSPs ask a SASE vendor about deployment? Where it runs, whether there's a management server, where traffic is inspected and how much latency that adds, whether laptops are covered off-site, what happens if the vendor's cloud is unreachable, and where logs are stored.