Built to be left.
The honest test of infrastructure isn't how it locks you in — it's how it lets you go. do.place is designed so that using it never becomes a trap: declarations instead of buried code, your data in open formats, exit as a designed path rather than a negotiation. That's not generosity. It's what makes a platform buyable.
europe-first, and precise about it
DoPlace GmbH is a Swiss company. Switzerland is not in the EU, and we are not going to blur that line to sound better. What europe-first means here: the contract sits in a European jurisdiction, the people operating the platform are in Europe, and the infrastructure is European — Hetzner today. Where a customer's data has to stay inside the EU, we deploy to EU-resident hosting. Nothing in the platform depends on a non-European hyperscaler, and that is the default rather than an option you have to ask for.
security and reliability, plainly
Isolation between tenants, encrypted transport and storage, least-privilege access, audit logging in the platform's own administration. No certification theatre: we don't hold ISO or SOC marks today and won't imply otherwise. What we will do is answer a security questionnaire with specifics, quickly.
put your security team in touchproperties, not promises
declaration-driven.
Services are structured declarations interpreted by the platform. What a service is stays legible — to you, to your auditors, to whoever comes after us.
multi-tenant with hard edges.
Tenants are first-class: their own users, their own data boundaries, their own contract anchored in the entity registry.
one identity.
Single sign-on across every tile on the board; industry-standard protocols; roles and visibility follow the declaration.
contract-anchored registry.
Every participant, every licence, one registry. The legal structure and the running system agree with each other.
reproducible deployments.
A release is a versioned artefact, published whole and switched to. Rolling back switches back — there is no half-deployed state to clean up afterwards.
hosted where you want it.
Managed by us, in your own cloud account, or on your own hardware. One product, one set of declarations — no separate on-premises edition running two releases behind.
operated from Switzerland.
Swiss company, data protection under the revised FADP and GDPR.
cookieless by construction.
Analytics is self-hosted and cookieless: no personal data stored, no consent banner needed — measured without being watched.
one platform, three stages
Idea, pilot, production — no re-platforming step in between.
the prototype is the system, declared smaller.
Most ventures pay for growth twice: once to build something that demonstrates the idea, once to rebuild it as something that can carry customers. Here it is the same platform reading the same declaration at three different sizes.
- idea — declare the service, put it on a board, show it to someone. Shared infrastructure, no procurement, no build
- pilot — real tenants, real licences in the entity registry, real ordering. The same declaration, with more of it filled in
- production — grow into isolation: your own tenancy, your own data boundary, your own hosting if you want it. The declaration you wrote on day one is still the thing running
None of those steps is a migration. Nothing gets rewritten because the venture got serious.
where it runs is your decision
Cloud or on-premises — the platform does not have a preference.
same declarations, same artefacts.
A deployment target is a deployment target. Changing it is an operational decision, not a product decision, and it does not fork the thing you bought.
- managed — we run it and carry the operations; you get the board
- your own cloud account — your provider, your billing relationship, your controls; we deploy into it
- on-premises — your datacentre, your network, your rules about what may leave the building
- and back again — moving between them is a deployment, not a rewrite
This is the same argument as the one below it. A platform you can host yourself is a platform you can leave — and a platform you can leave is one you can safely commit to.
portability & exit
First-class features, not fine print.
your venture outlives any vendor.
A platform run by a small company is only buyable if leaving it is easy. We build accordingly.
- open exports — your data leaves in open, documented formats, continuously, not just at the end
- legible declarations — what you configured is a readable structure, not vendor bytecode; it leaves with you
- a documented exit path — designed into the platform and the engagement
the deep-dive happens in conversation.
architecture walkthroughs for serious evaluations — under NDA, with the person who built it.