cube

You might know Cube as an open-source semantic layer (https://github.com/cube-js/cube). Started in 2018, now 19K+ stars, 1000+ releases. We kept hitting the same wall: everyone wants AI analytics, but AI without business context hallucinates. The fix is a semantic layer — a model that defines what "revenue" or "churn" actually means. But building one by hand takes weeks. So we built an AI agent that writes the semantic layer itself, then uses it to answer questions and build dashboards with no hallucinations. Connect your data → agent builds the model in seconds → ask questions in natural language → get accurate results grounded in your business definitions. Three months in GA. Running in 200+ companies. 500K+ lines of semantic layer code generated. Teams like Brex and Drata using it in production. OSS core isn't going anywhere. Agentic a

Not a SQL replacement, but if you're looking for an open source semantic layer, Cube is the way to go [0] 0 - https://github.com/cube-js/cube

https://github.com/cube-js/cube comes out very well at the end as a promising open source system, getting rather close to the bullseye. Would love to know more & hear people's experience with it. With exception, nice interesting stream but not a ton of interaction on https://news.ycombinator.com/from?site=cube.dev

This is the advancement of egg[0]. Egg (and the e-graph theory behind it) has recently been put into use in some databases (e.g. cube[1]) and compilers (e.g. cranelift[2]). It lends itself well to the use-case of optimizing query planers and compilers, as it at the core avoids the optimization pass ordering problem (where an earlier optimization pass may destroy information that could be useful for a later one). [0]: https://github.com/egraphs-good/egg [1]: https://github.com/cube-js/cube [2]: https://github.com/bytecodealliance/rfcs/blob/main/accepted/...

Long time ago, it was possible to built Cube into a Node.js app. However, the team decided to deprecate it: https://github.com/cube-js/cube.js/blob/master/DEPRECATION.m... The motivation is diverse but one of the reasons is that a Cube app should be scaled differently from a client-facing app. Noone probably wants their app to hang when Cube serves a ton of requests or refreshes cached data (and vice versa). That’s why it’s recommended to run Cube as microservices. I hope it’s not a big deal since a lot of cloud platforms provide container environments. Also, just recently, we’ve launched Cube Cloud which provides serverless experience for Cube apps and has a free tier: https://cube.dev/cloud/

It actually works exactly as you describe. We generate SQL query to return aggregates based on SQL supplied in Cube.js schema. We never fetch raw data from SQL backend. Architecture overview can probably help to understand: https://github.com/statsbotco/cubejs-client#architecture

Hi everyone! I want to share with you a serverless analytics framework - Cube.js: https://github.com/statsbotco/cubejs-client. I’m one of the authors and would love to hear your thoughts and feedback. Cube.js is an analytics layer for applications. It supplies building blocks to add analytics features into your application. It comes with caching, pre-aggregations and all other stuff you need to handle large data sets. We’re launching public beta today, with open-sourced React client and cloud hosted server. We’re planning to open source server as well, so it could be self-hosted as a container or on AWS Lambda/Firebase Cloud Functions. It is visualization agnostic, meaning you can use any visualization library you want. Looking forward to hearing your feedback! :)