ARCHITECTURE AND OPERATIONS

100% European Architecture

We design the architecture that runs your applications and prepare their long-term operation. Hosting, storage, backups and AI services rely on European providers; data is separated by purpose, access and recovery are documented, and operating costs are tracked. This organisation supports GDPR compliance. European providers are our default choice; the same architecture can also run on other clouds and with other AI models.

Discuss your project Explore HyDE and RAG search

REFERENCE ARCHITECTURE

A business application and its European services

The diagram shows a typical architecture for a custom business application, such as an HR application. The application, its PostgreSQL database, antivirus scanning of documents (CVs, for example) and monitoring run on a European server; email delivery, AI processing and backups are handled by separate European services. Embedding computation on a private server is available as an option. The Hub runs on this architecture. Services, regions and responsibilities are defined during the scoping of each project.

Scroll the diagram horizontally

EUROPEAN SERVICES

Choose services and their boundaries

Hetzner or OVHcloud for the application and its data; Scaleway for separate storage or backups; Mistral for AI processing; Brevo or Scaleway for email delivery: the proposed architecture uses European services. Regions, flows and contractual terms are defined explicitly for each component.

Original documents remain in private encrypted storage, with downloads controlled by the application. Only prepared, authorised text feeds AI search. The website hosted on Cloudflare and Stripe payments are separate from this architecture.

These are the services we propose by default. The architecture relies on open standards (Docker containers, PostgreSQL, S3-compatible storage, SMTP, AI model APIs), so it can be deployed with any provider that supports them, in Europe or elsewhere, including AWS, Azure or Google Cloud, and can use AI models other than Mistral. The hosting provider, model provider or S3 storage the client already uses can therefore be retained. The location and terms of each service are then checked during scoping.

Explore RAG filtering and pseudonymisation

OPERATIONS

Prepare service continuity

Back up and verify

Encrypted external copies, freshness checks and documented recovery procedures. A backup must be restorable and verifiable.

Monitor and act

Availability, resources, databases, certificates and backups: useful alerts, defined actions and verified recovery.

Prepare changes

Separate environments, fictional or anonymised test and acceptance data, and validation before release. Accounts and access remain controlled.

Check
Availability, resources, certificates and backups.
Alert
An actionable signal with a named owner.
Act
Intervention or recovery following procedures.
Verify
Verified return to service and documented status.

Operations · Checks connected to actions to support continuity and make service health understandable.

GDPR AND REVERSIBILITY

Governance, handover and operating cost

GDPR connects minimisation, purposes, individual rights, access and retention periods. Pseudonymisation does not remove data from the protection scope. Responsibilities and rules for other content are explicitly defined.

Depending on the hosting model, accounts are opened in the client’s name or managed by us on shared infrastructure. In both cases, architecture documentation and data exports make it possible to move to another provider. The budget distinguishes hosting, storage, backups, AI calls and maintenance. This approach also supports document collections, portals and integrations.

The Hub project

Connect these choices to your service with GDPR consulting

Let’s discuss your project

Let’s design your architecture.

Tell us about the services you need and how they will be operated. We can propose a suitable architecture, European by default or deployed on the cloud you already use.

Discuss your project