Apiome Wormhole
Move data across tenants and regions without ever crossing a compliance line.
Apiome Wormhole is a cross-tenant, cross-region data bridge for apiome-db. It moves rows between environments and geographies with schema-version awareness, classification-driven residency controls, bi-directional sync with conflict resolution, and an HMAC-signed audit ledger that stands up to an auditor.
What ships with Wormhole
Every Wormhole surface is wired into the rest of the Apiome platform — no glue code, no separate identity, no bolt-on integrations.
Live topology map
Animated map of every environment pair with real-time transfer flows, active-flow counts, and cross-region highlighting.
Bridge designer
Configure a source/destination pair with Class filters, one-way or bi-directional mode, and a transfer schedule.
Residency policy engine
Data classification tags assigned in the Schema Designer automatically allow or deny cross-region transfers, with CISO-gated overrides.
Schema compatibility checks
Pre-flight validation of Class versions across environments so incompatible transfers never start.
Bi-directional conflict resolution
Source-wins, dest-wins, or manual merge strategies for two-way sync between environments.
Tamper-evident audit ledger
Immutable, HMAC-SHA256 append-only record of every transfer, signed in a chain that makes tampering detectable.
A look inside Apiome Wormhole
Live design previews from the Wormhole mockup pack — 8 surfaces in total.
Classification tags (PII, Sensitive, Financial) drive automatic allow/deny decisions on every region boundary.
Validate Class version compatibility between source and destination before a single row moves.
Append-only, HMAC-SHA256 chained audit ledger with one-click compliance report export.
Use cases
Wormhole is designed around the way real teams actually work — not the way a tool wants them to work.
Seed staging and dev from production nightly with PII automatically stripped at the region boundary.
Enforce EU-to-US data residency rules declaratively and prove it with a cryptographically signed ledger.
Keep US, EU, and APAC production tenants in bi-directional sync with governed conflict resolution.
- Classification-driven residency policy with CISO approval workflow for overrides
- HMAC-SHA256 append-only audit ledger with exportable compliance reports
- Region-boundary allow/deny enforcement for PII, Sensitive, and Financial data
- Bi-directional sync with configurable conflict-resolution strategies
- Per-bridge Class filtering, scheduling, and transfer-run history retention
- Auto-suggest classification tags for new Classes from their properties
- Flag transfers likely to violate residency policy before they execute
- Recommend conflict-resolution strategy per Class from historical sync patterns
- Summarize audit-ledger activity into plain-language compliance narratives
AI residency and transfer copilot
Wormhole uses AI to classify data, flag risky transfers before they run, and explain policy decisions in plain language so operators and auditors stay in sync.
Every WormholeAI feature is grounded in your tenant's data, runs under your data-residency policy, and respects every role and ACL the platform enforces.
Every surface in Apiome Wormhole
A look at the 8 screens designed for this suite — covering everything from day-1 onboarding to day-100 operations.
