Open Systems AG, operating this platform as Open Systems SASE Experience (formerly marketed around Secure SD-WAN as a managed security service provider) SASE and SD-WAN profile

Summary

Strength | A specifically-named, quantified, extensively and consistently evidenced fully-managed operations model (Mission Control) - Level-3-engineer-only staffing, 400+ hours of additional training per engineer, and a confirmed 8-minute ticket-escalation commitment | Buyers get a genuinely low-operational-burden platform backed by concrete, checkable operational commitments rather than vague 'great support' marketing language | Best: buyers specifically wanting fully managed delivery with minimal internal operational burden. Less relevant: buyers wanting a self-service, do-it-yourself platform with minimal vendor involvement | High | Genuinely the single strongest, most specifically and consistently evidenced characteristic of this vendor across the entire profile - not a single feature but the company's whole operating identity.

Buyers get a genuinely low-operational-burden platform backed by concrete, checkable operational commitments rather than vague 'great support' marketing language

Summary

Overall Netify Assessment | Open Systems' most credible, best-evidenced strength is genuinely consistent across this entire profile: a specifically-named, quantified, fully-managed operations model (Mission Control) delivering real, checkable operational commitments, reinforced by five real, named customer case studies spanning genuinely varied scenarios with several quantified outcomes. That evidence, combined with a confirmed ISO 27001 certification and a genuinely rare degree of architectural transparency about partner-delivered components, makes this a credible shortlist candidate - particularly for large, multi-site organisations and European/Swiss-oriented buyers specifically. The profile is honest about real, specific gaps: no confirmed US-centric compliance certification, recent ownership and leadership changes, and comparatively thin remote-user/BYOD-specific evidence. This profile is solid enough to support initial shortlist guidance for large-enterprise, managed-service-preferring, and European-oriented buyers specifically, but the flagged compliance gaps and the recent ownership transition should both be discussed directly with Open Systems before use in a high-stakes, long-term, or US-regulated procurement decision. | Whole profile | Medium-High overall | Recommend direct Open Systems engagement to confirm current compliance-certification status and understand Swiss Post's strategic intent before this profile supports a high-stakes procurement decision.

Recommend direct Open Systems engagement to confirm current compliance-certification status and understand Swiss Post's strategic intent before this profile supports a high-stakes procurement decision.

Summary

Support/service reality | Genuinely one of the strongest, most specifically-evidenced support findings across this entire profile - a real, named, quantified 8-minute escalation commitment, Level-3-only engineer staffing with 400+ hours of additional training, and real, verbatim, independently-hosted customer reviews all reinforce the same, consistent picture. | Table 8 | High | Present this support-model evidence with genuine confidence - it is unusually specific, quantified, and consistently corroborated relative to the vague 'support available' finding common across this category.

Present this support-model evidence with genuine confidence - it is unusually specific, quantified, and consistently corroborated relative to the vague 'support available' finding common across this category.

Summary

Compliance & Footprint | A confirmed, primary-sourced, dedicated ISO 27001 certification page, reinforced by the company's genuinely long, three-decades-plus operating history and a specific, quantified global footprint (approximately 10,000 deployments across more than 180 countries). | No FedRAMP, SOC 2, PCI DSS, or HIPAA certification was found confirmed in any source reviewed in this research pass - a real, specific gap for buyers with US-specific compliance-attestation requirements, worth understanding given the company's genuinely European (Swiss) primary orientation.

Summary

Cloud-first organisation | Good fit, evidenced at a general level | Confirmed cloud-native, single-pass architecture and real, named customer evidence explicitly confirming protection across on-premises, data-centre, and cloud environments together (Mammut) | None significant identified | Not assessed | Table 3, 6 findings | Real, credible fit, reinforced by specific, primary-sourced, named-customer confirmation of unified multi-environment protection.

Summary

SSE deployment to remote users | Not evidenced with specific detail in sources reviewed, consistent with the broader Table 5 finding that remote-user/client-side evidence is thinner than the site-to-site/managed-operations side of the platform | Not itemised | Not itemised | Not itemised | Not quantified | Not itemised | Not detailed | A genuine, specific evidence gap for this exact scenario, consistent with the pattern found throughout Table 5.

Summary

Who is this genuinely best suited for? (mandatory) | Buyers specifically wanting genuinely fully managed SASE delivery with concrete, quantified operational commitments (8-minute escalation, Level-3-only engineers) rather than a self-service platform; large, multi-site, or internationally-distributed organisations, given the confirmed named case-study evidence at genuine scale (60+ locations); and European or Swiss-oriented buyers, or those with a specific preference for a state-backed rather than venture/private-equity-owned provider. | Tables 1, 8, 14, 15 | High | Buyers matching this profile can proceed with genuine confidence, backed by real, specific, quantified evidence rather than only generic managed-service marketing claims.

Buyers matching this profile can proceed with genuine confidence, backed by real, specific, quantified evidence rather than only generic managed-service marketing claims.

Summary

Limitation | Remote-user and BYOD-specific evidence is comparatively thin relative to the platform's well-evidenced site-to-site SD-WAN, managed-operations, and branch-connectivity capabilities (see Table 5) | Buyers whose primary requirement is remote/hybrid-workforce access specifically, rather than site-to-site connectivity, have less specific evidence to evaluate | Affects remote-user-heavy organisations most specifically | Table 5, 15 findings | Medium-High (confident about the specific gap found in this research pass) | A genuine, specific evidence gap - this profile's strongest evidence clusters around site-to-site SD-WAN and managed operations; buyers with a primarily remote-workforce use case should confirm ZTNA/remote-access specifics directly.

Buyers whose primary requirement is remote/hybrid-workforce access specifically, rather than site-to-site connectivity, have less specific evidence to evaluate

Summary

Global branch rollout | Genuinely one of the best-evidenced scenarios in this entire profile - the confirmed Altana case study describes connecting '60+ locations worldwide and securely integrated new acquisitions' | Existing branch network/WAN infrastructure to integrate or replace | Mission Control (fully managed) | Mission Control | Not quantified with a specific overall timeline, though the confirmed fully-managed model implies reduced customer-side effort | Not itemised | Not detailed | Genuinely one of the strongest, most specifically-quantified global-rollout scenarios found in this research pass - real, named-scale (60+ locations) evidence.

Summary

Questions to ask before recommending it | 1) Does Open Systems have any current FedRAMP, SOC 2, PCI DSS, or HIPAA certification, or a stated roadmap toward one? 2) Given the confirmed subprocessor disclosure, which platform components are native versus partner-delivered (beyond ZTNA and SWG antivirus), and how does support/SLA accountability work for partner-delivered components specifically? 3) What is Swiss Post's specific strategic intent for Open Systems following the 2024 acquisition, and what direction has the newly-appointed CEO signalled? 4) What does a realistic quote look like at our expected scale, given the confirmed absence of published, first-party pricing? | Synthesis of Tables 1, 12, 13, 16 | High | A direct, reusable question set for Netify's advisory conversations with buyers considering Open Systems.

A direct, reusable question set for Netify's advisory conversations with buyers considering Open Systems.

Summary

Deployment & Ops | A specifically-named, quantified managed-operations model (Mission Control) with a confirmed 8-minute escalation SLA and Level-3-engineer-only staffing, reinforced by real, named, quantified customer outcomes - Mammut's WAN replacement was completed in under two months, and KEMET's engagement cut costs by 50%. | The platform's entire value proposition centres on fully managed delivery; buyers specifically wanting a self-service, do-it-yourself platform with minimal vendor involvement should confirm this model fits their preferred operating approach, since a genuinely self-managed option was not confirmed as the platform's primary path in this research pass.

Summary

Biggest operational concern | The combination of no confirmed US-centric compliance certification (FedRAMP, SOC 2, HIPAA) and the recent, short-period ownership/leadership changes together represent the two most concrete, actionable considerations a buyer should resolve directly before committing to a long-term, high-stakes relationship. | Tables 1, 13, 19 | Medium-High | Netify should proactively flag both specific, evidenced considerations to buyers during the shortlist conversation rather than let either surface as a surprise later.

Netify should proactively flag both specific, evidenced considerations to buyers during the shortlist conversation rather than let either surface as a surprise later.

Summary

Where does it fall behind competitors? (mandatory) | No FedRAMP, SOC 2, PCI DSS, or HIPAA certification was found confirmed in this research pass; the company underwent two ownership/leadership changes in a short period (Swiss Post acquisition 2024, new CEO late 2025); remote-user/BYOD-specific evidence is comparatively thin; and no first-party, published pricing was found. | Tables 1, 5, 13, 16 | Medium-High | Named specifically and evidenced, not a generic hedge - the compliance-certification gap specifically should be raised proactively with any US-regulated or US-federal buyer.

Named specifically and evidenced, not a generic hedge - the compliance-certification gap specifically should be raised proactively with any US-regulated or US-federal buyer.

Summary

Firewall consolidation | Evidenced via the confirmed single-pass architecture integrating firewall alongside SD-WAN, SWG, NDR and unified threat detection together | Existing firewall infrastructure potentially retired | IT/security team | Mission Control | Not quantified with a specific timeline | Not itemised | Not detailed | The underlying architectural capability is genuinely well-evidenced (confirmed single-pass, no-service-chaining design), though a named customer case study specifically about firewall consolidation wasn't found in this pass.

Summary

Strength | A genuinely rare degree of architectural transparency - a confirmed, named subprocessor disclosure identifying Cyolo Security (ZTNA) and Avira (SWG antivirus) as the specific, named partners delivering two core platform functions | Buyers get real, specific, checkable visibility into exactly which components are native versus partner-delivered, rather than an undifferentiated 'fully native, single-vendor stack' claim | Best: buyers who specifically value vendor transparency and want to understand exact component provenance. Less relevant: buyers with no particular concern about native-versus-partner component delivery | Medium-High (confirmed via an independent source citing Open Systems' own subprocessor statement, though not independently cross-verified against a primary Open Systems source in this specific research pass) | A genuinely distinctive, worth-highlighting transparency practise, though Netify should confirm this disclosure directly with Open Systems given the sourcing caveat noted.

Buyers get real, specific, checkable visibility into exactly which components are native versus partner-delivered, rather than an undifferentiated 'fully native, single-vendor stack' claim

Summary

Co-managed transition | Genuinely a core, confirmed architectural option - the platform explicitly supports choosing a co-managed model alongside the confirmed fully-managed default, giving customers a real, structured path to increase direct involvement over time if desired | Existing tools/processes reviewed against Open Systems' co-managed model | Customer chooses desired level of involvement | Mission Control (co-managed mode) | Not quantified | N/A | N/A | A specific, confirmed, real architectural option - genuinely credible evidence that this platform accommodates a spectrum of customer involvement rather than being strictly all-or-nothing.

Summary

Mature NetOps/SecOps team | Conditional fit | Mature teams get real, confirmed flexibility via the confirmed co-managed option for direct involvement, though this platform's core, most extensively evidenced strength centres on fully-managed delivery rather than deep, named technical differentiation for sophisticated in-house teams wanting maximum self-directed control | Mature teams benefit from familiarity with the confirmed co-managed model specifically | Not assessed | Table 6, 9 findings | A reasonable fit specifically for mature teams wanting the co-managed flexibility option; teams wanting maximum self-directed, self-managed control should confirm this platform's fully-managed default model fits their preference.

Summary

Procurement watch-out | The confirmed subprocessor disclosure (Cyolo Security for ZTNA, Avira for SWG antivirus) means buyers evaluating this platform as a fully native, single-vendor security stack should confirm the practical implications directly - including support-escalation accountability when an issue originates in a partner-delivered component specifically | Buyers should ask directly how support and SLA accountability work when an issue traces back to a partner-delivered component, rather than assuming the same escalation path applies uniformly across every platform layer | Most relevant to buyers with strict single-vendor-accountability requirements, or those specifically evaluating vendor lock-in and dependency risk | Table 3, 12, 19 findings | Medium-High | A specific, worth-flagging nuance - this is not necessarily a weakness (partner-delivered components can reflect a sensible best-of-breed choice for specific functions), but buyers should understand the practical support implications directly rather than assume full, single-vendor accountability by default.

Buyers should ask directly how support and SLA accountability work when an issue traces back to a partner-delivered component, rather than assuming the same escalation path applies uniformly across every platform layer

Summary

Most credible differentiator | A specifically-named, quantified, consistently-evidenced fully-managed operations model - Mission Control's 8-minute escalation commitment and Level-3-only engineer staffing - reinforced by five real, named customer case studies with several quantified outcomes, rather than a generic 'great managed service' claim. | Tables 8, 18, 19 | High | This is the single sentence Netify's comparison engine could most confidently quote for this vendor specifically.

This is the single sentence Netify's comparison engine could most confidently quote for this vendor specifically.

Summary

VPN to ZTNA migration | Evidenced via the confirmed Zero Trust Service / Truly Universal ZTNA product, though a named customer case study specifically describing VPN retirement wasn't found in this pass | Existing VPN infrastructure retired | IT team | Mission Control | Not quantified with a specific timeline | Not itemised | Not detailed | Real, confirmed product capability exists; a named customer case study specifically for this exact migration scenario wasn't found in this pass, a genuine, specific gap worth noting.

Summary

Reporting reality | Strong specifically for network health, application/user-experience visibility, and site/circuit performance, reinforced by real, named customer evidence and a specific, named Microsoft Sentinel integration for MDR+; weaker or unconfirmed on compliance reporting, executive dashboards, and scheduled/custom reports, none of which were confirmed as distinct, named products in this research pass. | Table 10 | Medium-High for network/user-experience reporting; Low for compliance/executive reporting | Present the network-visibility and user-experience-monitoring strengths specifically rather than imply comprehensive reporting maturity across every category.

Present the network-visibility and user-experience-monitoring strengths specifically rather than imply comprehensive reporting maturity across every category.

Summary

Scope & Boundaries | Genuinely strong, named customer evidence - five real, named case studies (KEMET, Mammut, SOS Children's Villages, Mikron, Altana) spanning manufacturing, apparel/retail, international NGO, and multi-site acquisition-integration scenarios, several with specific, quantified outcomes. | Open Systems has changed ownership twice in a short period - from EQT private equity to Swiss Post in 2024 - and appointed a new CEO in late 2025; buyers making very long-term commitments may want to understand the current owner's specific strategic intentions directly, given how recently both changes occurred.

Summary

Commercials | A confirmed 'fully OPEX cost model', per Gartner Peer Insights' own hosted product description - a specific, distinctive commercial positioning point for buyers wanting to avoid capital expenditure on networking/security infrastructure entirely. | No first-party, published pricing was found in any source reviewed in this research pass, consistent with the pattern across most vendors in this category.

Summary

Highly distributed branch estate | Strong fit, extensively evidenced | The confirmed Altana case study (60+ locations, including newly-acquired sites) and the confirmed Mission Control global operations model together give this buyer profile genuine, specific, quantified evidence | Very low, given the confirmed fully-managed model | Not itemised | Table 4, 14 findings | One of the more specifically-quantified branch-estate findings in this profile - real, named-scale (60+ locations) evidence rather than a generic capability claim.

Summary

Mid-market | Good fit, evidenced | Real, named customer examples (Mikron, KEMET) suggest genuine mid-market applicability, reinforced by the confirmed fully-managed model's appeal to organisations without large internal IT/security teams | Benefits from, but doesn't strictly require, extensive internal networking expertise given the confirmed managed model | Not itemised | Table 14, 18 findings | Real, credible fit for this buyer profile, backed by named case-study evidence.

Summary

Multi-vendor SASE integration | Not a primary emphasis of Open Systems' own positioning in the sources reviewed, which centres on a single-vendor, fully-managed SASE platform rather than explicitly marketed best-of-breed pairings with named third-party SASE/SD-WAN vendors - though the confirmed subprocessor disclosures (Cyolo Security for ZTNA, Avira for SWG antivirus) show the platform itself already incorporates named third-party technology internally | Existing security tools already in place | Not itemised | Not itemised | Not quantified | N/A | N/A | A specific, worth-stating architectural-philosophy distinction - Open Systems presents a single, unified, fully-managed SASE proposition to buyers, even though internally it confirms sourcing specific components (ZTNA, SWG antivirus) from named third-party partners rather than building every layer entirely in-house.

Summary

MPLS to SD-WAN migration | Genuinely well-evidenced via a real, named, quantified customer example - Mammut 'replaced its aging WAN' with Open Systems SASE, with bandwidth management taken over in under two months | Existing WAN infrastructure retired or coexisting during transition | IT team, though substantially reduced given the confirmed fully-managed model | Mission Control (fully managed) | Genuinely well-evidenced - 'in less than two months, we took over bandwidth management' | Not itemised | The confirmed fully-managed model shifts most migration-execution risk to Open Systems' own Mission Control team | One of the better-evidenced migration scenarios in this profile - a real, named customer directly describing WAN replacement with a specific, quantified timeline.

Summary

AI reality | A real, direct, primary-sourced confirmation of AI/ML investment supporting Mission Control's proactive and reactive operations, reinforced by real, independent, verbatim customer-review language describing reduced operational complexity; a single, separately-branded AI product name (comparable to some competitors' named AI products) was not independently confirmed in this pass. | Table 11 | Medium-High | Represent the confirmed, real AI/ML investment with genuine confidence, while being clear that a single, distinctly-branded AI product name wasn't independently confirmed - the evidence here is genuine but framed generally rather than around one flagship product.

Represent the confirmed, real AI/ML investment with genuine confidence, while being clear that a single, distinctly-branded AI product name wasn't independently confirmed - the evidence here is genuine but framed generally rather than around one flagship product.

Summary

Merger/acquisition integration | Genuinely and specifically evidenced - the confirmed Altana case study directly describes securely integrating 'new acquisitions' as part of the same 60+-location deployment | Newly-acquired sites' existing network infrastructure integrated or replaced | Mission Control (fully managed) | Mission Control | Not quantified with a specific integration timeline | Not itemised | Not detailed | A specific, real, named-context example of exactly this scenario - genuinely credible, concrete evidence rather than a generic capability claim, reinforced by the vendor's own recent, direct experience of being acquired (Swiss Post, 2024) - worth noting as parallel, if unrelated, context.

Summary

Security & Analytics | A confirmed single-pass architecture spanning SD-WAN, SWG, firewall, NDR and unified threat detection together, reinforced by Gartner Peer Insights' own hosted description of 'no service chaining' for improved line-rate performance. | An independent source citing Open Systems' own subprocessor statement confirms ZTNA and SWG antivirus scanning are delivered through named third-party partners (Cyolo Security and Avira respectively) rather than fully in-house - a genuine, worth-understanding architectural characteristic rather than a fully native, single-vendor stack in every respect.

Summary

Lean IT team | Strong fit, extensively evidenced | The confirmed, extensively-evidenced fully-managed Mission Control model, with a specific, quantified 8-minute escalation SLA and Level-3-only engineer staffing, directly and consistently supports a genuinely low-operational-burden story throughout this entire profile | Minimal training investment implied by the confirmed fully-managed default model | Not assessed | Table 8, 9 findings | Genuinely one of the strongest, most consistently-evidenced buyer-profile fits in this entire profile - this vendor's core identity centres on minimising exactly this buyer type's operational burden.

Summary

Commercial reality | No pricing exists for this platform in any source found in this research pass, though the confirmed 'fully OPEX cost model' and the confirmed multi-product structure (SASE Experience, Managed Universal SSE, MDR+, Zero Trust Service) give buyers some real, useful commercial framing even without published figures. | Table 16 | Medium (confident about the absence of published pricing, and about the confirmed OPEX-model and product-structure detail) | Route any budget conversation to a direct Open Systems quote from the very first interaction - Netify currently has no benchmark figure of any kind to offer a buyer for this vendor.

Route any budget conversation to a direct Open Systems quote from the very first interaction - Netify currently has no benchmark figure of any kind to offer a buyer for this vendor.

Summary

When would Netify recommend looking elsewhere? (mandatory) | When a buyer needs confirmed, current FedRAMP, SOC 2, PCI DSS, or HIPAA certification; when a buyer specifically wants a fully self-service, minimally-managed platform rather than the confirmed, consistently fully-managed default model; or when a buyer wants a fully native, single-vendor security stack with no confirmed third-party component delivery. | Synthesis of Tables 3, 6, 13 | Medium-High | Each trigger is tied to a specific, evidenced gap rather than a generic 'consider alternatives' hedge.

Each trigger is tied to a specific, evidenced gap rather than a generic 'consider alternatives' hedge.

Summary

Global fit | Confirmed, specific global scale (approximately 10,000 deployments across 180+ countries), reinforced by real, named customer deployments spanning multiple continents, with Europe specifically the strongest-evidenced region given the company's Swiss origin and headquarters. | Table 7, 14 | High for Europe specifically; Medium for global reach generally; Low for country-level specificity outside Europe | The confirmed European/Swiss strength is worth highlighting directly for any buyer with a European or data-sovereignty-adjacent preference; always verify other-region delivery capability directly with Open Systems.

The confirmed European/Swiss strength is worth highlighting directly for any buyer with a European or data-sovereignty-adjacent preference; always verify other-region delivery capability directly with Open Systems.

Summary

Limitation | Two changes to the company's ownership and leadership structure occurred in a relatively short period - EQT's exit and Swiss Post's acquisition in 2024, followed by a new CEO appointment (Dennis Monner) in late 2025 | Buyers making very long-term commitments face genuine, if manageable, uncertainty about the current owner's specific strategic intentions, given how recently both changes occurred | Affects buyers prioritising long-term vendor stability and roadmap predictability as a selection criterion most specifically | Table 1 findings | Medium (the events themselves are well-corroborated across multiple sources; their long-term strategic implications are inherently forward-looking and not something this research pass can resolve) | Worth flagging directly, though tempered by the fact that Swiss Post is a stable, state-backed institution rather than a typical private-equity owner with a defined exit timeline - a genuinely different, and arguably more stable, ownership profile worth understanding on its own terms.

Buyers making very long-term commitments face genuine, if manageable, uncertainty about the current owner's specific strategic intentions, given how recently both changes occurred

Summary

When would Netify recommend it? (mandatory) | When a buyer specifically wants genuinely fully managed SASE delivery with concrete, quantified operational commitments; when a buyer is a large, multi-site, or internationally-distributed organisation wanting proven, at-scale evidence; or when a buyer has a specific preference for a European/Swiss-oriented, state-backed provider. | Synthesis of Tables 1, 8, 14, 15 | High | A clear, actionable recommendation trigger set for Netify's comparison tool to apply directly.

A clear, actionable recommendation trigger set for Netify's comparison tool to apply directly.

Summary

Remote-user-heavy organisation | Unknown - thin evidence specifically for the remote-user/client side of the platform (see Table 5) | Not assessed with confidence | Not assessed | Not assessed | Table 5 findings | A genuine, specific evidence gap - this profile's research skewed toward the site-to-site SD-WAN, managed-operations, and branch-connectivity sides of the platform, leaving remote-user/client-side evidence comparatively thin.

Summary

Deployment reality | Genuinely well-evidenced as low-effort and effective, backed by real, named, quantified customer deployments - Mammut's under-two-month WAN replacement and Altana's 60+-location, acquisition-inclusive rollout are both specific, credible, concrete examples rather than generic capability claims. | Table 4, 9, 17, 18 | High | Present the deployment evidence with genuine confidence, backed by specific, named, quantified outcomes across two genuinely distinct scenarios.

Present the deployment evidence with genuine confidence, backed by specific, named, quantified outcomes across two genuinely distinct scenarios.

Summary

Limitation | No FedRAMP, SOC 2, PCI DSS, or HIPAA certification was found confirmed in any source reviewed in this research pass, consistent with the company's primarily European/Swiss orientation | US-regulated and US-federal buyers cannot currently verify these specific certifications for this platform from public sources | Affects US federal government and US-regulated-industry buyers most specifically and directly | Table 13 findings | Medium-High (confident about the absence found in this specific research pass, though this may reflect a research-pass limitation or a genuinely European-market-focused certification strategy rather than confirmed permanent absence) | A specific, worth-flagging gap Netify should raise directly and early with any US-regulated or US-federal buyer evaluating this platform.

US-regulated and US-federal buyers cannot currently verify these specific certifications for this platform from public sources

Summary

Regulated organisation | Conditional fit, strongest for European/ISO 27001-relevant requirements specifically | ISO 27001 is confirmed directly via a dedicated, primary-sourced certification page; SOC 2, PCI DSS, HIPAA, and - most notably - FedRAMP were not confirmed | Buyer must independently verify sector-specific compliance status directly with Open Systems for anything outside the confirmed ISO 27001 scope | Not assessed | Table 13 findings | A real, confirmed ISO 27001 foundation exists, tempered by the specific, worth-flagging absence of US-centric certifications (FedRAMP, SOC 2, HIPAA) - a real, important distinction for any US-regulated or US-federal buyer specifically.

Summary

Global multinational | Strong fit, evidenced | Confirmed approximately 10,000 deployments across 180+ countries, reinforced by real, named customer examples spanning multiple continents and, in Altana's case, direct acquisition-integration across 60+ global locations | Needs Netify/buyer to verify specific-country coverage directly, given the Table 7 general-versus-specific coverage-detail gap | Custom enterprise pricing | Table 7, 14 findings | Genuinely well-evidenced multinational capability, reinforced by specific, named customer deployments spanning multiple distinct global regions.

Summary

SME | Conditional fit | The confirmed fully-managed model reduces internal skill requirements to near zero, though the platform's evidenced customer base (KEMET, Mammut, SOS Children's Villages, Mikron, Altana) skews toward genuinely large, multi-site, or internationally-distributed organisations rather than small businesses specifically | Minimal internal skills needed given the confirmed fully-managed model | No confirmed entry-level pricing tier or SME-specific positioning found in this pass | Table 14, 18 findings | A reasonable, though not extensively evidenced, fit - this vendor's evidenced case-study base and enterprise-oriented positioning suggest it may be better suited to larger, more complex estates than to the smallest SMEs specifically.

Summary

Strength | Five real, named customer case studies (KEMET, Mammut, SOS Children's Villages, Mikron, Altana) - genuinely more than found for most vendors in this category - several with specific, quantified outcomes (KEMET's 50% cost reduction, Mammut's under-two-month deployment, Altana's 60+ integrated locations) | Buyers get concrete, checkable, named-customer proof across a genuine variety of scenarios (cost reduction, WAN replacement speed, global NGO operations, OT/manufacturing security, M&A integration) rather than a single, isolated reference | Best: any buyer wanting named-customer evidence across multiple distinct scenarios before committing. Less relevant: N/A - this benefits any evaluation | Table 18 findings | High | Genuinely one of the richer, more varied case-study sets found in this research pass - five distinct, named, real customers spanning five different scenarios is a real, substantive evidence base.

Buyers get concrete, checkable, named-customer proof across a genuine variety of scenarios (cost reduction, WAN replacement speed, global NGO operations, OT/manufacturing security, M&A integration) rather than a single, isolated reference

Summary

Biggest operational advantage | A confirmed, specific, quantified 8-minute ticket-escalation commitment combined with real, verbatim customer-review language directly praising reduced operational complexity - concrete, real-customer evidence rather than only marketing language. | Table 8, 9 | High | Directly quotable with the specific, quantified SLA and real, verbatim customer-review language for credibility.

Directly quotable with the specific, quantified SLA and real, verbatim customer-review language for credibility.

Summary

What implementation challenges should buyers expect? (mandatory) | Expect a genuinely low-effort deployment experience under the confirmed fully-managed default model, reinforced by real, named, quantified customer examples (Mammut's under-two-month WAN replacement). Expect a real, confirmed choice between fully-managed and co-managed delivery for buyers wanting more direct involvement. Expect the commercial conversation to require a direct Open Systems engagement from the start, given the complete absence of published, first-party pricing. | Tables 6, 9, 16, 17 | Medium-High | Each expectation is traceable to a specific, evidenced finding elsewhere in this profile.

Each expectation is traceable to a specific, evidenced finding elsewhere in this profile.

Summary

Where does it stand out? (mandatory) | A specifically-named, quantified, extensively-evidenced fully-managed operations model (Mission Control); five real, named customer case studies spanning genuinely varied scenarios with several quantified outcomes; and a genuinely rare degree of architectural transparency about partner-delivered components (Cyolo Security, Avira). | Tables 8, 12, 18, 19 | High | These are the claims Netify can make most confidently and specifically to buyers, each backed by named, dated, primary-sourced or credible independent evidence.

These are the claims Netify can make most confidently and specifically to buyers, each backed by named, dated, primary-sourced or credible independent evidence.

Summary

Questions Netify still cannot verify | Current FedRAMP, SOC 2, PCI DSS, HIPAA, GDPR-specific-attestation, NIS2, and DORA status; specific, published pricing figures at any tier; the current, confirmed scope of native-versus-partner-delivered components beyond ZTNA and SWG antivirus; Swiss Post's specific strategic intent for the company; and remote-user/BYOD-specific client/agent technology detail. | Synthesis of Tables 5, 12, 13, 16 | N/A - explicitly unresolved | This list should drive the next follow-up (a direct Open Systems briefing) before this profile is considered fully closed out, particularly the compliance-certification and partner-component-scope questions given their direct relevance to regulated-sector and vendor-dependency-sensitive recommendations.

This list should drive the next follow-up (a direct Open Systems briefing) before this profile is considered fully closed out, particularly the compliance-certification and partner-component-scope questions given their direct relevance to regulated-sector and vendor-dependency-sensitive recommendations.

Summary

Large enterprise | Strong fit, extensively evidenced | Real, named, large-scale customer examples (Altana's 60+ locations, SOS Children's Villages' worldwide operations) directly demonstrate genuine large-enterprise, multi-site capability | Requires coordination between internal IT and Mission Control, though substantially reduced by the confirmed fully-managed default | Custom enterprise pricing likely, under the confirmed OPEX model | Table 7, 14, 18 findings | Genuinely one of the stronger large-enterprise findings in this profile - real, named, large-scale customer evidence rather than only architectural claims.

Summary

Sector fit | Manufacturing and non-governmental organisations are the best-evidenced sectors in this profile, each backed by a real, named, credible customer (Mikron, SOS Children's Villages respectively); retail/consumer goods and logistics/multi-site operations are also well-evidenced via named customers (Mammut, Altana); financial services and higher education are confirmed as general customer-base sectors without named individual case studies to the same depth. | Table 14 | High for manufacturing, NGOs, retail, and logistics; Medium for the generally-confirmed sectors; Low for sectors with no evidence | The five named case studies together span a genuinely diverse set of sectors - worth highlighting the specific, matching case study directly to any buyer in one of these confirmed sectors.

The five named case studies together span a genuinely diverse set of sectors - worth highlighting the specific, matching case study directly to any buyer in one of these confirmed sectors.