cube.js

📊 Cube — The Semantic Layer for Building Data Applications (by cube-js)

Cube.js Alternatives

Similar projects and alternatives to cube.js

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better cube.js alternative or higher similarity.

cube.js reviews and mentions

Posts with mentions or reviews of cube.js. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-07.
  • MQL – Client and Server to query your DB in natural language
    2 projects | news.ycombinator.com | 7 Apr 2024
    I should have clarified. There's a large number of apps that are:

    1. taking info strictly from SQL (e.g. information_schema, query history)

    2. taking a user input / question

    3. writing SQL to answer that question

    An app like this is what I call "text-to-sql". Totally agree a better system would pull in additional documentation (which is what we're doing), but I'd no longer consider it "text-to-sql". In our case, we're not even directly writing SQL, but rather generating semantic layer queries (i.e. https://cube.dev/).

  • Show HN: Spice.ai – materialize, accelerate, and query SQL data from any source
    5 projects | news.ycombinator.com | 28 Mar 2024
    I'm not too familiar with https://cube.dev/ - but my initial impression is they are focused more on providing APIs backed by SQL. They have a SQL API that emulates the PostgreSQL wire protocol, whereas Spice implements Arrow and Flight SQL natively. Their pre-aggregations are a similar concept to Spice's data accelerators. It also looks like they have their own query language, whereas Spice is native SQL as well.
  • Show HN: Delphi – Build customer-facing AI data apps (that work)
    1 project | news.ycombinator.com | 22 Mar 2024
    Hey HN!

    Over the past year, my co-founder David and I have been building Delphi to let developers create amazing customer-facing AI experiences on top of their data. We're excited to share it with you.

    David and I have spent our careers leading data and engineering teams. After ChatGPT got popular, we saw a rush of "chat with your data" startups launch. Most of these are "text-to-SQL" and use an LLM like GPT-4 to generate SQL queries that run directly against a data warehouse or database.

    However, the general perception now is most of them make for nice demos but are hard to make work in the real world. The reason is data complexity. Even smart LLMs find it difficult to reason about messy databases with hundreds of tables, thousands of columns, and complex schemas that have been built up piece-meal for years. Text-to-SQL can be a fine dev tool for data scientists and analysts, but we've seen many organizations hesitate to deploy it to end users, who never know if the answer they get one day will be the same the next.

    David and I found a better way. From our time in the data engineering world, we were familiar with a type of tool called "semantic layers." Think of them like an ORM for analytics. Basically, they sit between databases (or data warehouses) and data consumers (data viz tools like Tableau or APIs) and map real-world concepts (entities like "customers" and metrics like "sales") to database tables and calculations.

    Semantic layers are often used for "embedded analytics" (e.g. when you're building customer-facing dashboards into your application) but are increasingly also used for traditional business intelligence. Cube (https://cube.dev) is a prominent example, and dbt has also recently released one. They're useful because with a semantic layer, the consumer doesn't have to think about questions like "how do we define revenue?" when running a query. They just get consistent, governed data definitions across their business.

    We realized that semantic layers could be just as useful for LLMs as for humans. After all, LLMs are built on natural language, so a system that deterministically translates natural language concepts into code has obvious power when you're working with LLMs. With a semantic layer, we've found that companies can get AI to answer much more complex questions than without it.

    For a year now, we've been building Delphi to do just that. We've gone through a few iterations/pivots (initially we were focused on building a Slack bot for internal analytics) and are now seeing our developer-first approach resonate. We're being used to power customer-facing fintech applications, recruiting software, and more.

    How do you use Delphi? The first step is connecting your database; then, we build your semantic layer on top of it. Right now we do this manually, but we're moving more and more of it over to AI. Once that's done, we have 3 main ways of using Delphi: 1) white-labeling our AI analytics platform and providing it to your customers; 2) a streaming REST API and SDKs; and 3) React components to easily drop a "chat with your data" experience into your app.

    If this is interesting to you, drop us a line at [email protected] or sign up at our website (https://delphihq.com) to get in touch. Thanks for reading! Would love to hear any thoughts and feedback.

  • Apache Superset
    14 projects | news.ycombinator.com | 26 Feb 2024
    We use https://cube.dev/ as intermediate layer between data warehouse database and Superset (and other "terminal" apps for BI like report generators). You define your schema (metrics, dimensions, joins, calculated metrics etc) in cube and then access them by any tool that can connect to SQL db
  • Need to reduce costs - which service to use?
    1 project | /r/dataengineering | 5 Dec 2023
    also check out cube.dev. they can do the semantic layer and cache it so you are not hitting Snowflake all the time.
  • Anyone with experience moving to Cube.dev + Metabase/Superset from Looker ?
    1 project | /r/BusinessIntelligence | 3 Dec 2023
    We need metrics to live in source control with reviews. Metabase doesn't have a git integration for metrics, which is why we are convinced to use cube.dev as a semantic layer.
  • GigaOm Sonar Report Reviews Semantic Layer and Metric Store Vendors
    1 project | news.ycombinator.com | 8 Sep 2023
    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.
  • Show HN: VulcanSQL – Serve high-concurrency, low-latency API from OLAP
    4 projects | news.ycombinator.com | 5 Jul 2023
    How is this different from something like https://cube.dev/
  • Best Headless Chart Library?
    2 projects | /r/reactjs | 29 May 2023
    Have a look to cube.js
  • Advice / Questions on Modern Data Stack
    1 project | /r/dataengineering | 20 May 2023
    For now, I've been thinking on using self-hosted Rudderstack both for ingestion and reverse ETL, cube.dev as the abstraction later for building webapps and providing catching for the BI layer, and dbt for transformations. But I have doubts with the following elements:
  • A note from our sponsor - WorkOS
    workos.com | 25 Apr 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →

Stats

Basic cube.js repo stats
86
17,135
9.9
about 16 hours ago

cube-js/cube is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.

cube.js is marked as "self-hosted". This means that it can be used as a standalone application on its own.

The primary programming language of cube.js is Rust.


Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com