Small teams
Teams of five to fifteen people who want their own platform, without depending on shared third-party services.
Island S
The island in its most direct form: dedicated critical infrastructure, on a single server, for teams that need control and a clean exit without running a fleet.
THE APPROACH
The minimum, done with discipline.
Island S is the entry point to the product. A complete infrastructure, dedicated to a single client, reduced to the essentials and built with the same discipline as the larger islands. It is not a cut-down version or a pilot: it is a real island, with its own identity, its verified backups and its recovery test, at the scale of a small team. Sovereignty over infrastructure does not depend on the size of the budget. It depends on the method, and the method is the same across all three islands.
THE FORM
A single dedicated server.
Island S runs on a single server dedicated to one client. It shares resources with no one. It is the simplest form of the product, and it is worth stating clearly what that implies: Island S is not highly available. Scheduled maintenance is carried out in a downtime window agreed in advance, and a server failure interrupts the service until recovery is complete. In return, it is the most direct and contained way to have a genuinely sovereign platform.
- Servers
- A single dedicated server
- High availability
- No
- Environments
- Production
- Recovery test
- Real, before delivery
- Exit guarantee
- In writing, from the start of the contract
FOR WHOM
Who it fits.
Island S fits whoever needs their own controlled infrastructure, without the load of operating something large.
A first island
Organizations taking their first step toward sovereign infrastructure, who prefer to start contained, with the option to grow later.
Contained sensitive work
An internal portal, a team tool or a repository of sensitive data that must live on infrastructure that is owned and auditable.
WHAT IT INCLUDES
What goes into Island S.
Everything that defines an island, at its compact scale.
Dedicated infrastructure
Its own server, storage and network, with no co-tenancy with any other client.
Unified identity
A single identity gate for the island's applications, with second-factor authentication.
Encrypted, verified backups
Encrypted backups, checked on a regular basis to confirm that they truly restore.
Recovery test
Before delivery, the island is rebuilt in full and data is confirmed to return without loss.
Production environment
A stable, dedicated environment where the team's real work runs.
Exit guarantee
The client can take the island away, documented and rebuildable without Kverno. Set in writing from the start.
External vigilance
The island is watched from outside, continuously. If anything fails, the operations team gets an immediate alert, even when the island itself is down. The scope and alert times are set in writing in the contract.
WHAT IT RUNS
Applications that fit.
Island S is sized for contained workloads. It is a solid base for internal portals, working dashboards, team tools and light security applications. The more demanding threat-analysis platforms, with many dependencies, call for the capacity of Island M.
Portals and internal tools
Working dashboards, team portals and internal utilities on a stable, dedicated base.
Light intelligence
Threat-analysis platforms in their most contained form, such as MISP in a bounded installation.
Sensitive data
Repositories and applications handling sensitive information that must live on owned, auditable infrastructure.
THE LIMITS
What Island S does not solve.
It is worth being explicit. Island S is not highly available: maintenance involves an agreed downtime window, and a server failure stops the service until recovery is complete. Nor is it sized for intelligence platforms with many dependencies in production. If the work cannot take a planned stop, or if the load is demanding, the right island is M or L. Saying so from the start is part of the product.
HOW IT GROWS
From Island S to Island M.
An island does not lock its client into one size. Island S can grow toward Island M when the load increases or when more capacity is needed, without rebuilding the system and without redoing the work. The build method and the recovery test are the same across all three islands; what changes is the capacity. Starting with Island S closes no doors: it is a decision about scope, and scope can be widened.
Does Island S fit?
Tell us your case and we will say whether Island S is the right one, or whether your work calls for a larger island.