Book a demo
Comparison · Updated July 2026

Swift Fox vs Preseem

Preseem is a good product. It popularized fq_codel-based QoE shaping in the WISP industry, and its TCP latency analytics are useful — that's exactly why we built the same queueing and latency analytics directly into Swift Fox. This page lays out the differences so you can decide what fits your network. If we get a fact wrong, tell us and we'll fix it.

Choose Preseem if…

You want QoE analytics and shaping as a standalone add-on and you're happy keeping your existing billing and monitoring tools. It's a mature, focused product that does that job well.

Choose Swift Fox if…

You want the same fq_codel shaping built into your billing and monitoring platform — plus things no QoE appliance does: MPLS auto traffic balancing, tier-fair congestion shaping, full network monitoring with paging, DDoS mitigation, and CGNAT.

The architectural difference

Inline appliance vs. out-of-band control

Preseem sits in the data path. An appliance (theirs or your own hardware) is installed inline at your network edge; your customer traffic flows through it, where it's measured and shaped. This is a proven design, and Preseem's per-flow metrics come directly from that vantage point.

Swift Fox is out-of-band by default. A small "pingbox" (VM, cloud, or embedded device) monitors your network over a secure tunnel, and shaping, latency analysis, and captive portals are executed by your existing MikroTik edge router. MikroTik v7 supports fq_codel, so Swift Fox automates managing those queues, and TCP latency is measured from ACK timing without touching the data path. Nothing sits inline, so the platform can never become a single point of failure, and there's no appliance to size, upgrade, or fail over as you grow.

For networks without a MikroTik edge, our Pathbox appliance (currently in early access) delivers the same features as a plug-in inline device. The philosophical difference is that with Preseem, inline is the architecture, while with Swift Fox it's an option.

Neither design is "wrong." Inline gives Preseem direct flow visibility; out-of-band gives Swift Fox zero data-path risk and lets the same measurements drive routing decisions — which is how features like MPLS auto-balancing become possible.

Feature by feature

What each platform does

CapabilityPreseemSwift Fox
fq_codel QoE shaping to plan ratesYesYesbuilt into billing packages
Per-subscriber latency & QoE metricsYesmature cross-vendor dashboardsYesreal-time TCP latency analysis
Tier-fair shaping during backhaul congestionPer-AP capacity managementYes — PFOany bottlenecked backhaul or AP; every tier keeps the same % of paid speed
Plug and Play SetupYesgraphing and shaping requires limited initial setup—network infrastructure must be configured on the network map, but we'll help you do it with 2 hour free onboarding
Backhaul capacity measurement (signal / MCS / throughput)—Yesplus automated TCP speedtests between MikroTik routers
MPLS auto traffic balancing (RSVP-TE)—Yesunique to Swift Fox
Full NMS: per-CPE ping history, paging, on-call rotations—QoE-focused alerting but no ICMPYesevery device, every minute, history forever
DDoS detection & BGP blackholing—Yes
Carrier-grade NAT management—Yes
Billing, invoicing & card processingIntegrates with third-party billingSonar, Visp, Splynx, UCRM & othersOptional tieralso integrates with Sonar, UCRM & Visp if you keep them
Customer portal with self-service reconnect—Yes
Hosted PBX / call centre / ticketing—Optional tier
Inline appliance in the data pathRequiredappliance or your own hardwareOptionalout-of-band with a MikroTik edge; inline Pathbox available for other networks
Pricing (USD, under 5000 subscribers)$0.90 / sub / moIncl Fixed Wireless Add-On
$200 monthly minimum		$0.75 / sub / mo$50 monthly minimum, includes monitoring & automation
Free trial30 days30 dayswith 2 hours of free onboarding

Preseem information sourced from preseem.com as of July 2026. Preseem is a trademark of its respective owner; Swift Fox Systems is not affiliated with Preseem. If anything here is outdated or inaccurate, email us and we'll correct it promptly.

Total stack cost

What the whole stack costs

Preseem does one job, so most WISPs run it alongside a billing platform and a monitoring tool. The fair comparison is what the whole stack costs. Example at 1,000 subscribers:

Typical multi-tool stack

  • QoE shaping~$900 / mo
  • Billing & CRM platform~$1,500–2,500 / mo
  • Network monitoring tool~$200–400 / mo
  • Ticketing / PBX~$150–300 / mo
Four tools, four vendors~$2,750–4,100 / mo

Swift Fox — Network + Billing + Call Centre

  • QoE shaping (PFO, built in)included
  • Billing, portal & card processingincluded
  • Full NMS + MPLS auto-balancingincluded
  • Hosted PBX, ticketing & schedulingincluded
One platform, one vendor$2,000 / mo

Prefer to keep your billing system? The Network Management tier ($750/mo at this size) replaces the QoE appliance and the monitoring tool, adds MPLS auto-balancing, DDoS protection, and CGNAT — and integrates with Sonar, UCRM and Visp for disconnects.

Common questions

Frequently asked questions

Is Swift Fox's shaping really equivalent to Preseem's?
Both use fq_codel active queue management to shape subscribers to their plan rates while keeping latency low under load — the approach that eliminates bufferbloat and "my internet is slow" calls. The implementations differ in where they run: Preseem shapes inline on its appliance; Swift Fox programs queues on your MikroTik edge router or optionally in our inline Pathbox. Swift Fox additionally offers Package-Fair Oversubscription, which shapes all subscribers behind any saturated backhaul or AP proportionally by tier — useful during outages, weather events, or while you're building out capacity.
Can I run Swift Fox and Preseem together?
Yes. Some operators adopt Swift Fox for monitoring, MPLS automation, and billing while keeping Preseem for shaping. Swift Fox supports sending shaping details to the Preseem API directly, so that you can continue using Preseem alongside, taking advantage of the shaping hardware that you already own and have installed, while gaining the PFO capability that Swift Fox offers.
I use Sonar, UCRM or Visp for billing. Do I have to switch?
No. Swift Fox's Network Management tier works alongside your existing billing platform, including API integrations with Sonar, UCRM and Visp for automatic disconnect and reconnect. Many customers start there and consolidate billing later, on their own schedule.
What do I need on my network to get started?
If you have a MikroTik router at your upstream edge, you can get started right away with a cloud pingbox tunnel, no new hardware needed - or if you'd prefer to run pinging locally, we offer a VM image, Raspberry Pi image, or we can ship you an embedded device. The pingbox automates features in your existing router to enable shaping, captive disconnect, DDoS mitigation, and CGNAT. Monitoring is directly from the pingbox and works across every major radio vendor with no other changes. Setup includes two hours of free onboarding with a Swift Fox network engineer. If you don't run a MikroTik-based network, Swift Fox offers an inline appliance called the Pathbox that will perform all the same features.
Who builds Swift Fox?
Swift Fox was built by operators who founded and ran a multi-thousand-subscriber WISP in southern Alberta for ten years. Every feature — including PFO and MPLS auto-balancing — was built to solve problems we hit on our own network. When you book a demo, you talk to the founder who wrote the code.

See PFO shape a saturated backhaul, live

Book a 20-minute demo and bring your gnarliest congestion scenario. No slide deck — just the product, and the person who built it.

Book a 20-minute demo Start a free trial

Questions first? [email protected] · 1-866-779-1608