简体中文
EnglishAskYourDatabase Plans and Usage Allowances: How to Choose
Updated
AskYourDatabase does not publish plan names, prices, or numeric usage limits on the pages available here. What the site does make clear is the decision structure: Desktop and Website Chatbot are separate products, each with its own plan considerations, and private deployment is handled as an enterprise discussion rather than a self-serve tier. To choose, start from who needs the answers and where they will ask questions, then review plans and usage allowances on the pricing page for current figures.
The three paths, and who each one fits
The site frames the choice around "the people who need answers and where they will ask questions."
| Path | Built for | What you get | What to plan for |
|---|---|---|---|
| Desktop | Analysts, operations teams, and business users working in the Windows or macOS app | Connect from your computer, ask a question, inspect the SQL and results, then ask a follow-up or request a chart | Your computer needs database access; questions and necessary response data can reach a model provider through the AI gateway |
| Website Chatbot | Product teams adding database questions to a website or customer portal | Configure a chatbot, connect it to approved data, integrate the chat interface into your application | Plan authentication and user-level data access before rollout, and test that each user retrieves only the records they are allowed to see |
| Private deployment | Organizations with hosting or data-handling requirements | Application hosting, model endpoint, network access, and operational responsibilities agreed with the enterprise team | Self-hosting the application can still involve external model API calls; a locally hosted model is a separate deployment scope |
Two details in that table are easy to misread. First, "local connections" in Desktop do not mean offline AI — the site states that questions and necessary response data can reach a model provider through the AI gateway. Second, hosting the application yourself does not automatically remove external model calls; only a locally hosted model changes that, and it is scoped separately.
What "usage allowance" actually controls
The pricing page is the only place with current plan and allowance figures, and the site directs you there to "review plans and usage allowances." Because no numbers are published on the pages available here, treat the allowance question as something to verify directly rather than assume.
What you can reason about before you look:
- Desktop allowances govern how much analysis one person or a small team can run from a connected machine. Since each user connects from their own computer with database access, the number of seats and the query volume both matter.
- Website Chatbot allowances govern usage by your end users, not your team. A chatbot embedded in a customer portal can generate far more questions than an internal analyst would, so the allowance that fits Desktop may be the wrong shape for an embedded deployment.
- Private deployment is not a usage tier at all — it is a scoping conversation covering hosting, model endpoint, network access, and operational responsibilities.
If your main constraint is cost per question rather than features, the site also offers a direct comparison between AskYourDatabase and BlazeSQL, which is worth reading alongside the pricing page.
How to decide in practice
- Name the asker. Internal analyst or operations user → Desktop. Your product's end user → Website Chatbot. Neither, because you have hosting or data-handling constraints → enterprise discussion.
- Check the allowance against realistic volume. For Desktop, estimate questions per person per day. For an embedded chatbot, estimate questions per end user per month, then multiply.
- Confirm the data boundary before you commit. For Desktop, confirm which machine holds database access and that the AI gateway path is acceptable. For the chatbot, confirm authentication and per-user data access, then test that each user can retrieve only the records they are allowed to see.
- Compare plans on the pricing page, and compare products if cost is the deciding factor. The AskYourDatabase vs. BlazeSQL comparison covers the product-level trade-off.
Getting accurate answers once you have picked a plan
Plan choice and answer quality are separate problems, and the site treats the second one as a setup discipline rather than a feature:
- Connect approved data. Use a database account limited to the tables or reporting views you need, and start with read-only permissions for analysis. Connection guides exist for PostgreSQL, MySQL, SQL Server, BigQuery, and other supported engines.
- Define your business terms. Revenue, active customers, date ranges, and table relationships need explicit definitions, plus verified SQL examples and schema context, so a familiar business phrase maps to the intended data.
- Check before you explore. Compare the first answers against a trusted report and inspect filters, joins, and totals before relying on them.
This matters for plan sizing too: a deployment where business terms are undefined will burn questions on clarifying and correcting, which shows up as higher usage against the same allowance.
What to verify on the pricing page
Because the available pages do not state prices, plan names, or allowance numbers, confirm these directly before deciding:
- Current plan names and what each includes
- The usage allowance attached to each plan, and what happens when it is exceeded
- Whether Desktop and Website Chatbot are billed separately, since they are separate products
- What the enterprise path requires in terms of hosting, model endpoint, and network access
- Whether a locally hosted model is available and how it is scoped
The site's own framing is the most reliable starting point: choose based on who needs answers and where they will ask, then review plans and usage allowances for the numbers.