We had a comment in our codebase that said SQL Server doesn't handle pagination well, so we should just avoid pagination for now. And it did exactly that: shipped the entire result set to the browser and let it sort itself out. Same deal for Spanner.
A lot of Basedash is just "run the SQL the user wrote, show the rows." We support 10+ dialects (Postgres, MySQL, BigQuery, Snowflake, Athena, SQL Server, Spanner, and friends), and every query gets paginated because we can't stream a 12M row result set to a browser.
Basedash: AI data analyst
Congrats on the launch. The audience-specific AI context part is interesting.
Most access control tools make me think about who can see which data, but changing how the assistant responds depending on the team seems like the part that could matter a lot once more departments are using the same BI tool.
Do teams usually need that separation from the start, or does it become more important as usage spreads across the company?
Basedash: AI data analyst
Thanks @kevin_napier! Usually depends on the size of company. Once customers start onboarding multiple teams, they can benefit from group-level AI context. Especially when users have varying levels of technical experience.
Nice launch. The group-level AI context is the part I’d pressure test.
Access says what data someone can see, but the assistant also needs to know what it is allowed to do with that context. Do automations inherit the same group boundary, including MCP server and tool access?
Basedash: AI data analyst