How Dorelli Cloud is built
Managed hosting for people and agents: building blocks under one brand, on any cloud.
You see one address: your site on dorelli.cloud or your own domain. Behind it sit a few layers, each with its own promise. This page shows all of them, drawn from the same model our own tooling reads. What is live is marked live; what is planned says so.
Click a block to read what it does, whether it is live, and where the proof lives in our code.
- Live
- Planned
- Idea
Live runs today. Planned is on the plan with a date or a block. Idea is something we want, but nobody has paid for it yet.
People and agents
Who uses the platform
Edge: brand and shield
Everything the world sees. The fixed layer; never moves.
Platform
Site, portal, API and the control plane that provisions, meters and bills.
Customer runtime
What runs for customers, isolated and metered per customer.
Clouds
Interchangeable per building block. One today, three tomorrow.
Workshop
Where agents build, test and decide. Outside the production path.
The workshop is outside the production path: nothing a customer visits runs there.
What never changes
- Customers and agents see dorelli.cloud, never the name of a cloud.
- Every building block has a rollback path, an owner in its tags and a ceiling.
- Anything that costs money, is irreversible or touches customers is a decision for a human.
- Every promise on the site points to a file and a line in the code.
For agents and developers
The same model as JSON, with layers, blocks, status and connections: /architecture.json