Somewhere between a data hall and a maternity ward, the 3DN network drew first breath. The baby has a name, a passport stamp, and a public address: berlin.germany.politicap.eu is live on a node that is actually in Germany. Trading will follow. Please send flowers, not pager duty.
It is alive — mostly on purpose
For a long stretch the 3DN family looked like a proud parent with excellent blueprints and one very busy continent. PolitiCap, DutchBud, IWISH, and ZZP2ZZP already shared infrastructure, managed hosting habits, and the same stubborn taste for digital sovereignty. What we lacked was the theatrical moment: a second geography that was not a slide deck.
That moment arrived with a European node for PolitiCap. Not a marketing mirror. Not a screenshot of a dashboard. A real regional ECN edge, answering on a real hostname, sitting on European soil while the hub keeps identity, policy, and the long memory of the product.
What “live” means without the opera glasses
Strip the melodrama and the engineering is deliberately ordinary — which, in production infrastructure, is a compliment:
- A public regional name in the
{city}.{country}.politicap.eupattern - Authoritative DNS that can answer from more than one continent
- A compact Go ECN node binary for the market wire and API surface
- Local cache so European visitors are not punished for our intercontinental hobbies
- Accounts, signup, and ledger gravity still on the apex product
In plain language: the wire is regional; the passport office stays central. That split is how multi-region product design stays sane — and how digital sovereignty stays more than a slogan on a slide.
Why Germany, why now
Europe needed a node that was not cosplaying Europe from another timezone. Latency is a product feature whether product managers admit it or not. A Berlin-facing edge gives PolitiCap a place to stand closer to European readers and, soon, European trading flow — without cloning WordPress multisite, identity, or the full hub stack into every rack we like.
Is every transit path a poetry recital? No. Some traceroutes look like a bar fight. The point of regional compute is not that every link is pretty; it is that the people who matter for that market get a short last mile.
Trading soon to follow (yes, really)
A live edge is not yet a full trading floor, and we will not pretend otherwise. The sequence is intentional:
- Name and DNS that tell the truth about geography
- Node binary, cache, and hub handshake in production shape
- TLS that matches the public hostname
- Trading surfaces that follow once the wire is boringly reliable
Boring reliability is the romantic plot twist. Melodrama is for the announcement; monotony is for the market.
What this says about 3DN
3DN’s managed hosting and infrastructure story was never only “we run sites.” It is also shipping production patterns for the 3DN family — work · money · politics as a set of products that can grow by nodes instead of by monoliths. A coding agent can draft the runbook; engineering still has to stand the metal up, watch the cache hit-rate, and refuse to hand every visitor a long-haul penalty.
If you care about digital sovereignty with room for multi-region product design, this is the shape: one package, one policy plane, one cache habit, apex for accounts, edges where the people are.
Come say hello
The baby is noisy, European, and accepting visitors:
- berlin.germany.politicap.eu — Germany edge, live
- bangkok.thailand.politicap.eu — Thailand edge
- politicap.eu — apex product, signup, account
- Plant your ECN — if you want a node of your own
Trading soon to follow. Until then, please enjoy the melodrama. We suffered the traceroute so you do not have to.
Related: PolitiCap · Plant your ECN · 3DN
Leave a Reply