22 karma · joined April 21, 2020
As much as the performance and lightweight aspects of Tauri are great we also have to weight the consistency of user experience which Electron gives having Chromium built into it. All that said... it's worth us taking a second look to see if Tauri will work for us in this use case!
Learn more about that here: https://github.com/Brayden/starbasedb/issues/12
Is it auto-accessible REST endpoints? Easy to implement websocket support for the database? Data replication for scaling reads? Offline data syncing? A lot of potential wins for a layer like this to build on.
In terms of serving Outerbase on-prem, it's an enterprise offering we do support.
Some of our features that really help us stand out from this particular pack are the fact you can use EZQL in Outerbase to ask natural language questions on your database without knowing how to query (we'll even expose the SQL if you're interested in what was produced, great for learning SQL). Very helpful for larger databases. In addition to that you can take these queries and create data visualization right in our tool.
For the SQL stuff being displayed, we like that it gives non-technical users an opportunity to learn SQL along the way. Now providing it as an optional UI is a worthy consideration for us to perhaps make.
We do have a self-hosted version on our enterprise offering currently but I understand it might not be the most desirable for non-enterprise customers.
We do have a Slack integration that isn't launched YET but is in internal testing to be released soon. Glad to hear this feedback and know we're on the right track with thoughts here!
Today's large tools require in-depth specialized knowledge on the data as well as how to apply it to create dashboards. Our mission is to create data tools that non-developers can understand, use, and create impact with on day 1.
One feature we're really excited about is how to hold a conversation with your database to fine tune the chart you want in natural language, and have "verified" sources come in to double check what has been produced meets the expectations of the business. Certainly a lot more things on the way as well.
To be entirely candid and honest, returning a lot of rows presents problems on our end as well at the moment. It's something we are actively working on improving for large data sets to create the best user experience without having to concern yourself about what you're returning.
For our EZQL (natural language to SQL) you don't necessarily need to have foreign keys to infer relationships between tables. We try to infer those relationships for you.
For internal databases we do offer VPN and on-prem (Dockerized) solutions for our enterprise customers.
Private databases that are on localhost we don't _currently_ support on our native Mac app but it's on our roadmap!
We are working on a resolution to this issue right now. This is an issue with our logout function on the frontend not removing the auth token. There is no risk of scope access outside of your machine.
We will push out a fix shortly.
EDIT: Fix has been deployed. Thanks again!