PRODUCT

Embedded product assistant

Your customers want an assistant inside your product that can actually do things. Building that means solving tenant isolation, per-user scope, credential storage, approval flows and an audit trail before you write a single prompt. That is the part FlozentAi is.

Start building See the demo

The problem

Adding an assistant to a multi-tenant SaaS product means every answer must be scoped to the signed-in user’s tenant, and every action must be attributable. Getting that wrong once is a breach.

How it is built

Register your application and its environments
One application, with development, staging and production environments. Everything below is scoped to one of them.
Exchange your own tokens for agent identities
Your backend already knows who the user is. Token exchange turns that into an end user inside a host tenant — created automatically on first sign-in.
Drop the React component in
The provider takes a token callback and a deployment id. Authentication stays on your backend; the component never sees a long-lived secret.
Publish the actions your product should expose
Usually your own API first. The assistant can do exactly what you published and nothing else.

What you get

An assistant your customers can use on day one, scoped to their own data.
Isolation enforced in the database rather than by prompt instruction.
A per-run audit trail you can show a customer’s security reviewer.

What keeps it safe

End users are resolved from the exchanged token, not from the conversation.
Deployments are per environment, so staging cannot reach production data.
Kill switches let you stop new runs without a deploy.

Start read-only

Publish the read actions, run it for a few weeks, and read the traces. Deciding which writes to publish from evidence is both safer and a much easier internal conversation than deciding from a roadmap.

Questions

Do our customers need FlozentAi accounts?

No. Your customers are host tenants inside your workspace and their users are end users. They sign in to your product exactly as they do now.

Can we style it to match our product?

The React component ships with its own tokens so it does not inherit your page styles by accident, and those tokens are yours to override.

Build beyond the expected.

Create a workspace, register an application, and import your first API.

Create your workspace Read the docs

How it is built

Register your application and its environments

One application, with development, staging and production environments. Everything below is scoped to one of them.

Exchange your own tokens for agent identities

Your backend already knows who the user is. Token exchange turns that into an end user inside a host tenant — created automatically on first sign-in.

Drop the React component in

The provider takes a token callback and a deployment id. Authentication stays on your backend; the component never sees a long-lived secret.

Publish the actions your product should expose

Usually your own API first. The assistant can do exactly what you published and nothing else.