Great question!
1. We've built the entire product on Clickhouse (highly performant, open source OLAP database) so queries are much faster (10x+, see here [0] )
2. We've had an API[1] from day one. I know Dune has since launched an API, but our API is our core focus. We auto generate API call's right in the app, so it's easy to get started with it.
3. We have built-in "Destinations". For example, you can submit one API call to get the results of a query (which could be 100's of millions of rows) sent to S3 or your own data warehouse automatically. This would take dozens of hours of ETL work to do with Dune's API. In Luabase, it's one API call and all the ETL work will happen automatically behind the scenes.
4. Our datasets are highly curated by expert data engineers, so there's no guessing which view you can trust. Every dataset in Luabase is validated and ready for production.
5. You can import your own data and export to any destination we support without writing code.
6. We've already "decoded" many of the top projects (e.g. ENS, uniswap, etc.) and have modeled views of events. We're working on a way to allow customers to build custom decoding pipelines for smaller projects so that any contract you need decoded is just a few lines of Python away.
0 - https://www.loom.com/share/c817012b86ad494a9cee0f3fa4029733
1 - https://luabase.notion.site/API-b86c02f5fc244041bcd365c02628...