Intelligence teams
Teams running threat-analysis and correlation platforms, such as OpenCTI or MISP, in production.
The island where the real work happens: genuine capacity to run intelligence and security platforms in production, on a single high-capacity dedicated server.
Island M is the workhorse of the product. Where Island S offers a sovereign platform in its most contained form, Island M brings the capacity to sustain the real work of an intelligence or security team: full threat-analysis platforms, with their databases, their queues and their processes, running in production day after day. It is the island for those who already know what they need to run and want to do it on infrastructure that is owned, controlled and auditable.
Island M runs on a single dedicated server, sized with headroom for demanding workloads. It shares one characteristic with Island S, and it is worth saying clearly: Island M is also not highly available. Scheduled maintenance is carried out in an agreed downtime window, and a server failure interrupts the service until recovery is complete. The difference from Island S is in capacity. Resilience against a failure is what Island L brings.
Island M fits teams that run demanding tools and want to do so on their own infrastructure.
Teams running threat-analysis and correlation platforms, such as OpenCTI or MISP, in production.
Security teams that need capacity for their monitoring, logging and response tools.
Small firms working with sensitive data who prefer a dedicated platform over shared services.
Everything in Island S, plus the capacity and the staging environment that serious work calls for.
Dedicated infrastructure, unified identity with a second factor, encrypted and verified backups, a recovery test and an exit guarantee.
Headroom to sustain intelligence platforms with their databases, their queues and their processes, in production.
An environment separate from production, where the client team validates changes before taking them live.
A problem in the staging environment does not reach production. The real work stays protected from the trials.
Island M is sized for the full intelligence and security platforms, the ones Island S cannot sustain. It is the island where the real analysis work runs.
Full intelligence platforms, such as OpenCTI or MISP, with all their dependencies in production.
Monitoring, centralized logging and response tools for the security team.
Portals, dashboards and team tools, alongside the island's main platforms.
Island M gives working capacity, not uninterrupted continuity. It is not highly available: scheduled maintenance involves an agreed downtime window, and a server failure stops the service until recovery is complete. For operations where a stop is not acceptable, the right island is L, which tolerates the failure of one server without interrupting the service. Island M is the correct choice when the work is demanding and a planned maintenance window is acceptable.
Island M sits between Island S and Island L, and the difference from each is precise. Against Island S, M brings capacity: it sustains platforms that S cannot. Against Island L, it lacks resilience: L tolerates the failure of a server without stopping, M does not. An island can travel that path without being rebuilt: start at S and grow to M, or move from M to L when continuity becomes a requirement.
Tell us which platforms you need to run and we will say whether Island M is the right one for your case.