Fully Managed Metabase
as a Service

Relevant standard: Card data is handled upstream by the payment processor; the merchant's responsibility under PCI's SAQ-A framework is to keep payment scope out of internal BI. Metabase queries a Shopify-synced replica that excludes raw card data.

DANIAN configuration: Region pinned to the customer's primary market; sync windows offset from order-volume peaks; Postgres app DB on day one so daily revenue dashboards survive container restarts.

Workflow example: Daily 09:00 Slack pulse to the founder with yesterday's revenue, AOV, 30-day cohort retention, and Meta-ad ROAS. Weekly Monday dashboard for inventory days-of-cover.

Quantifiable detail: A 12-person DTC brand typically lands around 40 saved questions, 6 dashboards, and a 4–8 GB app database — well inside the €9/month plan.

Relevant standard: Product-event data is treated as personal data in most jurisdictions when joined to user IDs; access controls and export limits sit with your data team. Metabase's Pro tier adds row- and column-level data sandboxes if you need them, on your own Pro token.

DANIAN configuration: Connection routed to a Postgres read replica or warehouse over a private tunnel; MB_DB_CONNECTION_TIMEOUT_MS set generously for slow cold queries; JVM heap stepped up for wide cohort SQL.

Workflow example: A stalled-trial alert posts to #growth in Slack each morning. Weekly cohort retention dashboard for the leadership review; funnel and activation dashboards for the product team.

Quantifiable detail: A 30-person Series A team typically runs ~15 dashboards, ~120 questions, and ~6 scheduled alerts; heap pressure shows up first on cohort SQL over 24-month windows.

Relevant standard: Client data residency is contractual; some clients require EU-stored analytics metadata. You choose the region per Metabase instance and document the choice in your DPA.

DANIAN configuration: One Metabase instance per major client; MB_EMBEDDING_SECRET_KEY provisioned automatically; SSH tunnels to each client's warehouse so credentials never touch the agency laptop. Pro-tier features (no Metabase badge, interactive embeds) available when you supply a Pro token.

Workflow example: Each client portal embeds 4–10 signed dashboards covering acquisition, conversion, and retention metrics, refreshed nightly. Client logins are gated by the agency's own SSO in front of the portal, not by Metabase.

Quantifiable detail: An 8-person agency commonly runs 6–12 instances; each averages 8 embedded dashboards and ~30 saved questions. Per-instance billing means cost scales with client count, not user count.

Relevant standard: Risk and portfolio reporting is shaped by jurisdictional frameworks (Basel-aligned credit reporting, MAS, FCA returns). Source-of-truth obligations stay with the data and legal owners; Metabase is the read layer.

DANIAN configuration: App DB region pinned to match the reporting jurisdiction; Java and Metabase image versions pinned per release so a silent upgrade does not change a regulatory dashboard's numbers; daily off-site backups of both the app DB and serialization exports.

Workflow example: Daily delinquency-bucket dashboard for the credit team, weekly portfolio-mix view for the board pack, ad-hoc SQL for investor data-room questions, alerts on early-warning indicators.

Quantifiable detail: A small lending operation typically runs ~80 saved questions across credit, ops, and finance, with the heaviest dashboard pulling ~200k rows per refresh — comfortably handled by the standard plan.