Governed AI workspace · Cloud Ace

AI for the whole company, inside your rules.

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

  1. 1IdentifyWho, from which company, through which door
  2. 2EntitleYour groups may run this
  3. 3ClassifyThe highest label of the data it touches
  4. 4RetrieveOnly the collections you are allowed
  5. 5RedactID numbers and phones masked before leaving
  6. 6BudgetThe department's credits cover it
  7. 7RouteOnly a model allowed for that label
LabelHosted by Cloud Ace
PUBLIKApproved cloud models
INTERNALApproved cloud models
RAHASIARefused, with the reason

The first check that fails stops the request and says why.

Works with the accounts and documents you already use

Microsoft Entra ID Google Workspace SharePoint Google Drive

The problem

The two paths on offer do not fit you.

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.

Cloud platforms

  • Cloud-hosted by design
  • Priced per seat for large enterprises
  • Months to procure

Good governance, built for a different scale.

Genba

  • Access control and audit built in
  • The data's label decides which models may serve it
  • Hosted by Cloud Ace or in your building

Governance you can show an auditor.

Product

Controls that run, not policies on paper.

Company rules become technical checks that run on every request.

PUBLIKINTERNALRAHASIA

The label decides the engine

Every document collection is labelled PUBLIK, INTERNAL or RAHASIA. A request's label only ever goes up, never down.

Seven checks, every request

From any door: the web form, chat or the API. There is no shortcut around the gate.

A refusal with its reason

A refused request names the check that stopped it, the cause, and what you can do next.

One ledger, hash-chained

Every event, refusals included, is recorded and can be verified by an auditor without access to Genba.

Skills written once

One skill definition serves the form, chat and the API with the same rules.

Credits, not tokens

Each department has a monthly allowance. Staff never see tokens.

How it works

From sign-in to the record, in five steps.

  1. 1

    Sign in with company SSO

    Google Workspace or Microsoft Entra ID. No Genba passwords.

  2. 2

    Connect and label

    SharePoint or Google Drive. A collection's label decides where its data may go.

  3. 3

    Ask or run a skill

    In Bahasa Indonesia, from the web workspace.

  4. 4

    Seven checks

    Access, classification, redaction, budget, and routing to an allowed model.

  5. 5

    Recorded in the ledger

    Who, what, which documents, which model, and where it was processed.

Packages

Hosted or in your building, the same skills.

Choose by your data, not by features. Both run the same product and the same rules.

HostedCloud Ace runs itIn your buildingYour servers and GPUs
Who runs itCloud Ace, on Google CloudYour IT, supported by Cloud Ace
Highest data levelINTERNALRAHASIA
Time to startDays to weeksMonths, after an infrastructure check
Fits whenNo data must stay on your own infrastructureInternal policy says some data must not leave

Prices are not published yet. We discuss them in the demo.

Why Cloud Ace

Three facts, no adjectives.

Google Cloud partner

Cloud Ace delivers multi-model access through Vertex AI, including Google, Anthropic and open models.

Delivered inside customer buildings

Kubernetes on a customer's own VMware for a power-generation company, with data kept in Indonesia.

ISO 27001 practice

Our processes follow ISO 27001. Genba itself is not certified yet, and we say so.

Questions

What people ask in the first meeting.

Where is our data stored?

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.

Can Genba read our SharePoint?

Yes. Your administrator connects SharePoint or Google Drive, picks the folders and labels them. Genba reads only the collections each group is allowed.

What about confidential documents?

RAHASIA documents are served only by models in your building. The hosted package refuses RAHASIA data and points you to the in-building package.

How long until we can use it?

Hosted: days to weeks from the contract. In your building: months, because it starts with an infrastructure check.

What can Cloud Ace staff see?

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.

Must our data stay in Indonesia?

Not for most private manufacturers. Location is your choice; accountability is not. Genba makes that choice provable.

See Genba with your data and your rules.

A 45-minute demo with the Cloud Ace team. Pick times that suit you; we confirm within one working day.