ARCHITECTURE · DARK SECTION

What runs under the hood.

An honest architecture sketch. Components, data flows, cryptographic boundaries. When you need an architecture answer to a regulatory outsourcing question, this is the page you open.

Book an architecture review contact@dxzio.one

ARCHITEKTUR · DARK SECTION

What we operate — layered, signed, in the EU.

EDGEEdge gateway · TLS termination · WAF · rate limiting · no US CDN

APPLICATIONHeadless CMS · type-safe domain logic · no SaaS platform lock-ins

AGENT RUNTIMEAgent orchestrator · WASM sandbox · policy engine

DATAManaged Postgres on block storage · EU object-storage backup · BYOK encryption

AUDITEd25519-signed event store · Merkle chain · WORM-archived (FINMA: 10y · Swissmedic: 30y)

OBSERVABILITYLogs / traces / metrics — self-hosted, in the EU

LAYER DETAIL

Explained layer by layer.

Edge

Incoming traffic runs through a Kubernetes gateway with TLS termination, WAF policies and rate limiting at IP and token level. No US CDN in the chain. Certificates come from a Swiss ACME CA via DNS-01 challenge — the DNS server is located in Switzerland.

Application

The application layer is open: a self-hosted headless CMS for content, type-safe domain logic for the business rules. Deliberately against the "platform" approach — no low-code monolith, no 200 SaaS services that suddenly mirror data to the US in the fine print.

Agent runtime

This is where the agentic logic sits: a memory-safe orchestrator, model adapters for EU-hosted models (Swiss cloud, German cloud, own inference clusters), and a declarative policy engine. An agent action is a tuple of input, model version, policy snapshot and a signed decision.

Data

Operational data in a managed Postgres cluster on block storage. Backup layer in EU object storage. Blob storage, depending on sensitivity, on our own MinIO or via an EU S3 provider. No US cloud provider in the data plane. Encryption at rest with customer-held keys (BYOK).

Audit — Merkle chain with Ed25519

This is the anchor for every regulatory statement. An audit trail is a hash chain of signed events. Each event carries: timestamp (UTC), actor, input hash, model version hash, policy version hash, decision, reasoning hash, link to the previous event. Signed with Ed25519. Keys rotate quarterly; old keys remain verifiable.

Observability

Logs, traces and metrics stay in the EU — all self-hosted, no US SaaS, no US hyperscaler touching the telemetry path. Telemetry is data; data follows the same sovereignty rules as everything else.

DEPLOYMENT

Three deployment modes.

Full-prem

Where data lives: Customer data center
Where Dxzio operates: Customer data center, with operational support
Typical customer: Banks / cantonal hospitals with absolute data residency

Hybrid

Where data lives: Customer DC (data) · EU region (control plane)
Where Dxzio operates: EU region + customer DC
Typical customer: Most insurers, larger MedTech

EU cloud

Where data lives: EU region (Helsinki)
Where Dxzio operates: EU region + Cham operations
Typical customer: FinTech, smaller MedTech, pilots

MERKLE AUDIT CHAIN

Example: audit-chain entry (redacted).

One entry in the hash chain. An auditor holding the public key for dxzio-prod-2026-01-claim-pipeline can verify the signature offline — and walk backwards via prev_event_id.

{
  "event": {
    "id": "ad_01HKTM7Z2X3F8YBPGRJ5Q0WN1A",
    "ts_utc": "2026-04-22T08:32:11.482Z",
    "actor": "claim-triage-agent@v1.4.2",
    "tenant": "REDACTED-INSURER-LI",
    "input_hash": "sha256:b3c4a912e8d4...REDACTED",
    "model_version": "claim-triage-llm@2026-03-15",
    "policy_version_hash": "sha256:9f4e7b21...REDACTED",
    "decision": {
      "kind": "auto_approve",
      "amount_chf": 1842.5
    },
    "prev_event_id": "ad_01HKTM6V8K9P2T5QZWN4HBCXMR"
  },
  "signature": {
    "alg": "ed25519",
    "key_id": "dxzio-prod-2026-01-claim-pipeline",
    "value": "Ej3cJ2UQpa9kQzlR7iVcXvP...REDACTED"
  }
}

FAQ

Six questions CISOs always ask us.

Where does the model run?

Either in our own inference cluster in an EU data center, or with a Swiss / German cloud provider without a US subsidiary in the data path. We disclose concrete providers to customers in the architecture review under NDA. US hyperscaler endpoints are never contacted without explicit customer approval — and even then only for non-personal data.

What happens when a subprocessor changes?

You are notified with 60 days' notice. An architecture change introducing a new subprocessor goes through a change advisory board with your compliance function.

How does this relate to the CLOUD Act?

We are a Swiss GmbH with no US subsidiary, no US employees, no US data. The CLOUD Act cannot reach us because no anchor exists in the US. Our subprocessors are selected by the same pattern.

How reproducible are model decisions?

Fully, as long as the model artifact remains available. We retain all model artifacts, inputs and policy snapshots in WORM storage for your industry's retention period (FINMA: 10 years · Swissmedic: up to 30 years for clinical trials).

What if you as a company disappear?

Source code, keys and data-pipeline definitions sit in an escrow agreement with a Swiss notary (Bühler & Partner, Cham). Triggers: bankruptcy, sale to a US entity, or a written release request by you. You have the full right to keep operating your own stack on your own hardware.

How do you compare to Vertex AI Agent Platform / Bedrock Agents?

We don't compare — we solve a different problem. Vertex Agent Platform and Bedrock Agents are excellent when the CLOUD Act doesn't bother you. When it does, there's us.

ARCHITECTURE REVIEW

If something on this page is wrong, write to me.

This page is deliberately detailed — a CISO deserves a sketch, not a pitch
Wrong assumption about your regulator? We'll correct it
contact@dxzio.one · reply within 24h from the founder

Book an architecture review