Block [0·0·0] · Foundation Product infrastructure

MATE Hub: Isolated Integration Data Plane for ERP Connectors.

MATE Hub behind hub.mateit.de bundles OAuth broker, AES-256-GCM token vault, ClamAV virus scan, background jobs, and package store inside strictly separated infrastructure. Your ERP remains the leading source of truth — with no scattered API keys or unverified custom scripts.

Transport, not archiveIn-transit processing & auto-purge
AES-256-GCM & ClamAVEnvelope vault & fail-closed scan
Odoo 19 & 20 ReadyThin clients & package store /v1/modules
hub.mateit.de · Data Plane Architecture EU Hosting
MATE Hub · Isolated Data Plane TLS 1.2+ / RLS No-Archive ERP THIN CLIENT Odoo 19 / 20 GoBD in ERP EXTF & Export Log 1 Instance Key mh_... / Bridge Key Multi-Company X-Odoo-Company-Ref No OAuth Secrets DATA PLANE · HUB.MATEIT.DE Services & Security OAuth Broker 1 Redirect URI Auto-Refresh Token Vault AES-256-GCM Isolated KEK ClamAV Scan Fail-Closed EXTF & PDFs Celery Worker Retry-After Audit Log Package Store /v1/modules Canonical Odoo Bundles & Releases EXTERNAL APIS Partner APIs DATEV API EXTF & Docs ITscope / EDI Isolated DBs Control Plane mate-core isolated Portal & Rights Core rule: Payloads in transit only (auto-purge ≤ 30 days) · Append-only audit without secrets
MATE Hub Traefik Routing · Service DBs · Odoo 19 & 20

Why integrations need a dedicated data plane.

API credentials hard-wired directly inside an ERP create maintenance debt on every version upgrade and token rotation. MATE Hub pulls this infrastructure layer cleanly out of your ERP.

Clear separation of Control Plane & Data Plane

Customer portal, licenses, subscriptions, and entitlements run separately in the Control Plane. MATE Hub is strictly responsible for technical integration execution, the package store, and hardened outbound API communication.

Server-side OAuth/OIDC broker

Instead of registering individual OAuth apps per customer domain with external providers, the Hub provides one verified central redirect URI. A proactive refresh daemon keeps connections stable and cleanly revokes tokens whenever needed.

AES-256-GCM vault with envelope encryption

Refresh tokens and sensitive connection credentials are encrypted per tenant using envelope encryption (per-tenant DEK, isolated KEK inside the vault). No external read endpoint exists: tokens leave the vault strictly internally toward the API gateway.

Fail-closed ClamAV virus scan before forwarding

Every outbound file — such as EXTF posting batches or PDF document images bound for DATEV — passes an automatic ClamAV scan inside the Hub. If the scanner is unreachable, the system fails closed and only retries the job after a clean check.

Celery job orchestration & append-only audit

Asynchronous transfers respect external API rate limits and Retry-After headers automatically. Every action writes an immutable audit entry with request correlation — strictly without passwords, tokens, or business payloads in logs.

Package store & canonical Odoo thin clients

Through the /v1/modules endpoint, the Hub serves versioned Odoo client bundles for Odoo 19 and Odoo 20. Your ERP modules stay lean, upgrade-ready, and require nothing more than a rotatable instance or bridge key.

Trust boundaries, data protection, and deliberate scope.

Blueprint before code matters most for infrastructure: before any tenant goes live, data ownership, retention limits, and operational ownership are agreed in writing.

When it fits & prerequisites

MATE Hub is the technical foundation for companies that want to operate production MATE connectors such as DATEV in Odoo 19 or Odoo 20 securely, with strict tenant isolation and without managing their own OAuth app registrations.

  • Clean data ownership inside your ERP: EXTF generation, charts of accounts, GoBD export logs, and document archives remain completely inside your ERP database.
  • Separate service databases: Every connector service runs with its own database, vault namespace, and Row Level Security (tenant_id) — with zero shared tables between DATEV and other apps.
  • Single-company or multi-company: Each legal entity receives a rotatable instance key (mh_...), or multiple companies in one database connect through a bridge key with explicit company identification.
  • Contractual safeguards: Data Processing Agreement (Art. 28 GDPR), documented technical and organizational measures (TOMs), EU hosting, and defined offboarding purge (vault and payload wipe).

Limits & deliberate boundaries

MATE Hub replaces neither your ERP nor an audit archive — it specifically solves the security and operations gap between your ERP and external partner APIs.

  • Not a second accounting or document archive: Payloads exist only encrypted in transit and are automatically deleted after confirmed delivery within the agreed retention window (30 days maximum).
  • Not a generic no-code sandbox: The Hub is not a replacement for ad-hoc automation tools, but a strictly typed, audited platform built for business-critical financial and operational records.
  • No unverified AI training: Transferred financial or document records are never shared across tenant boundaries or used for AI model training.
  • Direct mode for own app registrations: Operators holding their own production app registration in the respective partner portal can continue using direct mode inside the client.

Frequently asked questions about MATE Hub.

Answers on architecture, tenant isolation, and data retention behind hub.mateit.de.

Does MATE Hub permanently store our accounting or ERP data?

No. MATE Hub operates on a transport-not-archive principle. Payloads such as DATEV posting batches or document scans are processed exclusively encrypted in transit and automatically purged under short retention rules once delivery is confirmed. GoBD-relevant archiving and export logs remain entirely inside your ERP.

Why do OAuth tokens and API calls run through the Hub instead of directly inside the Odoo module?

Because external OAuth integrations like DATEV would otherwise require a separate app registration, callback URLs, and local client secrets inside every customer ERP instance. Through MATE Hub, refresh tokens stay encapsulated inside the AES-256-GCM vault while the Odoo module communicates as a thin client using only a rotatable instance or bridge key.

How are tenants and different integration services isolated from each other?

Each integration service uses its own dedicated database, separate vault namespaces, and independent deployments. Within each service, strict tenant isolation is enforced via tenant_id and Row Level Security. There are no shared schemas between DATEV and other connectors, and no secrets or payloads ever appear in logs.

Which Odoo versions and authentication models does MATE Hub support?

The canonical MATE Hub Odoo clients support Odoo 19 and Odoo 20. Single-company setups use a dedicated instance key; multi-company databases isolate legal entities cleanly either via one instance key per company or via a cross-company bridge key using X-Odoo-Company-Ref.

Can MATE Hub also be used alongside existing systems outside Odoo?

The data plane is API-driven and cleanly separates control plane, package store, and individual connector services. Today, canonical clients for Odoo 19 and 20 are our production focus; whether connecting additional ERP or legacy systems via the Hub makes sense is something we evaluate together in an architecture call.

One real workflow is all it takes.

Planning a hardened DATEV or ERP integration on Odoo 19/20 and want to review tenant isolation, key management, and DPA upfront? Briefly describe your environment.

Matthias GrdanManaging Director · Process & ERP Architecture
Architecture & Integration TeamDedicated Project Lead · Villingen-Schwenningen

The introductory call is free of charge. Your inquiry is delivered directly via our Google Workspace mail service — or alternatively as a pre-filled email draft or one-click clipboard copy.

When an endpoint is configured, submissions are sent via our Google Workspace mail service; in local preview mode, a pre-filled email draft opens in your browser. Privacy Policy

Book a call