TutorialIntroducing DuckDB and MotherDuck integrations
Reconfiguring data access control for every data app in your stack opens the door to inconsistencies and gaps. Centralize permissions upstream for uniform security.
Redundantly and directly querying your data source results in latency and unnecessary costs. Cube’s caching layer, pre-aggregations, and query queuing fix that.
Cube’s API-first approach and SQL-compliant protocol enable you to maintain every BI tool or data app with consistent metrics definitions, access control, and caching.
Integrate with anything
We legitimately feel blessed to have found Cube. We’ve been using Cube to compute and aggregate data from different sources. With it, we’ve been able to quickly put together a dashboard that we can update whenever we need, without needing to think about the end data language. So, the ease with which we can now create new metrics visualizations whenever we launch a new business feature—plus, the always helpful and welcoming Cube comm
Web Architect at rawpixel
I love the BYOV (bring your own visualization) that Cube enables, as well as its true modeling layer for dynamic modeling—these allow us to make our in-app analytics and reporting offering as precise as we’d like them to be, as well as far more reusable for different customers with varying configurations. Customizing our visualizations without building out the complex querying logic allows us to quickly iterate on our in-app analytics, so we have more time to invest in value-add analytics and product features. And, the Cube team and community are amazing—every question or challenge we had was answered, often conveniently over Slack at what seemed like almost any time of day.
CTO & Co-Founder at Aclaimant
With Cube, we’ve been able to speed up time to release a new data model to production by 5x and decrease analytics downtime by 90%.
Senior Data Engineer at Cloud Academy
Fully managed hosting of your Cube apps