cube
The official Cube image — the open-source semantic layer that defines metrics once and serves them to BI tools, applications, and AI agents through SQL, REST, and GraphQL APIs.
What is Cube?
The Cube image packages Cube, an open-source semantic layer that sits between your data warehouse and your consumers. Teams define data models — measures, dimensions, joins, and access rules — as code, and Cube serves consistent metrics through SQL, REST, and GraphQL APIs to BI tools, embedded analytics, and AI agents, with a pre-aggregation engine and caching for fast queries. A deployment typically runs the Cube API server, refresh workers, and Cube Store, configured through environment variables and a model folder. It is used by data and analytics engineering teams that want a governed, single source of truth for metrics.
What is Echo's Cube image?
Echo's Cube image is a hardened build of Cube on Echo's hardened base. Echo images are designed to be a drop-in replacement: swap the image reference in your Dockerfile or deployment manifest and CVEs go to zero without disrupting your data models, pre-aggregations, database credentials, and API security settings. Every image is tested across clouds, image use cases, and deployment targets. Echo ships every image in two variants:
- Distroless variant — optimized for runtime use, with the smallest possible attack surface
- Default variant — includes essential build tools, package managers, and shells for teams that need operational access
For production Cube deployments, the distroless variant keeps all runtime operations — query planning, SQL generation, caching, pre-aggregation refresh, and API serving — fully intact while minimizing exposure; the default variant suits data and analytics engineering teams that need shell access for inspecting generated SQL, running the CLI, or debugging data models.
What is the difference between Echo's Cube image and the public Cube image?
Public Cube images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a semantic layer API server used in production. Cube images run continuously with access to data warehouse credentials, metrics definitions, and API secrets. OS-level CVEs in the base image — particularly in libraries such as openssl, zlib, and libc, along with the Node.js runtime dependencies — create exploitable paths that bypass application-layer controls entirely, allowing attackers to move from a network-reachable service to host-level access. For teams running Cube across many environments, the image is also a steady source of scanner noise in the CI pipeline — every package in the base becomes a finding your security team must triage, even when none of it is reachable from the service. Echo's build retains everything Cube needs for query planning, SQL generation, caching, pre-aggregation refresh, and API serving while removing the packages that don't belong in a production Cube semantic layer API server. As we covered in our post on how to protect your company from software supply chain attacks, long-running services that hold sensitive data and listen on the network are among the widest attack surfaces in the container stack. Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Echo images are recognized by all major scanners and mirrored to all major registries, so they fit into existing pipelines without changing your registry, scanner, or runtime tooling.
FAQ
Can I replace my Cube image with Echo's Cube image?
Yes. Echo's Cube image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. data model files, warehouse driver settings, pre-aggregations, JWT-based API security, and BI tool connections all continue to work without changes to your models or dashboards.
Is Echo's Cube image FIPS-validated?
Yes. Echo's FIPS-validated images use cryptographic modules with an active FIPS 140-3 CMVP certificate, making them fit for federal use — unlike FIPS-compliant images that haven't been validated. This matters for teams running Cube workloads inside FedRAMP boundaries, where a semantic layer API server that holds warehouse credentials and serves governed data to many downstream consumers must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Cube image.
What is Echo's vulnerability management SLA on the Cube image?
Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Patches are mirrored automatically into your private registry so you're always running a clean version — critical for a long-running service that holds data warehouse credentials, metrics definitions, and API secrets and is reachable over the network.
Is Echo's Cube image distroless?
Echo ships every image in two variants: a distroless variant optimized for runtime use, and a default variant that includes essential build tools, package managers, and shells. For production Cube deployments, the distroless variant is the leaner, more secure choice; for data and analytics engineering teams that need shell access for inspecting generated SQL, running the CLI, or debugging data models, the default variant is the right fit.
How does Echo achieve such a drastic CVE reduction in Cube?
Echo's Cube image is built from source with only the absolute essentials needed to run the Cube semantic layer API server, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Cube version your applications and their dependencies are certified against — avoiding a disruptive upgrade forced purely by OS-level vulnerabilities in the base image rather than by your own requirements.
Will Echo's Cube image help us achieve FedRAMP?
Yes. The hard parts of FedRAMP — managing vulnerabilities, applying fixes, and using FIPS-validated cryptography — are baked into Echo images, including STIG-hardened configuration and ConMon/POA&M-ready reporting. For data and analytics engineering teams running Cube under an ATO — whether that's governed program metrics, embedded analytics, or a metrics API for AI agents — Echo's hardened Cube image keeps the semantic layer API server layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.
.avif)