Free tools
- No per-person access control
- No audit trail
- Depends on the one engineer who built it
No licence cost, and every risk is yours.
Governed AI workspace · Cloud Ace
Every request passes seven checks, is routed by the label on its data, and is recorded in a ledger you can audit.
In development
The gate every request passes
| Label | Hosted by Cloud Ace | In your building |
|---|---|---|
| PUBLIK | Approved cloud models | Local or cloud |
| INTERNAL | Approved cloud models | Local or cloud |
| RAHASIA | Refused, with the reason | Local models only |
The first check that fails stops the request and says why.
Works with the accounts and documents you already use
The problem
No licence cost, and every risk is yours.
Good governance, built for a different scale.
Governance you can show an auditor.
Product
Company rules become technical checks that run on every request.
Every document collection is labelled PUBLIK, INTERNAL or RAHASIA. A request's label only ever goes up, never down.
From any door: the web form, chat or the API. There is no shortcut around the gate.
A refused request names the check that stopped it, the cause, and what you can do next.
Every event, refusals included, is recorded and can be verified by an auditor without access to Genba.
One skill definition serves the form, chat and the API with the same rules.
Each department has a monthly allowance. Staff never see tokens.
How it works
Google Workspace or Microsoft Entra ID. No Genba passwords.
SharePoint or Google Drive. A collection's label decides where its data may go.
In Bahasa Indonesia, from the web workspace.
Access, classification, redaction, budget, and routing to an allowed model.
Who, what, which documents, which model, and where it was processed.
Packages
Choose by your data, not by features. Both run the same product and the same rules.
| HostedCloud Ace runs it | In your buildingYour servers and GPUs | |
|---|---|---|
| Who runs it | Cloud Ace, on Google Cloud | Your IT, supported by Cloud Ace |
| Highest data level | INTERNAL | RAHASIA |
| Time to start | Days to weeks | Months, after an infrastructure check |
| Fits when | No data must stay on your own infrastructure | Internal policy says some data must not leave |
Prices are not published yet. We discuss them in the demo.
Why Cloud Ace
Cloud Ace delivers multi-model access through Vertex AI, including Google, Anthropic and open models.
Kubernetes on a customer's own VMware for a power-generation company, with data kept in Indonesia.
Our processes follow ISO 27001. Genba itself is not certified yet, and we say so.
Questions
On the hosted package, in Google Cloud's Jakarta region. Every request records where it was processed, and you can see it in the residency report.
Yes. Your administrator connects SharePoint or Google Drive, picks the folders and labels them. Genba reads only the collections each group is allowed.
RAHASIA documents are served only by models in your building. The hosted package refuses RAHASIA data and points you to the in-building package.
Hosted: days to weeks from the contract. In your building: months, because it starts with an infrastructure check.
By default, none of your content. Emergency access needs a reason and a second approver, is time-limited, and is recorded in your own ledger.
Not for most private manufacturers. Location is your choice; accountability is not. Genba makes that choice provable.
A 45-minute demo with the Cloud Ace team. Pick times that suit you; we confirm within one working day.