SYSOPERATIONAL
UPTIME99.99%
WORKERS12 ACTIVE
EDGE LATENCY42ms
PROTOv2.6
REGIONEU · DE · AT · ES
--:--:-- UTC
Cloudflare-Native · Edge Engineering · v2.6

Terminal Systems Engineering. A specialist operation.

We define what operator-grade real estate infrastructure looks like — at the highest level.

We design and build operator-grade web terminals on Cloudflare infrastructure. Protocol-driven. Edge-native. The undisputed specialist for European real estate.

View Engineering Access Criteria
worker.js · terminal_intake_v2.6
live · prod
// Cloudflare Worker · Edge Runtime
// SystemBase · Protocol Intent Router
runtimeCloudflare Workers storageKV · R2 · D1 cold_start0ms protocolintake_v2.6 accessapproval-gated statusDECISION_READY
Worker deployed · UDH-EU-1
PROD · v2.6.1
Frankfurt
12ms · DE
Amsterdam
15ms · NL
Vienna
18ms · AT
Madrid
22ms · ES
Paris
14ms · FR
Milan
20ms · IT
Cloudflare Workers V8 Isolates · Zero Cold Start Protocol-Driven Architecture iFrame Engineering Real Estate Europe Operator Terminal Systems Intent Routing · KV · R2 · D1 Private Deployment Machine-Readable Structure GDPR · IAB TCF 2.2 · LOPDGDD Approval-Gated · Territory-Exclusive SystemBase OS · Protocol v2.6 Cloudflare Workers V8 Isolates · Zero Cold Start Protocol-Driven Architecture iFrame Engineering Real Estate Europe Operator Terminal Systems Intent Routing · KV · R2 · D1 Private Deployment Machine-Readable Structure GDPR · IAB TCF 2.2 · LOPDGDD Approval-Gated · Territory-Exclusive SystemBase OS · Protocol v2.6
SYSTEM MONITOR
All systems nominal
0
Protocol Flows
≤50ms
Edge TTFB
0ms
Cold Start
0
Global PoPs
0
Operator-Controlled
1/reg
Exclusive License
Workers · Operational
KV / R2 / D1 · Nominal
iFrame Layer · Active
Protocol Engine · v2.6
System Metrics

Engineered to specification.

Response
0
TTFB at Cloudflare Edge — not origin server
Cold Start
0ms
V8 isolate execution — no container spin-up ever
Protocol Flows
0
Governed operator flows — immutable in production
Global PoPs
0
Cloudflare edge network — globally distributed
Uptime
99.99%
Operator SLA — protocol engine continuously monitored
Intent Coverage
0
Real estate anlass-specific protocol paths
Compliance
3×
GDPR · LOPDGDD · IAB TCF 2.2 certified
Territory
1/reg
Exclusive per region — enforced at infrastructure level
Deployment Coverage

European
market focus.

Territory-exclusive deployments across Central and Southern Europe. One operator per region — protocol-standardized, edge-native, IAB certified.

DE / AT / CH
Active · German-language marketsDSGVO compliant · WKO aligned
ES / IT / FR
Active · Southern European marketsLOPDGDD · Bilingual delivery
Edge nodes
FRA · AMS · VIE · MAD · PAR · MILSub-20ms to all major EU markets
FRANKFURT 12ms · DE · Primary Hub AMSTERDAM 15ms · NL VIENNA 18ms · AT · Primary MADRID 22ms · ES · Primary PARIS 14ms · FR MILAN 20ms · IT ZURICH · 16ms LEGEND ACTIVE DEPLOYMENT PRIMARY MARKET EXPANSION UNITEDDATAHUB · EU DEPLOYMENT MAP · PROTOCOL v2.6 · 6 ACTIVE NODES
Core Disciplines

What we engineer.

Six disciplines. No generalism. Every system built to production specification on Cloudflare infrastructure.

01 · Primary
Operator Web Terminals
Controlled decision interfaces embedded in operator environments. Intent capture, protocol-driven qualification, structured handoff. No free-text. No ambiguity.
SystemBase OS25+ ProtocolsiFrame
02 · Infrastructure
Cloudflare Workers & Edge
All routing logic, API layers, and terminal delivery run on Workers. V8 isolates, zero cold start, globally distributed. Not a CDN layer — the execution environment itself.
WorkersKV · R2 · D1Edge-native
03 · Data
Machine-Readable Architecture
Entity graphs, semantic schemas, structured data models designed for machines — search engines, AI, routing logic. Meaning encoded at system level, not described in text.
JSON-LDSchema.orgAI-ready
04 · Routing
Protocol-Governed Intake
Every inbound signal follows a defined protocol path. Classification, priority scoring, channel resolution, handoff — immutable, auditable, reproducible at scale.
GuardrailsAudit trailAccess control
05 · Signals
Visibility Engineering
Structured authority signals across local, longtail, and AI search. Engineered for machine comprehension — not keyword density. Intent-matching entity architecture.
Local authorityRich resultsAI search
06 · Automation
Controlled Response Systems
WhatsApp Business API automation triggered by terminal intent events. Operator-defined sequences, escalation logic, handoff thresholds — not broadcast messaging.
WhatsApp APISequencesOpt-in governed
System Architecture

End-to-end.
Every path governed.

From intent selection to operator handoff — every step defined, every output auditable.

system_architecture.svg · UDH Protocol Stack v2.6
Live System
VISITOR LAYER EDGE LAYER PROTOCOL LAYER OPERATOR LAYER TERMINAL iFrame · Intent SELECTION 25+ Protocols CONTEXT Qualification CLOUDFLARE WORKERS · EDGE RUNTIME · V8 ISOLATES 300+ PoPs · 0ms cold start · Sub-50ms TTFB · KV / R2 / D1 CLASSIFY Intent · Score VALIDATE Schema Gate PRIORITIZE Score · SLA ROUTE Channel Select WHATSAPP Immediate CRM WRITE Structured CALLBACK Scheduled HANDOFF Decision-Ready CLOUDFLARE KV / R2 / D1 Session · Config · Audit · Telemetry AUDIT & COMPLIANCE GDPR · IAB TCF 2.2 · Signed ACCESS CONTROL Cloudflare Access · Territory Lock
PROTOCOL FLOW
01
Intent Capture
Terminal surfaces structured selection. Operator-defined categories, no free-text. Ambiguity eliminated at entry.
Worker · iFrame
02
Qualification Gate
Context fields validate against protocol schema. Incomplete signals rejected before operators.
KV validation
03
Protocol Classification
Classified against 25+ defined flows. Priority score assigned. Operator routing rules applied.
Workers router
04
Channel Resolution
Priority + config determines channel: WhatsApp immediate, callback, CRM write, or escalation.
API dispatch
05
Structured Handoff
Formatted for immediate operator action. Context, intent, priority, next-step — decision-ready.
R2 · Audit log
HANDOFF PAYLOAD
handoff_payload.json
{   "protocol": "intake_v2.6",   "intent": "sale_valuation",   "confidence": 0.94,   "priority": "HIGH",   "context": {     "region": "AT_Vienna_3",     "anlass": "owner_transition",     "timeline": "3_months"   },   "routing": {     "channel": "whatsapp_primary",     "sla": "60_minutes"   },   "audit": {     "worker": "udh-prod-eu-1",     "signed": true,     "gdpr": true   },   "status": "DECISION_READY" }
TTFB at edge
≤ 50msCF edge — not origin
Cold start
0msV8 isolate — no container
Protocol flows
25+ · version-controlledImmutable in production
Compliance
GDPR · IAB TCF 2.2Audit trail on every handoff
Engineering Depth

Code that runs
the real estate edge.

Two production Workers. Real implementations. This is what Cloudflare-native engineering looks like at protocol level.

EXPLORER
/ workers
📄intake_router.js
📄kv_session.js
📄csp_iframe.js
📄whatsapp_seq.js
/ schemas
📄intent_schema.json
📄handoff_payload.json
/ config
📄wrangler.toml
📄protocol_v2.6.yaml
intake_router.js
1// Cloudflare Worker · Protocol Intake Router
2// SystemBase v2.6 · EU Edge
3
4import { classifyIntent } from './protocol';
5import { validateSchema } from './schema';
6
7export default {
8  async fetch(req, env, ctx) {
9    const body = await req.json();
10    const valid = validateSchema(body);
11    if (!valid) return gate_reject(body);
12
13    const cfg = await env.KV.get(
14      `op:${body.region}:config`
15    , { type: "json" });
16
17    const intent = classifyIntent(body, cfg);
18    const result = buildHandoff(intent, cfg);
19
20    ctx.waitUntil(audit(env.R2, result));
21    return Response.json(result, {
22      headers: secureHeaders(cfg)
23    });
24  }
25}
csp_iframe.js
1// CSP Enforcement · iFrame Security
2// Operator-signed · Worker-enforced
3
4const POLICY = {
5  "default-src": "'self'",
6  "script-src": "'self' 'nonce-{n}'",
7  "connect-src": "'self' *.udh.workers.dev",
8  "frame-ancestors": OPERATOR_ORIGINS,
9  "upgrade-insecure-requests": ""
10};
11
12export function secureHeaders(cfg) {
13  const nonce = crypto.randomUUID();
14  const origins = cfg.allowed_origins
15    .map(o => `https://${o}`).join(' ');
16  return {
17    "Content-Security-Policy": buildCSP(POLICY, nonce),
18    "X-Frame-Options": "ALLOW-FROM",
19    "X-Content-Type-Options": "nosniff",
20    "Operator-Signature": sign(cfg.key, nonce)
21  };
22}
Deployment History

Active
development.

We ship. Protocol versions are versioned, documented, deployed with rollback. Not a static product — a living system.

v2.6.1Apr 2026CURRENT
D1 integration · Edge-native relational data
Migrated session state from KV to D1 for complex operator queries. Zero latency increase at edge.
D1Workers
v2.6.0Mar 2026
iFrame CSP hardening · Operator-signed builds
CSP nonces signed with operator key. Frame-ancestors enforced at Worker level.
CSP v3iFrame
v2.5.0Jan 2026
WhatsApp API v2 · Sequence engine rebuild
Full sequence engine rewrite. Escalation logic driven by intent classification.
WhatsApp API v2Sequences
v2.4.0Nov 2025
Protocol v2 · 25+ intent flows · Schema validation
Complete protocol library rebuild. All flows schema-validated at edge.
Protocol v2Schema
Technical Specification
Runtime
Cloudflare Workers · V8Zero cold-start · 300+ global PoPs
Response
≤ 50ms TTFB at edgeMeasured at CF edge — not origin
Protocol
v2.6 · 25+ flows · ImmutableAuditable, version-controlled
Storage
KV · R2 · D1 — edge-nativeNo external DB · EU data residency
iFrame
CSP v3 · Sandboxed · SignedHost isolation at Worker level
Compliance
GDPR · LOPDGDD · IAB TCF 2.2DPA · Consent receipts · Audit trail
Access
CF Access · Zero-trust · ApprovalTerritory-exclusive at infra level
Deploy
Private · Parallel · No rebuildStaged rollout · Full rollback
Infrastructure

Cloudflare-native.
Edge-first. Always.

Every component runs at the edge. Workers, KV, R2, D1 — all Cloudflare primitives. No origin dependency, no cold-start penalty.

⚡
Cloudflare Workers
All routing, API layers, and terminal delivery execute as Workers. V8 isolates — not containers. Sub-millisecond execution, globally consistent.
V8 isolate execution — no containers, no delays
300+ global Points of Presence
Custom routing rules per operator deployment
Zero-trust access layer on all endpoints
🖼
iFrame Architecture
Terminals delivered as secured iFrames hosted on Workers. System logic isolated from host environment. CSP, sandboxing, signed builds enforced at infrastructure level.
Sandboxed execution — logic never exposed to host
CSP v3 headers enforced at Worker level
PostMessage protocol for controlled parent comms
Per-deployment signed builds with version locking
🗄
KV · R2 · D1
Session state, operator config, telemetry via Cloudflare's storage primitives. Globally replicated, GDPR-aware, EU data residency configurable.
KV — low-latency session and config reads
R2 — structured telemetry and handoff payloads
D1 — relational data at edge, no external DB
EU data residency configurable per deployment
🔐
Access & Governance
Approval-gated deployments. Operator permissions, territory locks, and protocol guardrails enforced at infrastructure level — not application-layer settings.
Cloudflare Access — zero-trust authentication
Territory-exclusive licensing enforced at edge
Signed deployment artifacts — immutable audit trail
Rollback available at all stages
Engineering Principles

Not a vendor.
The standard.

Principle 01
Protocol over intuition.
Every decision path is defined before deployment. Systems follow protocols — not assumptions. If it isn't specified, it doesn't ship.
Principle 02
Edge-native by default.
We build on Cloudflare Workers because operator systems cannot tolerate latency, origin dependency, or cold starts. The edge is not a deployment strategy — it is the architecture.
Principle 03
Operator-controlled. Always.
System logic is never exposed to end users. Governance, access, routing enforced at infrastructure level — not as configurable settings.
Principle 04
Data minimization by design.
We collect what the protocol requires. Privacy compliance is a system constraint enforced at architecture level — not a legal checkbox.
Principle 05
One market. Deep expertise.
We specialize in European real estate. Protocol libraries, entity schemas, and intent taxonomies built specifically for this domain.
"Information is everywhere. Operator systems make decisions from it — consistently, at scale, without variation. That is the engineering problem we solve."
Christian Kricke · Managing Director · MediaHUB Next Level SL
Cloudflare-native · Workers, KV, R2, D1, Access
IAB TCF 2.2 · GDPR · LOPDGDD compliant
Real Estate specialist · DE, AT, CH, ES, FR, IT
Approval-only · Territory-exclusive deployment
MediaHUB Next Level SL · Palma de Mallorca
Registro Mercantil de Illes Balears · Est. 2023
Access · Selective Deployment

We select
our operators.

UnitedDataHub does not take every project. We work with operators who require systems built to specification — where control, protocol integrity, and operational stability are non-negotiable.

✓You need systems built from specification — not configured from templates
✓Your operation requires protocol integrity and governed access at infrastructure level
✓You are building or operating in the European real estate market
✓You understand that exclusivity is structural — one operator per territory, no exceptions
Direct Engineering Contact
+49 (0) 211-8797487-0 · +34-919 0308 55
Send Enquiry
What you get
Production systems. Built to spec.
Engineered from the ground up on Cloudflare infrastructure. Protocol flows defined. Operator access governed. Territory locked. No shared codebases, no template layers.
What we don't do
We don't do agencies.
No general web design, no marketing sites, no plugin integrations. We engineer operator terminals, routing systems, and edge infrastructure.
The standard
First. Real Estate. Status.
Operators who deploy SystemBase hold exclusive territory rights. The system is not available to competitors in the same region. Infrastructure-level exclusivity — not a claim.
SYS · LIVE MONITOR
statusOPERATIONAL
workers12 active
protov2.6.1
edge_ttfb42ms
cold_start0ms
uptime99.99%
kv_reads--
requests--
regionEU · DE/AT/ES
--:--:-- UTC