Firewall
Depending on the product and purchase option, Boingfire systems can be provided with a firewall pre-installed or delivered as a clean platform for your own installation. This allows you to choose a ready-to-deploy appliance or maintain a standardized internal image.
Yes. Boingfire is designed as a flexible, standardized x86 edge platform that can support home, SMB, and multi-site corporate firewall deployments. You can run a wide range of firewall stacks depending on your security and management requirements.
Depending on the product and purchase option, Boingfire systems can be provided with a firewall pre-installed or delivered as a clean platform for your own installation. This allows you to choose a ready-to-deploy appliance or maintain a standardized internal image.
Boingfire reduces deployment friction by standardizing hardware across sites, enabling repeatable imaging, and supporting consistent configurations. This approach improves rollout speed, reduces configuration drift, and makes troubleshooting and replacements faster and more predictable.
Yes. Boingfire systems are built for continuous operation with an appliance-style design that prioritizes stability, low power usage, and reliable uptime, making them suitable for home networks, retail sites, offices, and branch locations.
Boingfire supports common firewall and routing platforms, including FreeBSD-based and Linux-based options. Many customers deploy OPNsense or similar solutions, while others install their preferred security stack for custom requirements.
IoT Gateway
Yes. A typical gateway setup is Node-RED + Mosquitto (MQTT), often containerized for consistency and ease of updates.
Yes. Multi-port designs and VLAN segmentation allow clean separation between device networks, management access, and uplink traffic.
On supported models, LTE/5G expansion is available. This enables remote-site deployments and failover designs where wired WAN is unavailable or unreliable.
Use a gold image plus containerized services, then clone builds per customer/site. Maintain pre-imaged spares for fast replacement.
Most deployments use Ubuntu Server LTS or Debian with Docker. If your gateway is primarily networking-focused, OpenWrt x86_64 can be a strong option.
MSP
Boingfire enables a pre-staged, “ship-to-site” workflow: you can image and configure units in advance, label them per customer/location, and ship directly to the site for fast turn-ups. This approach reduces on-site time, minimizes configuration drift, and simplifies troubleshooting because the hardware baseline remains consistent.
Boingfire platforms are available with practical configuration options, such as memory and storage sizing, and (model-dependent) add-ons like Wi-Fi and LTE/5G modules. This allows MSPs to standardize on a core platform while still tailoring deployments for specific client use cases, performance needs, and connectivity constraints.
Boingfire is a purpose-built, fanless edge appliance platform designed for repeatable MSP deployments firewall/VPN, SD-WAN CPE, branch routing, and edge gateways. You can standardize on one hardware family, pre-stage configurations, and deploy consistently across clients to reduce variance and improve supportability.
Boingfire is positioned as an MSP-friendly platform with support designed around real deployment needs, consistent builds, predictable hardware behaviour, and practical guidance for rollouts and replacement strategies. Warranty and support terms may vary by model and program, but the intent is to keep deployments stable and serviceable over the long term.
Boingfire is designed to be OS-agnostic, supporting standard firewall, routing, and virtualization stacks used by MSPs. Typical deployments include open-source firewall distributions, Linux-based routing/VPN solutions, and hypervisor-based edge builds so you can align the device to your preferred toolset and client requirements.
SD-WAN
Yes. Boingfire is a strong fit for branch CPE roles terminating overlays, enforcing segmentation, and supporting multi-WAN connectivity.
On models that support cellular expansion, LTE/5G can be used for primary WAN in remote sites or failover in business-critical locations.
Yes. Most SD-WAN architectures rely on multi-WAN health checks, failover, and policy routing capabilities supported by standard firewall/router stacks deployed on Boingfire systems.
Use a gold image plus standardized templates, label devices per customer/site, and keep pre-imaged spares for swap-and-go replacement.
For MSP-friendly deployments, OPNsense or pfSense are common choices with WireGuard/IPsec overlays. For routing-heavy designs, VyOS is a strong option. For flexible “SD-WAN + apps,” Ubuntu/Debian works well.
VPN
Yes. Boingfire can serve as a branch gateway that terminates site-to-site tunnels and enforces segmentation between local networks and the VPN overlay.
Yes. Many deployments use Boingfire as a combined security gateway: VPN + firewall rules + VLAN segmentation, enabling consistent policy enforcement across locations.
Use a gold image plus standardized templates, label devices per customer/site, and maintain pre-imaged spares for swap-and-go replacement.
For MSP deployments, OPNsense or pfSense are common because they combine VPN and firewall policies in one platform. For routing-centric designs, VyOS works well. For flexible “VPN + apps,” Ubuntu/Debian is a strong option.
WireGuard is often preferred for simplicity and performance. IPsec is widely supported for site-to-site and interoperability. OpenVPN remains common for certain remote-access scenarios and compatibility needs.
White Label
On supported models, Wi-Fi/LTE/5G expansion is available. The recommended configuration depends on your region, carrier requirements, and deployment model.
Yes. White label programs typically include labelling and device identification aligned to your naming standards, with optional packaging inserts for a professional handoff.
Yes. We can align on a standard image and staging workflow so your deployments remain consistent across customers and sites.
A best practice is a “fast replacement” strategy: maintain a small pool of pre-imaged spares for swap-and-go recovery. This keeps downtime low and support predictable.
That’s common. Most providers use one baseline build plus client/site-specific profiles. We can structure labelling and staging to match your rollout method.
