spiculedata/saiku: README-based editorial guide
A guide grounded in the README, repository metadata, and license for installing and checking spiculedata/saiku.
Project scope
spiculedata/saiku describes itself in the README as "Open-source semantic layer: one cube for Excel (MDX/XMLA), dashboards, and AI agents (MCP). Mondrian + Apache Calcite.". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "README", the README says: Open-source Semantic Layer analytics for cubes , drag-and-drop in the browser, SQL through Mondrian + Calcite, and a typed REST surface so AI agents can query without ever seeing MDX.. That establishes the project's stated boundary, not a production test.
Suitable use cases
The README's "What is Saiku" section gives a useful starting point for deciding whether the project fits: Apache Arrow wire format for cellsets, so the browser and any. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Mondrian 4.8.1.x (Spicule fork) , with a Calcite-based SQL planner. It can shape a first test, but it does not replace testing in the intended environment.
How it works
The operating model is spread across sections such as "Try it in 30 seconds". The source evidence includes: > For a real deployment, drop SAIKUDEMO=true and set an admin password: > -e SAIKUADMINPASSWORD='a-strong-password'. Saiku refuses to start on the > default admin/admin once it's network-reachable, so one of those two is > required.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.
Installation and first run
Start installation from the README's documented entry point. A command that can be checked in the source is: docker run -d -p 8080:8080 --name saiku -e SAIKU_DEMO=true ghcr.io/spiculedata/saiku When the README contains no runnable command, this article does not invent one. Open its "What is Saiku" section and confirm system dependencies, default ports, and first-run initialization before using a public server.