Query.me v0.1 is live - our very first release.
For the entire team here this is all very exciting as the results of many months of work become fully visible for the first time and we are finally entering the next phase - with real users and stuff.
We are all looking forward to working closely with all of you over the next couple of weeks and months (and maybe even years) as we create the best query experience ever together!
Query.me is a collaborative SQL IDE based on the idea of working together in notebooks
A few core ideas and concepts:
shareabledocuments that can serve many different analytical use cases.
SQL Databasesand then query your data right inside your notebooks, which is great for ad-hoc querying, storytelling, or complex analysis and data transformation.
Search- Query.me creates a searchable index of all notebooks and data assets making it easy to discover what data is available. While pretty basic at this stage, we have big plans to build on top of this in the future.
Usersto your workspace to collaborate on notebooks, share queries and data.
Well, everything. :-)
And as it's the first release, please know that we are still working hard on core functionality and making sure it's a smooth experience from start to finish.
While our list of things we would like to add is veeeery long there are a few catches we think you should know:
1) All users in your workspace are admin users
We have NOT implemented differentiated roles and permissions at this point. Therefore all users inside one workspace are equal and can access all things and do all things. If you want to share a notebook with someone, that someone needs to be invited to your workspace. Roles, permissions and sharing settings are coming soon though.
2) Notebooks are not yet truly multiplayer ready
Multiple users can access a single notebook at the same time. However, you will
a) not see who is currently in a notebook or where,
b) not see changes made by other users until you refresh the page, which can lead to conflicts.
3) Query results cache is not yet configurable
We plan to give everyone the option to configure if and how long query results will be cached and where. At the moment though it's stored (encrypted!) on our end with a 30 day retention.
If you have any questions contact us at email@example.com