What we publish
Product behaviour: S3 as source of truth, roles, health as freshness, plans, and how to request a workspace. That is enough for a buyer to understand the work.
How we work
Client estates are private. The method is public.
We do not list customers, databases, dump sizes, or health on this website. What we will describe is how a workspace is isolated, what we store, and who is allowed to see an inventory — after we have issued access.
What we keep private
Anything that identifies a live estate: company names, database names, object keys, regions in use, backup counts, and whether last night’s dump arrived.
One workspace at a time
Operators do not get a global dump pile. Each client has its own storage target, people, and audit trail. Cross-listing objects across clients is not how the console is used.
Access is issued, not linked from here
The public site has no sign-in on purpose. Console accounts are created after onboarding, with the minimum role needed to view, download, or audit.
Onboarding without a public catalogue
- Request a plan Company count, Odoo versions, regions — not a list of production database names on a form we will publish.
- Connect storage In the private console: bucket or prefix, IAM or encrypted keys.
- Discover in private Sync builds the inventory where only your roles can see it.
- Operate Health, history, and recovery stay behind those roles.