KRONOS—REPORTING

What "business intelligence" has looked like since 2009

Twelve clicks to change one column. A pivot table wearing a suit.

Keep scrolling

Enterprise business intelligence

Most teams stay because leaving looks expensive. Not because it's good.

The semantic model is years of work. Hundreds of reports depend on it, and every analyst has learned one vocabulary. Kronos was built to that shape deliberately — attributes are attributes, facts are facts — so this is a migration, not a rebuild.

Request early access → See what's built
Click a row to drill Revenue · FY 2026 · live in this page
Visualization types
18Bar to sunburst — the gallery below shows ten of them rendered for real.
Tenant isolation
1:1One database per customer. Not a shared table with a filter on it.
Retraining required
0Same object model, same terminology, same drill behaviour.
Audit re-verified
24hEvery entry hash-linked to the last and re-checked daily. Tampering is detected, not hoped against.
02 / 04

Built as a platform, not a chart library.

The grouping below is the information. A tool that has visualizations but no semantic layer, or a semantic layer with no distribution, is a tool you will outgrow in a year.

Semantic layer

the part that takes years to rebuild

Attributes & hierarchies

Multi-level, with drill paths that behave the way your analysts already expect.

Facts & compound metrics

Level overrides, conditional metrics, and transformations that survive the move.

Custom groups & consolidations

Banding and arbitrary row grouping, evaluated where the data lives.

Prompts

Attribute, element, value and object prompts — including cascading dependencies.

Query & performance

where BI tools quietly give up

ROLAP pushdown

Aggregation runs in your warehouse. We do not pull a million rows to sum them here.

Cubes when you want them

Bind a report to a cube for speed, or leave it live. The grain contract is enforced either way.

Lineage

Ask what depends on an object before you change it, and get a real answer.

Versioning

Every edit recorded, with restore. Retention is a policy you set, not a mystery.

Governance & delivery

the reason procurement says yes

ACLs and row-level security

Object permissions and security filters composed, not bolted together.

Custom security roles

Define privilege sets that match how your organisation actually delegates.

Subscriptions

Scheduled and data-triggered delivery to PDF, XLSX and CSV, with real unsubscribe.

Folders & navigation

An object model people can find things in, with independent folder ACLs.

03 / 04

Four ways in. Pick the one that sounds like your week.

Each goes deeper on one thing. They all end up in the same place.

For MicroStrategy teams

The migration is the reason you're still there.

Not the software. Parity on the objects that matter, so the model comes across and nobody has to relearn what a metric is.

Read the parity case → No BI team

Three weeks for one column

Easy Mode hides the parts you don't need yet, without capping what you can grow into.

See Easy Mode → Analysts

When it ends in a spreadsheet

Eighteen visualization types, conditional formatting, and exports that carry the formatting.

See the library → Serving customers

Your name, not theirs

Database-per-tenant isolation with a single control plane and a real audit trail.

See the control plane →
04 / 04

Bring the report nobody wants to rebuild.

The compound metric with the level override — the one with a security filter on it. We're taking a small number of early-access customers before general availability, and that report is what we would rather spend the session on.

We'll reply personally, not with a drip sequence. No newsletter, and we don't pass your details to anyone.

Got it — thank you.

We'll be in touch from a real address within a couple of days. If it's urgent, aaron@kronosautomation.com reaches us directly.