Thanks so much for your contribution!
To give you some context on where we’re coming from - we have been
building data connectors professionally since 2019, starting with
Google Data Studio connectors (we have one for Bubble currently
under review). In that world we have hit the large dataset wall
repeatedly - Data Studio caps at roughly 10-30k records due to a
3-minute load limit (data is fetched live from the API without any caching), and there is no clean way around it without sharing your data with a third party that stores it so it can be fetched by Data Studio without making live API calls.
Developing Local Claude extensions change that entirely. Because the
extension runs on your machine, we can do something a hosted connector
never could - sync your Bubble data to a local SQLite database in the
background, and have Claude query that directly for reporting and
analytics. Joins work properly, we can store large data sets, we can store historical data, and nothing leaves your machine.
We are a team of 2 building from Spain, currently developing several
Claude tools alongside this one for our clients and as our own products. Between our products and our
consulting business we have integrated over 50 APIs in the past 7 years (yes we’ve done it before the AI era, although of course we make use of the tools available to us now) so the
architecture of what we are building is solid and informed by real
production experience.
As someone in this recent thread
put it well - deep messy integrations with ongoing maintenance are one of the categories that holds value long term. That is where we want to bring value. And the fact that it is a paid product means we are
genuinely there when support is needed or something breaks - this is
not a side project someone abandons in six months.
The local SQLite sync could be the Agency tier feature we are building
next. Before we scope it properly we would love to understand your
setup better:
- How many data types are you working with and roughly how many rows
in the largest ones? - Is the reporting use case internal or client-facing? Would you require multiple separate databases, one per Bubble app?
- Would you want to use the data retrieved for anything else other than reporting (e.g. syncs to other tools, writing to Google Sheets, industry specific reports like Amazon fulfilment manifest template generation etc)?
- What does your current sync or reporting setup look like?
Happy to take this to a direct conversation if easier - you can book a call with us on our website.