Skip to content
Saiku Cloud

Cube library

The Cube library is a gallery of working Mondrian cubes for common analytics domains — SaaS metrics, e-commerce, healthcare reporting, HR analytics. Each template has a description, the measures and dimensions it ships with, and a one-click adopt button that copies the schema into your tenant rebound to your tables.

It’s the fastest path to a working cube when your data shape roughly matches one of the templates. If you have an orders table with customer_id, product_id, total, and a created_at date, the e-commerce template gets you to a queryable cube in about two minutes — significantly less than even the Schema designer.

Adopting a template

  1. Browse the templates. Each card lists what’s in the cube; click Use this on the one that fits.

  2. Pick a connection. The template needs a warehouse to point at.

  3. Map the template’s expected table names to your actual ones. The picker walks you through this — if your tables happen to match the template’s defaults (a fact_* and dim_* pattern, most commonly), the mapping auto-fills.

  4. Click Adopt. We clone the template, rebind it to your tables, and save it as a fresh schema in your tenant. It appears on the Schemas page and is queryable from Analyze immediately.

After adoption the schema is yours — edit it freely on the Schemas page, the template stays untouched.

What’s in the library today

  • SaaS metrics — MRR, churn, ARPU, plan distribution, signups vs. cancellations.
  • E-commerce — orders, revenue, AOV, conversion rate, cart abandonment.
  • Healthcare reporting — patient counts, visit volumes, length of stay, payer mix.
  • HR analytics — headcount, tenure, attrition, comp banding.

More templates ship periodically. If there’s a domain you’d like us to cover, tell us.

When the template doesn’t quite fit

Two options when your warehouse uses different naming or columns than the template assumes:

  • Rename during adoption. The mapping step lets you point the template’s expected fact_sales at your actual analytics.commerce.transactions.
  • Adopt then edit. Take the template as-is and use the Schemas page XML editor to adjust.

If neither path gets you what you need, the Schema designer is your friend — start from scratch with AI assistance instead of forcing the template to fit.

  • Schemas — adopted templates live here.
  • Schema designer — start from a warehouse instead of a template.
  • Connections — the warehouse you’ll point the template at.