Since then a lot has improved: More databases are supported, most of the product can now be used for free, and most importantly:
The app now comes with an analytics workspace powered by an embedded ClickHouse instance, running locally on your machine. This allows you to query local files, files on S3, PostgreSQL, SQLite & more - and all of those at once.
If you mean the common OpenAI API key, I'm not sure how that's different in regards to feeling secure compared to separate keys. Would you mind elaborating further, please?
To clarify, the common API key is known only by my server, not by the app!
Right now it's pretty simple: First I drop the table/column information if the token limit gets exceeded otherwise (this is shown as a warning in the UI). Then if the limit still gets exceeded, the I show an error to the user.
I plan to make this process more smart eventually.
I first announced DB Pilot on HN back in April: https://news.ycombinator.com/item?id=35761979.
Since then a lot has improved: More databases are supported, most of the product can now be used for free, and most importantly:
The app now comes with an analytics workspace powered by an embedded ClickHouse instance, running locally on your machine. This allows you to query local files, files on S3, PostgreSQL, SQLite & more - and all of those at once.
Embedding ClickHouse was possible thanks to chDB (https://github.com/chdb-io/chdb). A recent discussion on HN about it: https://news.ycombinator.com/item?id=37985005