An AI analyst inside your product

You can embed AI chat, the dashboards workspace, insights, automations, and models, each on its own or together in the full app, plus read-only shared dashboards. In React, each one is a component, such as BasedashChat or BasedashDashboards, and an ID prop opens a specific chat, dashboard, or automation. The full app takes props that hide the features you don't want, as long as one of the five stays visible. The embed is the real product, so new Basedash features reach your customers without a release on your side.

Your app signs them in, not Basedash. When a signed-in user opens the page, your server creates a JWT with their email, the Basedash organization ID for their company, and an optional name and role, signs it with that organization's secret, and hands it to the embed. The SDK's createEmbedToken helper does this, with a 10-minute expiry by default. Basedash creates the user and their membership the first time a token is used, so there's no separate account or invite. Keep the secret on your server: anyone holding it can sign in as any user in that organization.

For customer-facing analytics, usually yes. An organization per customer, created through the Basedash API with embedding turned on, gives each one its own data sources, dashboards, members, and JWT secret, so a token for one customer can't reach another's data. If customers share one organization and one Postgres database, Basedash sets a basedash.groups session variable on every query, and your row-level security policies can filter rows by each member's groups. For shared dashboards, a signed filter token can lock a tenant ID instead.

The embed's sidebar shows the organization's own name and icon rather than a Basedash logo, so customers see their company there. You can hide the organization name, remove the sidebar entirely when your app owns navigation, and pick which features appear. The theme can be light, dark, or follow the user's system setting, so it sits naturally in your app. Hiding parts of the embed is presentation only, so use Basedash permissions to control what each member can actually open.

Yes. BasedashChat embeds the AI analyst on its own, and the full app includes it next to dashboards. Customers ask in plain language and get answers, tables, and charts from the data sources in their organization, limited to what their member account can access, and they can keep asking follow-up questions. You can hide the suggested prompts and open a specific chat by ID. Customer data is never used to train AI models.

Yes. Share a dashboard to get a public link and render it with BasedashSharedDashboard or an iframe, with no Basedash user or token. Its filters stay hidden unless you choose to show them. To give each viewer only their own rows, create a filter token on your server that locks values such as a company ID: Basedash verifies the signature, applies the values server-side, and hides those filters, so viewers can't change them. Embedding a single chart on its own isn't available yet.

Embedding is part of the Enterprise plan, along with self-hosting, SSO, and SCIM. You can embed Basedash Cloud or your own self-hosted instance: the SDK takes an instanceUrl, and tokens are created the same way for both. Book a demo to walk through your product, how many customer organizations you expect, and which features you want to show them.

Embeds render Basedash in an iframe, including the React SDK's components, rather than as native React UI. Basedash doesn't expose a messaging API to the host page yet, so the frame doesn't resize itself, report navigation, or take commands from your app, and you give it a fixed or full height instead. Single charts can't be embedded on their own, only shared dashboards and the app itself. If one of these blocks what you're building, tell us about it.