Skip to main content

Load the AcmeCloud sample

AcmeCloud is a synthetic B2B SaaS estate — customer operations, revenue, product usage, support, and prepared exports — that you can load into a workspace with one click from the Getting Started page. It is the same dataset the public examples cookbook, metatate-examples, is built on, so once it is loaded the cookbook's notebooks and walkthroughs run live against your own workspace.

Only a workspace admin or owner can load or remove the sample; other members see the card and are prompted to ask an admin.

Starter or full estateDirect link to Starter or full estate

The sample loads in two tiers:

  • Starter — 5 tables and 4 approved policies (acme-customer-use, acme-email-masking, acme-payment-protection, acme-retention): the core allow / deny / mask story, with no collections. This is the default first load and a good first-run tour.
  • Full estate — 9 tables and 15 approved policies covering destination-aware transfer rules, HR and GDPR context, and AI-lifecycle governance, plus a "Customer 360" collection grouping five tables and a set of custom taxonomy types. Eight tables are governed; the ninth, legacy_customer_backup, is deliberately left ungoverned so you can see the honest not_enough_published_state answer (see answer states). The examples notebooks expect the full estate.

If you start with the starter tier, you can expand to the full estate later from the same card.

What loading provisionsDirect link to What loading provisions

  • A sample connector, AcmeCloud sample warehouse — marked as sample data and never syncs; no external system is contacted, and it does not count against your real connectors' syncs.
  • A synthetic catalog under acmecloud_demo.public, with descriptions and taxonomy classifications already curated.
  • The AcmeCloud policies as approved canonical policy versions.
  • A real current deployment publication. The demo runs through the actual deployment pipeline — the plan is created and applied under your own session, then published the same way the deployment worker publishes your changes — so Deployments shows a genuine publication and MCP answers read genuine deployed instruction decisions.

Removing itDirect link to Removing it

The sample is fully reversible: Remove demo deletes everything it loaded — the publication, the demo policies, and the sample connector with its catalog. You can reload it at any time, and reloading starts from a clean slate.

note

Loading the sample never creates an MCP access token. Tokens are shown only once at issue time, so issue your own in the MCP module's Tokens tab afterward, then connect an agent.

Where to go nextDirect link to Where to go next