Security & Trust · Hosting
An infrastructure whose boundaries can be explained.
The hosting architecture is designed to separate simulation environments, control where processing takes place and make technical dependencies explicit. The level of isolation depends on the configuration actually deployed.
Client
Application access, questions and engagement parameters.
Imagine All The People environment
Application, orchestration, compute and storage used for simulations.
Required services
Hosting infrastructure and language models, depending on the deployment mode.
Five layers, from application to infrastructure.
Application
Interface, constrained population construction, simulation execution and delivery of results.
Layer: application
Orchestration
Coordination of processing, calls to language models, and execution management.
Statut : CONFIGURABLE
Compute
Compute resources used for simulations.
Statut : CONFIGURABLE
Storage
Working data and engagement results.
Statut : CONFIGURABLE
Infrastructure
Servers, network and data center, operated by an infrastructure provider or by the client.
Layer: infrastructure foundation
“Dedicated” must have a defined scope.
A dedicated component does not automatically mean that the entire chain is physically isolated.
Application environment
Environment specific to the engagement, with logical separation in all modes.
Statut : EN PLACE
Compute / storage
Shared in the hosted configuration; reserved or provided by the client in other modes.
Statut : CONFIGURABLE
Network / infrastructure
Depends on the selected provider or the client's infrastructure.
Statut : CONFIGURABLE
Administration
Operated by our teams in the hosted configuration, and by the client in other modes.
Statut : CONFIGURABLE
Three documented configurations.
These configurations address different constraints; they are not a quality scale.
Environment hosted by us
Where?
France
Who administers it?
Our teams
What is dedicated?
Application environment; shared compute and storage
Deployment on client infrastructure
Where?
Determined by the client
Who administers it?
The client, with support
What is dedicated?
Compute and storage provided by the client; remote access scoped and logged
Deployment isolated from any external network
Where?
Determined by the client
Who administers it?
The client, operating independently after deployment
What is dedicated?
Infrastructure separated from external networks; open-source models run locally
The last two modes are scoped case by case, following an architecture review.
Delegating hosting does not transfer every responsibility.
Choice of mode
Client
Decides
Imagine All The People
Scopes and documents the options
Infrastructure provider
—
Administration
Client
When deployed on its infrastructure
Imagine All The People
In the hosted configuration
Infrastructure provider
Hardware and network foundation
Updates
Client
Approves maintenance windows for client deployments
Imagine All The People
Provides and applies versions
Infrastructure provider
Maintains the foundation
Deletion
Client
Requests it, and performs it on-premise
Imagine All The People
Performs it according to the terms set out in the contract
Infrastructure provider
—
Where processing takes place, and what it depends on.
- Documented location
- The imagineallthepeople.io website and the simulation environments we operate are hosted in France.
- Provider
- Public website hosted by OVH SAS (France).
- Potential external models
- Depending on the model selected, a non-European proprietary model may involve processing outside the EU.
- Client deployment
- Location and operator determined by the client.
Hosting in France covers the website and the environments we operate; on its own, it does not establish sovereignty. Regulatory traceability →
What is not certified to date.
- ISO 27001
- Not certified to date.
- SecNumCloud
- Not qualified to date.
- HDS
- Not certified to date.
Any certifications held by a provider cover that provider's own scope and do not constitute certification of Imagine All The People.
Dedicated ≠ invulnerable
Reserved resources reduce some co-tenancy exposure, but the environment remains exposed to operational risks.
Located ≠ sovereign by definition
The location of a data center describes neither software dependencies, nor the choice of language model, nor the applicable contractual terms.
Hosting ≠ application security
The hosting architecture does not cover application and operational controls, which are described on the Operational Security page.
Continue
Understand what data enters the system.
View →See how the infrastructure is protected day to day.
View →Understand the compliance scope and the available evidence.
View →Need to validate the architecture with your CISO? Our teams work with your security and infrastructure leads to scope a configuration suited to your constraints.
Talk to our team →Your next decision
Which decision do you want to explore?
Describe your need. We can point you to the right level of support.
