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.