REVIEWITDocumentation
ConceptUp to date · verified on 14 October 2026

Choose your on-premises installation scenario

Machine translation, not yet reviewedThis page was translated by a model from the French version, which is authoritative. Read the French version.

01Two modes, four scenarios #sec_d942e224

The on-premises edition installs in two ways, of your organization's choice:

  • single server: one server handles everything;
  • 3-tier architecture: a front-end tier (your load balancer), a separate application tier and a data tier, with the level of availability you choose.
ScenarioREVIEWIT ServersAvailabilityData loss / recovery (indicative)For whom
S1 — Single server1Automatic service restart15 min / 4 hPilot, medium-sized entity, secondary site
S2 — Simple 3-tier1 application + 1 dataSeparate tiers, no redundancy15 min / 4 hOrganization that requires tier separation
S3 — High-availability 3-tier2 application + 2 data + 1 witnessLoss of one server does not interrupt service0 / 2 minProduction of a large account
S4 — HA 3-tier + PRAS3 + 1 application and 1 data on a second siteLoss of one site is recoverable5 min / 4 hRegulated sectors

Data loss and recovery values are orders of magnitude, calibrated during the pilot program.

Schéma S1 : un serveur unique porte l'accès, les services, le scellement, PostgreSQL, le coffre et les fichiers. Schéma S2 : un tier d'accès facultatif, un serveur applicatif et un serveur de données, sans redondance. Schéma S3 : répartiteur en paire, deux serveurs applicatifs actifs, cluster Windows, témoin, coffre à trois voix. Schéma S4 : site de production en haute disponibilité, site de secours avec réplique PostgreSQL et procédure de bascule.

02Moving from one scenario to another #sec_780933a9

The topology is an installation parameter, not a fixed choice at first deployment. You move from S1 to S2, from S2 to S3, then from S3 to S4 by adding servers, without reinstalling: each new server joins the existing installation with an encrypted adhesion package produced by the first server.

A pilot can therefore start as a single server and scale to high availability when moving to production.

03Option: a dedicated authority zone #sec_bed05756

Components that SEAL proofs can leave the application servers for two dedicated authority servers, in a restricted network zone. This option adds to scenarios S2, S3 or S4, for organizations that require SEAL to live separately from user services.

04Indicative sizing #sec_d063d1a9

RoleProcessorsMemoryDisks
Single server (S1)16 vCPU64 GB128 GB system, 500 GB SSD (databases, vault, files), 100 GB (logs)
Application8 vCPU32 GB128 GB system, 100 GB
Data8 vCPU32 GB128 GB system, 500 GB shared SSD (databases), 200 GB shared (files)
Witness (S3, S4)2 vCPU8 GB64 GB system, 20 GB
Authority server (option)4 vCPU8 GB64 GB system

A single server supports up to three subscriptions, an application server up to five; beyond that, count approximately 1 vCPU and 4 GB of memory per additional subscription. Database volume grows with the number of governed identities and decisions. These values are indicative: they are measured and adjusted during the pilot program.

05Which scenario to choose #sec_84e9f941

  • You are evaluating REVIEWIT, or a mid-sized entity uses it alone: S1. This is the simplest to set up and maintain.
  • Your policy requires separate third parties, with no continuity requirement: S2.
  • REVIEWIT supports production campaigns for the entire group: S3. Each application server carries the entire load; Windows patches are applied one server at a time, without interruption.
  • Your regulator requires a recovery plan on a second site: S4.

Next: prepare your information system, then the detailed architecture.

Esc
↑↓ navigate↵ openSee all results →