Dex
Dex is an AI data assistant that connects to your company database and answers plain-English questions by writing and running the SQL for you, returning tables, charts and short explanations, in the browser or inside Slack.
What is Dex?
Dex is an AI data assistant for companies that keep their numbers in a database but do not want to write SQL to read them. The home page is blunt about it: connect your database and ask questions in plain English, like ChatGPT, but for your company's data. The problem it targets is the reporting queue. You file a ticket, someone builds a dashboard, and weeks later you finally get the insight, usually too late. Dex names the three symptoms directly: days of waiting, missed opportunities, and limited access, since only technical profiles can reach the raw data.
The product runs in four steps. You connect a database through credentials that are encrypted end to end, with PostgreSQL, Snowflake, BigQuery and MySQL given as examples, alongside MongoDB, Redshift, Databricks, Supabase, Shopify, Stripe, Slack and CSV in the integrations grid. You then ask a question the way you would ask a colleague: What was our best-performing product last week?, Which marketing channel drives the most revenue?, Why did sales dip in Q2? Dex writes and runs the SQL itself, generating the SELECT, JOIN, WHERE and GROUP BY clauses, and hands back tables and charts with an explanation, exportable as needed.
Two things separate it from a query console. The first is interpretation: the publisher claims Dex reports trends, root causes and anomalies rather than raw rows. The second is where it lives. Connect it to a Slack workspace and mention @Dex in any channel to get answers, visualisations or reports inside the conversation. Role-based permissions and governance settings control which sources and tables each member can reach.
The stated audience is founders, analysts and operators, with no technical skills required, and the home page carries a Trusted by Y Combinator founders badge next to a single anonymous five-star testimonial from an early YC founder. Product documentation covering workspaces, connections, messaging, dashboards and recurring reports is online. Five pricing tiers run from a permanent free plan up to a quoted Enterprise contract. The site is English only, and the publisher is not identified anywhere by a registered company name.
What it does
- Answer plain-English questions asked against a connected company database
- Write and execute the SQL behind each question automatically
- Return results as tables, charts and written explanations, with export
- Surface trends, root causes and anomalies instead of raw rows
- Answer questions inside Slack when mentioned as @Dex in a channel
- Connect relational databases, warehouses and SaaS sources such as Shopify and Stripe
- Build dashboards and recurring reports
When to use Dex / When not to
A quick filter to help you decide if Dex is the right fit.
When to use Dex
- Founders and operators who need a number out of the company database without waiting on an engineer
- Business, marketing and product analysts running ad hoc questions on revenue, channels or feature usage
- Small data teams that have become the reporting bottleneck for everyone else
- Slack-first teams that would rather ask a question in a channel than open a BI tool
- Companies already running PostgreSQL, Snowflake, BigQuery, MySQL, MongoDB, Redshift or Databricks
When not to use Dex
- Developers who need a product API: none is exposed, and the OpenAPI section in the documentation is the sample template shipped with the documentation tool
- Mobile-first users: there is no iOS and no Android application
- Regulated buyers who need terms of service, a named legal entity, a DPA or a GDPR statement before signing anything
- Teams whose database is outside the published connector list, or who need more than the capped connections and monthly credits of the entry tiers
- Non-English-speaking teams: the interface, the documentation and the questions themselves are English only
How to use Dex
A typical end-to-end flow, from setup to results.
- Create an account on the sign-in page with Google or an email address
- Start on the permanent free plan through the Get Started Free button, or book a demo call for an Enterprise setup
- Connect a first data source by entering its credentials, which are encrypted end to end
- Open the network access the connection requires, using the Connect Data Source, troubleshooting and connections FAQ pages of the documentation if it fails
- Ask a first question in plain English, for instance which product performed best last week
- Let Dex write and run the SQL, then read the table, the chart and the explanation it returns
- Export the result, or refine the question to dig into a trend or an anomaly
- Set role-based permissions so each teammate reaches only the sources and tables they should
- Connect Dex to your Slack workspace, then mention @Dex with a question in any channel to get the answer in the conversation
- Add dashboards and recurring reports, and move up a plan when monthly credits or connection slots run out
Pros & Cons
Pros
- No SQL skill required: founders, analysts and operators are the explicitly named audience
- Answers in seconds where a dashboard request would take days or weeks
- A permanent free plan of 500 credits a month with one connection, not a time-limited trial
- An unusually clear data policy: no customer data stored, no training or fine-tuning on company content
- Twelve published connectors covering relational databases, warehouses, NoSQL and SaaS sources such as Shopify and Stripe
- Works inside Slack, so the analysis happens where the team already talks
- AES-256 encryption in transit and at rest, role-based permissions, and public product documentation
Cons
- No terms of service at all: the /terms route does not exist and the footer link is inactive
- No company name beyond a copyright line, no postal address, no country of establishment, no named founder
- No GDPR mention, no DPA, no sub-processor list and no certification such as SOC 2 or ISO 27001
- No hosting country or region declared: the privacy policy says only secure, compliant cloud providers
- No product API despite an OpenAPI section in the documentation that is only the sample template of the documentation tool, and no mobile application
- Signs of an uncleaned starter template: a broken og:image path, a leftover TODO comment, dead About, Careers and Security footer links, and documentation still announced as coming soon on the support page
- Monthly credits and connection slots are capped from the entry tiers, the whole site is JavaScript-rendered so nothing is readable without executing JS, and a single anonymous testimonial supports the product claims
Pricing & Plans
Dex offers a permanent free plan, comprising 500 credits per month and one database connection, rather than a time-limited trial. The lowest paid entry point is the Starter plan at USD 20.00 per month. Professional is priced at USD 50.00 per month and Business at USD 200.00 per month, while Enterprise pricing is available on quotation only. Billing is monthly and denominated in US dollars; no annual rate is displayed.
- USD 0 per month - 500 credits per month
- 1 connection
- USD 20 per month - 2
- 000 credits per month
- up to 3 connections
- USD 50 per month - 5
- 000 credits per month
- up to 5 connections
- priority support (marked Most Popular)
- USD 200 per month - 20
- 000 credits per month
- up to 15 connections
- advanced features and dedicated support
- custom pricing on quotation - unlimited credits and connections
- custom integrations and dedicated account management
Data, GDPR & hosting
A consolidated view of how Dex handles your data.
GDPR overview
There is no GDPR implementation to report. The words GDPR, DPA, sub-processor, SOC and ISO appear nowhere on the site, in the privacy policy or in the JavaScript bundle that carries the whole of the site's content. No Article 27 EU representative is designated, no data protection officer is named, no legal basis for processing is stated, and no right of access, rectification, portability or objection is described. The only user-facing mechanism is operational: disconnect the database or remove the app from Slack, then ask the support team to delete any residual data. The single published address is hello@dexdata.ai, presented as general support rather than a privacy channel. No postal address and no legal entity are published, and the privacy policy carries neither an effective date nor a version number.
Who owns the data?
The privacy policy is the only document that touches ownership, and it is written in the customer's favour. Database credentials are encrypted end to end, actual data and database records are never stored, and only the schema (tables, columns and relationships) is retained, so the model knows how to build a query. Query results are processed live and never reused after delivery. The publisher states it does not sell, share or use customer data for anything beyond running the service. Note what is missing: there is no terms of service, no named legal entity and no licence clause anywhere, so ownership here is described by a privacy notice rather than granted by contract.
Reuse rights
Nothing published grants or restricts reuse of what Dex returns: with no terms of service, no licence text tells the customer what may be done with the answers, tables and charts it exports. The privacy policy at least confirms the publisher claims no further right, stating it neither sells nor shares customer data nor uses it for any purpose beyond delivering the service. On the publisher's side, use is tightly bounded: models generate answers and queries but are never retrained on company data; database content and Slack messages are excluded from training and fine-tuning; each interaction is handled independently inside the workspace session; Slack access is limited to the messages and files needed to answer the question. Encryption is AES-256 in transit and at rest with secure key management, and role-based permissions govern which sources and tables a member can reach. Absent contractual terms, none of this is enforceable as a commitment.
Data retention & training
Hosting summary
Hosting is barely documented. The privacy policy devotes a single sentence to it, saying the infrastructure is hosted on secure, compliant cloud providers with strict access control, and names no provider, no country and no region. There is therefore no declared jurisdiction, no data-residency option and no way to establish whether processing happens inside or outside the EU or the US. What the policy does define is the scope of what is hosted: only the database schema, meaning tables, columns and relationships, sits on the publisher's side. Actual data, database records and query results do not, results being processed in real time and never saved. Encryption is applied in transit and at rest using AES-256 with secure key management. No sub-processor list, no data processing agreement and no certification such as SOC 2 or ISO 27001 is published. The technical stack visible in the site's JavaScript bundle points to Supabase for authentication and related services, but the publisher never presents it as a hosting provider, so it stays a technical observation rather than a published fact.
Things to keep in mind
Risks and trade-offs to weigh before adopting Dex.
- No terms of service exist, so nothing contractual governs the relationship at the date of review, including liability, availability and termination
- The publisher is not identified: no company name beyond a copyright line, no postal address, no country of establishment and no named founder
- No GDPR mention and no DPA: European personal data should not be pushed through the tool before that gap is investigated with the publisher
- No hosting country or region is declared, making data residency impossible to assess, and the database schema is retained on the publisher's side for as long as a connection is live
- Connecting a production database means handing credentials to a third party: check the rights granted to the service account and prefer a read-only, least-privilege user
- Trusting generated SQL without reading it erodes analytical judgement over time. A confident-looking answer can rest on a wrong join or an unstated assumption, and if nobody on the team can check the query, nobody will notice
- The surface can mislead: About, Careers, Security and Terms of Service footer links lead nowhere, the documentation advertises an OpenAPI section that is only a sample template, and the LinkedIn address published on the site points to an admin console
Setup & Integrations
Technical difficulty
Low to moderate. Sign-up is immediate with Google or an email address, nothing is installed, no agent is deployed and no code is written. The one genuinely technical step is the database connection: supplying credentials and opening the network access the service needs, which usually means involving whoever administers the database. Dedicated documentation covers connecting a data source, troubleshooting connections and a connections FAQ. The Slack route adds one step, connecting the workspace, after which questions are asked by mentioning @Dex. The free plan allows one connection, rising to fifteen on Business.
Deployment
Integrations
Supported languages
Behind Dex
Social
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
Do I need to know SQL to use Dex?
Which databases and data sources can Dex connect to?
Is there a free plan, and what does the cheapest paid tier cost?
How does the Slack integration work?
Does Dex store my data or train its models on it?
Can I control who can see which data?
Where is the data hosted?
Is there an API or a mobile app?
Are there terms of service?
Should you pick Dex?
Dex does one thing and says it plainly: connect a database, ask a question in everyday English, and it writes the SQL, runs it and returns a table, a chart and a short explanation, in the browser or in Slack. For a team whose analytics requests currently sit in someone else's queue, that is a narrow and legible promise, and the permanent free plan makes it testable without a purchase order.
The data posture is better than the size of the product would suggest. The privacy policy says the publisher never stores actual data or database records, keeps only the schema, processes query results in real time without reuse, deletes the schema and connection details immediately on disconnection, and excludes customer content from model training and fine-tuning. Encryption is AES-256 in transit and at rest, with role-based permissions on sources and tables.
The counterweight is everything around the product. There are no terms of service at all, the route does not exist and the footer link is dead. There is no company name beyond a copyright line, no postal address, no GDPR mention, no DPA, no sub-processor list, no certification and no declared hosting country. The privacy policy carries neither an effective date nor a version, and is framed mainly around the Slack use case while the commercial site sells a web application. Several footer links lead nowhere and the documentation is still announced as coming soon on the support page.
Read together, this is a young product worth an hour of a curious team's time on the free tier, and a serious due-diligence exercise before it touches a production database in a regulated company. Test it on non-sensitive data first, and ask the publisher in writing for the contractual and hosting commitments the site does not provide.
- Choosing a selection results in a full page refresh.
- Opens in a new window.