No SDR. Just the engineer who built the chain.
Three doors. Each is a real inbox plus a 30-minute call — technical from the first message, English or German.
Three doors. One person writes back.
Three doors, three real inboxes — all answered by the engineer who built the chain. Engineering for SDK and chain mechanics. Compliance for regulator-mapping and evidence packs. Operations for incidents and existing accounts. No SDR forwards. No template reply.
Engineering
For questions about the SDK, the policy DSL, chain mechanics, or how /api/audit/verify actually works. The engineer who built the chain reads this inbox first — not an intake form, not a triage layer. Replies within one DACH business day.
Compliance
For regulator-mapping questions, evidence-pack format, the Article-13/14/26/73 row data, or whether your BaFin questionnaire lands in our export. The compliance topic gets a separate inbox so it doesn't drown in engineering noise. Replies are dated and signed.
Operations
For incidents on the multi-clock SLA, billing and invoice questions, plan changes, and anything an existing account needs to keep running. Pre-sales technical questions go to engineering. This inbox is for keeping live ones live.
The chain runs in Frankfurt. The engineer writes from Cologne.
Adjudon is one engineer, EU-based. The chain runs SHA-256-anchored in Frankfurt eu-central-1; the engineer writes from Cologne and takes the ICE to Frankfurt for in-person reviews. The Imprint (§ 5 DDG) carries the registered seat. FinanzCamp, re:publica, a Landesbank roundtable — DM the engineering door for a coffee.
Four fields. One inbox. One business day.
If a 30-minute call feels heavy, write here. The same engineer reads it. No qualification questions, no enrichment, no third-party form provider — just the four fields the reply actually needs.