ThreadQL: just query your data in a slack thread
I'm excited to share that ThreadQL v0.1.0 is now open-source and available at https://threadql.com. This AI-powered application pioneers the era where asking questions is the new query language.
The problem I've always had
Work in a tech company long enough and you realize: the database is where the truth lives. Every order, every user, every metric — it's all in there. But getting answers out of it? That's a different story.
If you're technical you write SQL queries. If you're not, you message the dev or data team and wait. And wait. And wait.
I've come to understand this dependency from both positions. On the product side, experiencing frustrated product owners wanting instant answers but being blocked if we can’t respond in time. And on the dev side I’ve had my plethora of flow-breaking "can you just run this quick query?" requests. And I kept thinking:
Why can't I just ask my database a question like I'd ask a person?
And why can't it live where I already work — in Slack?
That's what ThreadQL does.
ThreadQL Lives in Slack
ThreadQL isn't another app you have to switch to. It's right in your Slack.
You ask a question in plain English, and ThreadQL responds with your data. No SQL. No context switching. No waiting.
"How many users signed up this month?"
"What's our top product by revenue?"
"Show me the orders that haven't shipped yet."
Ask. Get answers. Done.
Need the Raw Data?
Need further analysis? Just ask ThreadQL to export a CSV and it'll send it straight in the slack thread. Download, open in Excel and work from there. Your data, delivered where you already are.
Why I’m Open Sourcing It
This isn't a product I’m selling. It's a tool I believe belongs to the community.
Organizations deserve to unlock the data they already have. Every person in your company - product, marketing, support, operations - should be able to ask questions and get answers. The knowledge is sitting there in your database. ThreadQL just helps you talk to it.
Under the Hood
For Security:
Only parameterized SELECT queries allowed, SSH Bastion Host support, privacy by design, optional approval-first workflows
For Reliability:
Multi-Tenant Support, LLM Provider Fallback, MySQL & PostgreSQL support, Auto table scanning schedule
For Deployment:
Helm Chart, or docker-compose stack and an admin panel
The Vision
Here's what I think the future of data access looks like:
You have a question. You ask it in Slack. You get an answer. That's it.
The database holds your organization's living knowledge. ThreadQL unlocks it — right where your team already works.
Check it out: https://github.com/emtay-com/threadql
P.S. This is a 0.1.0 release - early but functional. I've tested it as thoroughly as I could, but might have missed cases. If you run into issues or have ideas for improvements, your contributions and feedback are more than welcome. And if this clicks, star it on GitHub to help others discover it
Top comments (0)