Open Systems vs Jimber: two European SASE platforms compared for mid-market sovereignty

Jimber is the stronger fit for European mid-market organisations between 50 and 400 users that need partner-first deployment, transparent per-user pricing, and EU jurisdiction without relying on a Swiss adequacy decision. Open Systems suits enterprises that want a fully managed SOC service through Mission Control and accept the enterprise premium that comes with it. Both deliver Europe-headquartered SASE, but they target different buyer profiles.

You have already filtered out the US mega-vendors. The CLOUD Act question came up in a board review or a supply chain assessment, and now your shortlist is European-headquartered platforms only. Two names that surface in that conversation are Open Systems, the Zurich-based provider with a long enterprise pedigree, and Jimber, the Belgian single-vendor SASE platform built for the mid-market.

This is the first European-versus-European comparison in the Jimber series, and the analysis works differently because of it. The sovereignty question is no longer US versus EU. It becomes Swiss jurisdiction versus EU jurisdiction, a fully managed SOC model versus a partner-first model, and enterprise heritage versus a platform purpose-built for teams of 50 to 400 users. If you have read the Jimber vs Zscaler comparison or the Cato Networks comparison while screening out US vendors, the analytical framework here is the same. The questions you ask are the ones the sovereignty conversations we heard at Cybersec Europe pushed to the front of every evaluation.

What Open Systems delivers in 2026

Open Systems sells the Open Systems SASE Experience, a co-managed platform split into SD-WAN as a Service for edge routing and transport, and SSE as a Service for user security. Capabilities are licensed as modular SKUs under those two layers, administered through the Mission Control Portal. The historic differentiator is Mission Control itself: a fully managed network and security operations service that is included by default, not sold as an option.

The SKU set covers Zero Trust Network Access to replace legacy client VPNs, Secure Web Gateway for proxy-based filtering, Firewall as a Service for edge segmentation, CASB for SaaS governance, and standard and advanced email security. Under CEO Dennis Monner, appointed in late 2025, the company has expanded the SASE Experience brand rather than rebranding it. The corporate backdrop changed more than the product naming did. Private equity owner EQT exited in 2024, and Open Systems moved under the strategic ownership of Swiss Post, a state-backed Swiss institution.

A point worth checking in any evaluation is what runs natively versus through partners. Open Systems builds SD-WAN and Firewall as a Service on its own proprietary stack, but several core elements are partner-integrated. According to the company’s subprocessor statement published in February 2026, ZTNA is delivered through Cyolo Security (Israel), the SWG antivirus engine through Avira (Germany), the Web Application Firewall through Convotis Swiss Cloud (Switzerland), and OT/IoT monitoring through Nozomi Networks (US). The operational supply chain is more globalised than the Swiss-heritage positioning suggests.

Mission Control is the part most external content gets wrong or oversimplifies. In 2026 it places Level-3 certified engineers on the front line rather than first-tier triage staff, operating a follow-the-sun model across Zurich, Bern, Dusseldorf, Linz, San Francisco, Hawaii, and Noida. Open Systems commits to device health checks every 60 seconds, incident notification within 6 minutes, and ticket escalation to a Level-3 engineer within 8 minutes. This is a genuine, high-touch service. It is also the reason the platform carries the cost profile it does.

What Jimber delivers in one platform

Jimber’s SASE platform converges ZTNA, Secure Web Gateway, Firewall-as-a-Service, SD-WAN and a Web Application Firewall in a single cloud-managed console. NIAC hardware extends the platform to printers, IoT sensors, and industrial controllers that cannot run an agent. The company is headquartered in Belgium, processes data inside the EU by default, and runs a partner-first multi-tenant model. The ICP is organisations between 50 and 400 users.

The platform is single-codebase rather than a bundle of integrated SKUs. One policy engine governs application access, web filtering, and network controls. One user directory feeds every module. Pricing is custom per user, without bandwidth surcharges or per-site licensing tiers, and the figures are quoted per environment.

Jimber is not an enterprise replacement for a fully staffed SOC operation, and it does not pretend to be. There is no bundled 24/7 managed service inside the platform price. Service partners provide managed operations separately where a customer wants it. That separation is deliberate, and it is the cleanest line between the two platforms in this comparison.

Quick comparison: Open Systems and Jimber side by side

Which European SASE platform fits mid-market organisations best in 2026

For European mid-market organisations between 50 and 400 users, Jimber is the better fit. It pairs a single-codebase platform and EU jurisdiction by default with a partner-first commercial model and native isolation for agentless devices through NIAC. Open Systems is the stronger choice for global enterprises that want a vendor-operated SOC service and can absorb the premium.

The decision is rarely about whether Open Systems works. It does, and the customer signals back that up: a 98% retention rate, an 8.5-year average customer tenure, and Gartner Peer Insights scores around 4.9 for delivery and execution. The Mission Control service is real and well regarded. The question is whether a mid-market team with three IT generalists needs, and wants to pay for, a fully managed follow-the-sun SOC with edge appliances at every site.

European buyers add a second layer. NIS2 Article 21 supply chain assessments now require evidence of where data is processed, which subprocessors are involved, and what foreign jurisdiction exposure exists. A Belgium-headquartered vendor with EU-only processing and no US entity is simpler to document than a Swiss vendor with a US subsidiary, an Azure dependency, and an Israeli ZTNA subprocessor. Both can pass a CCB CyberFundamentals review. One generates fewer follow-up questions.

There is also a reference gap that matters for Benelux buyers. Open Systems’ public customer list skews to global enterprises such as Franke, Logitech, and Tetra Pak, and to humanitarian organisations like the IFRC and SOS Children’s Villages. It lists no public mid-market references in Belgium, the Netherlands, or Luxembourg. For a 200-user organisation in Ghent or Eindhoven, that means evaluating performance through DACH manufacturing case studies rather than local peers.

Architecture: cloud-native simplicity vs Mission Control depth

Open Systems runs a single-pass processing architecture, where routing, SD-WAN optimisation, firewall rules, and proxy filtering execute in one packet-processing cycle rather than chaining through separate virtual machines. That design reduces latency. The hosting model underneath, though, is hybrid and cloud-extended rather than cloud-native from inception: physical edge appliances at branch sites, core SSE capabilities in dedicated Azure tenants (primarily Switzerland North), and WAF plus portal databases hosted with a Swiss partner. Mission Control adds 24/7 human oversight as part of the platform, not as a layer you assemble yourself.

Jimber’s architecture is cloud-native, runs on European infrastructure, and is operated day to day by service partners rather than by Jimber itself. This is the core operating-model difference. With Open Systems, the vendor operates the platform on your behalf through Mission Control. With Jimber, the vendor builds and maintains the platform and a service partner operates it for you.

That distinction shapes everything downstream. The follow-the-sun SOC means an Open Systems customer has a single vendor relationship and a guaranteed engineering response, but also accepts edge appliances, longer deployment cycles, and a co-managed portal that customers consistently flag as clunky in Gartner Peer Insights reviews, where ease of administration scores 3.7 against delivery scores near 4.9.

For a lean mid-market team running cloud-first with few physical offices, the appliance-heavy underlay is more infrastructure than the environment needs. For a distributed manufacturer with complex WAN requirements and no internal security staff, that same underlay and the engineering service behind it are exactly the point.

Pricing: premium managed service vs transparent per-user

Open Systems is premium-priced because Mission Control is bundled in. Pricing is quote-only, with no public figures, and it is multi-dimensional: per-user SSE subscriptions, SD-WAN edge bandwidth per site, the number of physical locations, and a one-time setup fee for design and provisioning. The managed SOC is part of the base subscription, not a separate line.

Research compiling G2 and Gartner Peer Insights signals places a typical mid-market deployment, around 200 users with two branch sites, at an estimated first-year total cost of ownership between roughly 80,000 and 150,000 euros once setup, per-user SSE, and per-site bandwidth are combined. The setup component alone is estimated in the 15,000 to 35,000 euro range. These are indicative ranges from third-party analysis, not published rates, and the quote-only model makes any direct per-user comparison difficult without a multi-week scoping exercise. Industry benchmarks for 2026 put platform-only SASE licensing from larger vendors at roughly 14 to 22 dollars per user per month, with fully managed services running far higher, which is the band Mission Control sits in.

Jimber uses custom per-user pricing without bandwidth-based add-ons or per-site surcharges, and does not bundle a managed SOC into the platform price. Where a customer wants managed operations, a service partner provides it separately and prices it transparently. The structural point matters more than any single figure: one number per user, no escalating fees as sites come online, and a managed layer you buy only if you need it. The honest trade-off is that Open Systems’ premium buys a real, included engineering service, while Jimber’s lower platform cost assumes you have a partner or internal capacity to run it.

Swiss HQ vs Belgian HQ: sovereignty mechanics for EU buyers

Both vendors are non-US, but Switzerland sits outside the EU and Belgium sits inside it. That difference is real, and it is smaller than headline sovereignty marketing implies, so it is worth being precise rather than alarmist.

Switzerland holds a GDPR adequacy decision. The European Commission first recognised it in Decision 2000/518/EC on 26 July 2000, and a comprehensive review published on 15 January 2024 formally maintained that status. Personal data can flow from the EU/EEA to Switzerland without Standard Contractual Clauses. Switzerland’s revised Federal Act on Data Protection (FADP) entered into force on 1 September 2023 and aligns closely with GDPR, though it differs in detail: it operates on a relative opt-out principle for private-sector processing rather than requiring a positive legal ground, and it treats securely encrypted data as non-personal for parties without the keys.

The CLOUD Act is where the Swiss-versus-Belgian distinction becomes concrete. Open Systems AG is headquartered in Zurich, but its corporate structure includes Open Systems Americas Inc. in San Francisco. The US CLOUD Act can compel any entity under US jurisdiction, including foreign companies with US subsidiaries, to disclose data in its possession, custody, or control regardless of where that data physically sits. So even with data stored in Zurich or an EU Azure boundary, the US subsidiary creates a structural exposure that contractual safeguards cannot fully close. A Belgian vendor with no US footprint, like Jimber, is outside that mechanism entirely.

The Mission Control model adds an operational dimension on top of the legal one. Level-3 engineers in Noida and San Francisco access the co-managed portal and query real-time traffic logs during their shifts. Under Swiss adequacy, EU-to-Switzerland data flows are covered, but for an organisation processing sensitive metadata under GDPR Article 9, or documenting a NIS2 supply chain assessment, that routine non-EU administrative access is a line item that has to be acknowledged. Open Systems’ own documentation notes that some telemetry, support logs, and routing metadata may be accessed from outside the EU/EEA.

For a CCB CyFun supply chain evaluation, the two vendors produce different dossiers. The Swiss vendor’s file has to cover the adequacy decision, the FADP, the US subsidiary’s CLOUD Act exposure, the Azure and Nozomi subprocessor relationships, and the global SOC access pattern. The Belgian vendor’s file is shorter because the answer to most jurisdiction questions is the same: EU entity, EU processing, no foreign parent. Neither fails the assessment. The documentation effort differs, and these mechanics matter most where the cross-border data transfer rules intersect with your specific risk register.

OT, IoT and agentless device support

Open Systems has no native agentless hardware appliance. The edge appliances it ships handle WAN termination, routing, and branch firewall segmentation, not the discovery and isolation of unmanaged OT or IoT devices. For that, the company resells Nozomi Networks. Under a partnership formalised in April 2026, Nozomi Guardian and Arc sensors are deployed across the customer network to inventory and monitor OT and IoT assets, with telemetry streamed into Mission Control for the Level-3 engineers to triage. An older MDR+ IoT integration with Microsoft Defender for IoT, dating to 2022, sits alongside it but the development focus has shifted to the Nozomi model.

This works, but the operational and sovereignty profile is heavier. Deploying Nozomi requires network spanning or TAP configuration, sensor installation, and telemetry pipeline tuning. Alerts pass through Nozomi’s AI and cloud, then to the SOC, and the data path crosses both Nozomi (US-headquartered) and Open Systems’ global support centres. For an OT environment that is itself a sovereignty-sensitive asset, that is a longer chain to document.

Jimber addresses the same problem with NIAC, the Network Isolation Access Controller, integrated into the SASE platform itself. NIAC is a local hardware appliance that plugs into the network where agentless devices live, a factory floor, a clinic, a branch with managed printers. Devices behind it are isolated by default, traffic is encrypted in transit, and access runs through the same Zero Trust policies that govern users.

The practical difference is where the integration cost lands. For a mid-market manufacturer with PLCs and HMIs on a line, Jimber treats agentless devices as a first-class SASE concern handled at the hardware layer inside EU jurisdiction. Open Systems treats it as a partner-delivered add-on with a capable but more complex and more globally distributed pipeline.

Service model: Mission Control SOC vs partner-first

This is the architectural choice that defines the rest of the comparison, and it is a genuine trade-off rather than a flaw on either side. Open Systems operates the platform for you through Mission Control. Jimber provides the platform and a service partner operates it. Different procurement, different relationship, different failure modes.

Mission Control means a single throat to choke. One contract, one vendor relationship, certified Level-3 engineers reachable without wading through chatbots, and a dedicated Technical Account Manager who learns your topology over years. Customers praise exactly this in reviews: direct engineer access, TAM dedication, and rock-solid ISP line management across global sites. The cost is flexibility. You operate inside Open Systems’ model, change requests for minor adjustments can lag, and explaining non-standard workflows to high-level engineers can require repetition.

Jimber’s partner-first model spreads the relationship differently. A service partner delivery model means you choose the partner, the partner operates the platform from a multi-tenant console with full role-based access, and you can switch partners without changing platforms. The cost is that there are more relationships to manage and the quality of operations depends on the partner you select rather than on a single vendor SLA. For organisations that already work with a trusted integrator, that is an advantage. For organisations that want one vendor to own everything end to end, Mission Control is the cleaner answer.

Mid-market accessibility: enterprise heritage vs purpose-built

Open Systems’ heritage is enterprise. Its stated target is 500 to 10,000-plus employee organisations, skewing to global manufacturing, energy, chemicals, and large NGOs with distributed high-risk sites. The platform’s reliance on physical SD-WAN underlay management, onsite edge appliances, and mandatory co-managed service reflects that history. The mid-market push under Dennis Monner is recent, dating to late 2025.

That heritage shows up in deployment time. For a 200-user organisation with branch offices, Open Systems’ timeline runs 3 to 6 months, driven by hardware procurement, edge appliance logistics, ISP line orchestration, and co-managed design workshops. Jimber’s cloud-native onboarding avoids physical edge appliances and typically completes in weeks, with phased rollout starting from ZTNA for remote users.

For a lean 50 to 400 user organisation operating cloud-first with minimal physical footprint, the Open Systems model is more platform than the environment requires. The capability is real. The fit is the question.

Choose Jimber if, choose Open Systems if

Both platforms are legitimate European SASE choices. The decision is about operating model and scale, not about which is better in the abstract.

Choose Jimber if:

• You operate a European mid-market organisation between 50 and 400 users
• You want EU jurisdiction directly, without relying on a Swiss adequacy decision or documenting US subsidiary exposure
• A partner-first deployment model, where you choose and can switch the partner that operates the platform, fits how you work
• Transparent per-user pricing without bandwidth or per-site surcharges aligns with your procurement
• Agentless devices, printers, IoT sensors, OT equipment, need native isolation through NIAC hardware
• You do not need a fully managed SOC service bundled into the platform price
• You work with or through a service partner that needs full multi-tenant tooling

Choose Open Systems if:

• You are an enterprise of 1,000-plus employees with complex, distributed physical sites
• You want a fully managed SOC service through Mission Control rather than operating the platform yourself
• You are willing to pay an enterprise premium for a vendor-operated platform with guaranteed Level-3 engineering response
• Global follow-the-sun support across multiple continents is a requirement
• Swiss data jurisdiction is acceptable within your supply chain risk assessment
• You prefer a single vendor relationship over managing multiple partner relationships

Final verdict for European mid-market teams

Jimber is the stronger fit for European mid-market teams between 50 and 400 users that need single-platform simplicity, EU jurisdiction directly, a partner-first service model, native agentless device coverage through NIAC, and transparent per-user pricing. Open Systems is the stronger fit for global enterprises that want a fully managed SOC service through Mission Control and accept Swiss jurisdiction and an enterprise premium. Both are credible European platforms, evaluated for different organisations.

Frequently asked questions

Is Open Systems’ SASE platform cloud-native or hybrid?

Open Systems uses a single-pass processing engine but a hybrid, cloud-extended hosting model. It combines physical edge appliances at branch sites, dedicated Microsoft Azure tenants in Switzerland North and EU boundaries, and third-party Swiss hosting for the WAF and portal databases, rather than being cloud-native from inception.

What is Open Systems Mission Control and is it included in the platform price?

Mission Control is Open Systems’ co-managed network and security operations service. Level-3 certified engineers run monitoring, configuration, and incident response on a follow-the-sun model. It is bundled into the base subscription by default, which is the main reason the platform carries an enterprise price point rather than a lower self-managed tier.

Does Switzerland have a GDPR adequacy decision for SASE data flows?

Yes. The European Commission recognised Switzerland in Decision 2000/518/EC in 2000 and maintained that status in a review published on 15 January 2024. EU-to-Switzerland personal data transfers are permitted without Standard Contractual Clauses. A separate CLOUD Act exposure exists because Open Systems operates a US subsidiary.

Can Open Systems support agentless devices like printers and IoT sensors?

Open Systems has no native agentless appliance. It addresses OT and IoT by reselling Nozomi Networks sensors, which feed telemetry into the Mission Control SOC. Jimber handles agentless devices natively through NIAC hardware, which isolates printers, cameras, PLCs and similar devices inline within the SASE platform.

What size organisations does Open Systems typically target?

Open Systems has historically targeted enterprises of 500 to 10,000-plus employees, with a customer base in global manufacturing, energy, chemicals, and large NGOs. A mid-market push began in late 2025, but the appliance-heavy underlay and mandatory managed service remain calibrated for larger, distributed organisations.

Is Jimber a Gartner-recognised SASE vendor?

Jimber was not included in the Gartner Magic Quadrant for Single-Vendor SASE in 2024 or 2025, whose leaders are Palo Alto Networks, Fortinet, Cato Networks, Cisco, Zscaler, and Netskope. Open Systems is also absent, sitting closer to the managed security service provider category. Jimber occupies an emerging European single-vendor SASE segment.

Which European SASE vendor offers transparent per-user pricing?

Jimber uses custom per-user pricing without bandwidth or per-site surcharges, quoted per environment with transparent partner margins. Open Systems uses a quote-only, multi-dimensional model that combines per-user fees, SD-WAN bandwidth, physical site counts, and one-time setup, which makes a direct per-user comparison difficult without a scoping exercise.

Both Open Systems and Jimber are legitimate European SASE platforms, and the choice turns on how you want the platform operated and at what scale. For European mid-market IT teams choosing between European SASE platforms in 2026, the decision comes down to operating model fit, a vendor-run SOC service versus a partner-first model, and whether your environment is enterprise or mid-market. If you want to see how Jimber handles your specific deployment, compliance, and OT requirements, book a 30-minute walkthrough. Bring your NIS2 supply chain register and your current vendor list. The SASE vendor evaluation framework sets out the seven criteria we use to compare any two platforms.