Skip to content

Architecture

A transparent, auditable architecture with separate management and data planes.

Reference architecture

An overview of the core layers and their functions.

  • Data plane: mail, files, working together, AI inference
  • Management plane: identity, policy, audit, monitoring
  • Network plane: a gateway that checks every request
  • Operations plane: MSP workflows and reporting

Architecture principles

Transparency, separation and auditability.

The architecture is designed to keep data flows transparent and to simplify compliance.

We separate management, data and network so that each plane has its own controls and logs.

The stack stays modular so that organisations can migrate in phases.

  • Management and data logically separated
  • TLS by default
  • Open standards for export

Architecture in three dimensions

Transparent separation of management, data and network.

Layer model
Layer model

Management plane (identity, audit, policy), data plane (mail, files, AI) and network plane separated, each with its own access controls and audit logging.

Data flow and access
Data flow and access

All data flows run through authenticated API gateways. No direct database access from outside. In transit TLS 1.2 or higher, TLS 1.3 is supported. Cloudflare (US) sits at the edge of the network, for DNS and secure connections. Backups are stored in the Hetzner data centre in Falkenstein (Germany). Backups have been stored encrypted.

Backup and recovery
Backup and recovery

Backups in the Hetzner data centre in Falkenstein (Germany), on a separate disk and VM. Every night an encrypted copy of the databases and the mail goes to separate object storage at Hetzner, outside this server and also in Falkenstein.

Management vs data plane

Separation of management and user data.

PlaneFunctionSecurity
Management planeIdentity, policy, auditMFA, least privilege
Data planeMail, files, AI inferenceTLS, ACLs
Network planeRoutingGateway

Resilience and DR

Continuity during outages and incidents.

  • Backups in the Hetzner data centre in Falkenstein (Germany), on a separate disk and VM
  • Every night an encrypted copy of the databases and the mail in separate object storage at Hetzner, outside this server and also in Falkenstein
  • Monitoring with Prometheus and alerting by push message and email; no 24/7 on-call

Integration layer

Open standards and exportable data.

  • OIDC for one Noveu login
  • Open standards for mail and file formats
  • Audit log per organisation, exportable as CSV
  • After termination, your data back on request (CSV, JSON, SQL, MBOX for mail)

FAQ

Frequently asked questions about the architecture.

Is the stack modular?
Yes, modules can be introduced in phases.
Can we start with a hybrid setup?
Yes. After termination, we make your data available on request within 30 days (CSV, JSON, SQL, MBOX for mail), delete it within 30 days and overwrite backups after 90 days at the latest.
Is there a standard reference design?
Yes, through the architecture reference resource.