Is this another BI tool?

QueryPanel is infrastructure for embedding analytics and generating safe SQL—built for product surfaces, not standalone analyst workspaces.

How do you handle tenant isolation?

Tenant context is part of generation and execution—not something you toggle later in a dashboard filter.

What does implementation look like?

Attach your database with the SDK, wire auth claims, and embed UI where customers already work. Scope follows your surfaces—not building a query engine from scratch.

How do you keep AI SQL accurate as schemas evolve?

Ground generation in synced schema metadata and your knowledge base—annotations, glossaries, and examples—so retrieval and SQL stay aligned with how your data model actually works.

How are tenants counted?

A tenant represents a distinct customer or organization within your SaaS product. We count the number of unique tenants that access or generate analytics in a given billing month.

What counts as an AI chart?

An AI chart is generated whenever an end-user asks a natural language question that results in a new chart, or when an editor uses AI to create or modify a dashboard block.

What happens when limits are exceeded?

You can purchase overage credits for AI charts. For tenant limits, we'll notify you when you approach your plan's limit and help you upgrade to the next tier. We never cut off access for your end-users without warning.

How are AI models selected?

We support OpenAI, Gemini, Anthropic, and even OpenRouter. Bring-your-own-key is available from Starter and above (including Growth and Scale). Custom plans also support bring-your-own-model setups. If you want a specific provider or model path, ping us at csaba.ivancza@querypanel.io.

QueryPanel vs Explo

Customer-facing analytics and white-label reporting for SaaS products, now part of Omni.

Explo built its reputation around customer-facing analytics, AI-powered reports, and fast deployment for SaaS teams. Omni acquired Explo in October 2025 and says Explo customers will transition to Omni before the Explo platform is sunset, so new evaluations should treat this as an Omni-vs-QueryPanel decision rather than a standalone Explo roadmap decision.

Start building Read the docs

Comparison at a glance

This table summarizes typical positioning. Every vendor changes over time—validate details against current documentation and your security review.

Dimension	Explo	QueryPanel
Current product status	Omni acquired Explo in October 2025 and describes Explo as a wholly owned subsidiary during a customer transition period before sunsetting the Explo platform.	Independent QueryPanel roadmap focused on headful React embedded analytics, tenant-aware AI, and headless zero-trust SDK paths.
In-app experience for end users	Explo emphasized dashboards, AI-powered reports, white-label delivery, customer customization, and embedded sharing inside a SaaS product; buyers should now validate how those workflows map to Omni.	First-class `@querypanel/react-sdk` components—`QuerypanelEmbedded` for a full dashboard, or `QueryPanelProvider` with `QueryInput` / `QueryResult` for a bespoke flow. They render in your React tree like any other product screen (layout, router, modals, tokens)—not a separate iframe "mini app" on another origin. Mint short-lived JWTs on your server; never ship your workspace private key to the browser.
Primary product shape	Customer-facing analytics suite centered on dashboards, report builder workflows, exports, and embedded sharing, now part of Omni's broader analytics platform.	AI-native React workspace plus headless Node `ask()` calls for teams that want customer questions, SQL, and charts in one loop.
Trainable knowledge & steering	Analytics behavior and report workflows are configured primarily in the vendor platform around your connected data sources.	Gold SQL queries (curated examples the model prioritizes), database annotations (business context on tables/columns, re-embedded with schema), glossary (domain terms and definitions), and tenant-level definitions (isolation field, enforcement, and per-tenant sync context so every ask() is grounded in the right customer slice—not a one-size global prompt).
Natural language workflow	Explo highlights AI-powered reports and dashboard customization as part of the embedded reporting workflow.	Natural language to SQL and chart generation are central workflows for both the embedded UI and headless API use cases.
Developer ownership	Faster time-to-reporting when dashboards, reports, and delivery methods already match your product expectations, with transition diligence needed for new Explo evaluations.	More developer-owned control: React SDK in the frontend, Node SDK in the backend, auth and execution fully aligned with your app stack.
Security & delivery model	Explo promoted white-label delivery, customer data sharing, direct database connections, and enterprise security features such as dedicated hosting and region-specific stacks; confirm current Omni packaging and hosting terms.	Zero-trust path keeps credentials and query results on customer infrastructure when you need strict data-boundary control.
Best first win	Launch customer dashboards, AI reports, and export/share workflows quickly without building a reporting stack from zero.	Launch customer-facing AI analytics with product-native React UX, tenant-aware SQL generation, and a path to deeper customization.

Account for the Omni transition

Explo buyers should validate the current Omni migration, packaging, and roadmap before treating an Explo proof of concept as a long-term standalone decision. QueryPanel is a separate product path for teams prioritizing AI-native customer questions and a developer-owned embed.

When Explo is the better fit

Honest tradeoffs help your team pick faster—and match how buyers actually decide.

You are already in the Explo or Omni ecosystem and want the migration path Omni is providing for existing Explo customers.
You want a productized embedded reporting stack with dashboards, AI reports, exports, and white-label delivery in one vendor package, and Omni's broader BI platform fits your roadmap.
You care more about fast delivery of branded dashboards and customer reports than about owning the query-generation workflow directly in app code.
You want end users to customize dashboards and receive scheduled or shared data without your team building that whole layer from scratch.

When QueryPanel is the better fit

Choose QueryPanel when you want customer questions, generated SQL, and charts to stay close to your product code and database drivers instead of adopting a broader reporting and export platform.

You want a trainable knowledge system—gold queries, DB annotations, glossary, and tenant-aware definitions—so NL→SQL and charts reflect your business, not generic schema-only guesses.
You want a Notion-like React analytics workspace with built-in AI assistant first, then a headless Node SDK for stricter zero-trust and custom UI paths.
You want natural-language analytics to be the main product interaction, not only AI-assisted report building around dashboards and exports.
You prefer to keep SQL generation reviewable in your own backend path and keep execution with your existing drivers and infrastructure.
You want one SDK path for embedded customer analytics, product-native customization, and server-side `ask()` calls from your own API.

Comparison FAQ

What should Explo customers evaluate after the Omni acquisition?

Confirm the migration timeline, feature mapping, pricing, hosting, and support model for the Explo-to-Omni transition. Also validate whether the resulting platform still fits the customer analytics workflow you plan to own.

Still evaluating Explo and QueryPanel?

Start on the free tier, embed one dashboard, and compare implementation time against your current shortlist.

Start free All comparisons