About
Infrastructure you don't have to think about.
xdew.cloud started from a simple idea: your team should spend time on your product, not on keeping servers alive. We built a cloud platform and we run it ourselves, so you don't have to.
Behind the scenes
Why identity is its own service
For a while, one internal service owned everything — projects, workspaces, and every user and role alongside them. It worked, until every new permission check turned into another exception bolted onto logic that already did too much.
So identity moved out. Users and roles now belong to their own service, which is the only thing that decides who can do what. Everything else just asks it a question and gets back a clear yes or no.
That's the shape of the whole platform now: a new capability gets its own small, focused piece — not another branch in something that already does too much.
- beforeOne service watched projects, workspaces, users and roles, and authorized itself from a local permission check.
- afterThe identity service owns users and roles exclusively, and every other service authorizes through it instead of guessing.
- resultTwo small, focused services you can reason about in one sitting, instead of one you have to hold in your head all at once.
Principles
What we won't compromise on.
Every resource has one clear owner
A project, a workspace, a bucket — each is a single well-defined object internally, not scattered state across three systems.
One service, one concern
Identity was split into its own internal service specifically so access checks ask one clear question instead of guessing.
We carry the pager, not you
Uptime, patching and backups are on us. Your team gets a dashboard and a point of contact, not a rotation.
Status is not optional
Every resource reports its own status. If you can't see whether something finished, it doesn't count as done — you'll always see it in the console.
Curious how it holds together?
Tell us what you're building and we'll walk you through exactly how it runs on xdew.cloud.