On this page
Day 23 - First company client: econsultants on OpenCloud KM0
econsultants onboarding: OpenCloud KM0, transfer of econsultants.es, and a static site rebuilt on our infrastructure.
KM0 is no longer only community and demos: econsultants is our first company client with full OpenCloud KM0 onboarding. It matches what we wrote on day 22: an SME with its own domain, team files, and someone who walks the handover.
Who they are
econsultants is a renewables consultancy focused on wind and rail industry. They have spent decades connecting companies with suppliers and projects. Their day-to-day needs reliable cloud and a stable corporate site, not an opaque panel on another continent.
What we delivered
Three pieces, one operator:
- OpenCloud KM0: file cloud and collaboration on the same EU infrastructure Kilometer 0 already runs (cloud.km0digital.com).
- Domain: we transferred and operate econsultants.es on our perimeter (DNS, HTTPS, hosting).
- Static site: rebuilt and published on our system. Light site, no heavy CMS: services, specialisations, and contact in ES/EN.
It was not “open an account and good luck”. It was onboarding: accounts, domain, production site, and a human counterpart when something breaks.
Why it matters
It proves the SME path end to end: identity and files in Cloud, domain under control, public web in the same house. The same pattern fits other small companies that want out of “Drive + Gmail + loose hosting” without building an IT department.
Data in Germany (Hetzner), serious pricing and support: the product we already offer on pricing, applied to a real client.
Close
If your company needs the same kind of handover (cloud, domain, static web), contact us or come to a meetup. Live site: econsultants.es.
More from the blog
- Day 29 - One KM0 login: Keycloak for Cloud web, desktop, and mobile Cloud in the browser, the OpenCloud desktop client, and the mobile apps now share the same KM0 sign-in. Why we moved, what to do, and links to the new tutorials.
- Day 28 - A cleaner front door for public HTTPS We put a reverse proxy in front of the public edge so TLS and routing sit in one place, with a maintenance path ready, while Cloud URLs stayed the same.