We are building Quary (<a href="https://quary.dev">https://quary.dev</a>), an engineer-first BI/analytics product. You can find our repo at <a href="https://github.com/quarylabs/quary">https://github.com/quarylabs/quary</a> and our website at <a href="https://www.quary.dev/">https://www.quary.dev/</a>. There’s a demo video here: <a href="https://www.youtube.com/watch?v=o3hO65_lkGU" rel="nofollow">https://www.youtube.com/watch?v=o3hO65_lkGU</a><p>As engineers who have worked on data at startups and Amazon, we were frustrated by self-serve BI tools. They seemed dumbed down and they always required us to abandon our local dev tools we know and love (e.g. copilot, git). For us and for everyone we speak to, they end up being a mess.<p>Based on this, we decided there was a need for engineer-oriented BI and analytics software.<p>Quary solves these pain points by bringing standard software practices (version control, testing, refactoring, ci/cd, open-source, etc.) to the BI and analytics workflow.<p>We integrate with many databases, but we’re showcasing our slick Supabase integration, because it: (1) keeps your data safe by running on your machine without data flowing through our servers; and (2) enables you to quickly build an analytics layer on top of your Supabase Postgres instances. Check out our Supabase guide: <a href="https://www.quary.dev/docs/quickstart-supabase">https://www.quary.dev/docs/quickstart-supabase</a><p>What we’re launching today is open source under the Apache 2.0 license. We plan to keep the developer core open source and add paid features like a web platform to easily share data models (per-seat pricing), and an orchestration engine to materialize your data models.<p>Please try Quary at <a href="https://quary.dev">https://quary.dev</a> and let us know what you think! We're excited to put the power of BI and analytics into the hands of engineers.
Congrats on the launch!<p>I've built analytics products, and the good thing about dashboards is that there's budget for them. People like eye-candy, and are willing to pay for it. I like how you picked Postgres as your initial database, because I think it's still the #1 databases for analyics (even though it's OLTP) that no one talks about.<p>The three products where I think you may want to write short comparison pages are:<p>- Rill
- Preset
- Metabase<p>And I'd take a hard look at ClickHouse as your next database. They're missing a dashboard partner. And I think they're users are much more engineering-centric and therefore a good fit for you than the analytics crowd around Snowflake.
Side comment: what an interesting landing page it has. That Slack CAT button right within the fold is a good idea. A walkthrough and a way to schedule a meeting with the founders. This is very straightforward. Good luck!
Congrats on the launch!<p>I think here's a few players in this space (dev-friendly BI tool) already:
- Holistics.io
- Lightdash
- Hashboard<p>These tools all allow analysts to use both/either a local/cloud IDE to write analytics logic, and check in to Git version control.<p>How do you plan to differentiate with them?
All these comments ask for comparisons. It might be worth creating some alternative pages like podia do [1]. It could be helpful for your growth.<p>Seems like a cool project!<p>[1] <a href="https://www.podia.com/podia-alternatives" rel="nofollow">https://www.podia.com/podia-alternatives</a>
Very cool!<p>Do you anticipate going more towards improving the data modelling capabilities (take on dbt et al) or more towards Business Intelligence (dashboards then hosting then drag&drop query builder all the way until the dreaded pdf export)<p>Something that is overlooked in the dbt direction is how complex data models get.
BI nothing seems overlooked, it is just hard!<p>I like that you have a clear anti-ICP [dbt customers, analysts]. This keeps you clear of the BI/DWH space. I do wonder how you avoid getting stuck in the BI tar pit [], or avoid getting stuck in the dbt middleware zone. Maybe with a core focus on engineers getting further and further without needing a BI/data team!<p>[]<a href="https://twitter.com/generick_ez/status/1782844341674786952" rel="nofollow">https://twitter.com/generick_ez/status/1782844341674786952</a>
We're all on on <a href="https://www.sigmacomputing.com/" rel="nofollow">https://www.sigmacomputing.com/</a> bc we don't like hosting/managing/provisioning essential tools like this + this seems more complicated to configured.<p>I would recommend a simpler setup like Metabase Docker (which I re-evaluated recently): <a href="https://www.metabase.com/docs/latest/installation-and-operation/running-metabase-on-docker" rel="nofollow">https://www.metabase.com/docs/latest/installation-and-operat...</a>
Seems a lit samiliar to redash, writing sql to build dashboards. or using pygwalker + streamlit for more customization. <a href="https://docs.kanaries.net/pygwalker" rel="nofollow">https://docs.kanaries.net/pygwalker</a>
I'll ask another of the "how is this different" questions - how is this different from <a href="https://evidence.dev/">https://evidence.dev/</a> ? Quary seems a little like dbt + Evidence from what I can see.
Tried going through the onboarding sample project from within VS-Code locally… I know, you suggest trying it in the Github Browser, but, hey, I'm perverse and it's available as an option within the extension.<p>It's not at all clear from the documentation or the onboarding notes how to seed a SQLite in-memory database and the CSVs in the `seeds` directory are <i>sometimes</i> referred to in the sample schemas, but sometimes not. So, kinda got stuck.<p>I know if I stuck with it (I got impatient), I'd figure it out myself, but it does seem to be a missing element in the docs.<p>Looks fascinating, though.<p>Kinda like Elixir LiveBook, but focussed on DBs.
Congrats on the launch!<p>I've been evaluating evidence and observable framework for a while, and this seems like a nice addition as alternative<p>But I just realized you require login when using vs code, what is it used for? And can I completely self host this?<p>Thans!
We are looking at moving our Power BI stuff to Apache Superset [1]. How does this compare to Superset?<p>[1] <a href="https://superset.apache.org/" rel="nofollow">https://superset.apache.org/</a>
Looks pretty exciting, congrats. For looking at the intro video and skimming through the documentation, I think I mostly understood what it does and how it works. What I don't understand is the endpoint: can I show the dashboards to an end-user? Does it builds a website, or its usage is limited inside VS Code?
It's unfortunate that org-mode is not more wide-spread (linked to Emacs). Org-mode covers this and a million other use-cases.
Don't get me wrong though, this looks really good. So, congrats to OP :)
Does it support datasource merges like redash do? I had hard time looking for simple solution where I could easily join data from multiple sources and provide simple charts from engineering to support teams.
How is this different from Lightdash? <a href="https://github.com/lightdash/lightdash">https://github.com/lightdash/lightdash</a>
Just out of curiosity, what was the reason for the MIT -> Apache 2 move? <a href="https://github.com/quarylabs/quary/commit/db7a42a58ce66df13f42623bab5966b5c0235f0d">https://github.com/quarylabs/quary/commit/db7a42a58ce66df13f...</a>
See also Eclipse BIRT ... <a href="https://en.wikipedia.org/wiki/BIRT_Project" rel="nofollow">https://en.wikipedia.org/wiki/BIRT_Project</a> . It seems to have languished for a while but it's active once again based on updates to this Stack Overflow posting: <a href="https://stackoverflow.com/questions/53362448/development-status-of-birt-reporting-framework#:~:text=Update%20Jan%202023%3A,BIRT%20works%20with%20Java%2017" rel="nofollow">https://stackoverflow.com/questions/53362448/development-sta...</a>.
Hate to derail the conversation, but is Quary something I could easily whitelabel to embed BI into my product for my customers? (Passively) looking for solutions in that that don’t feel dumbed down.