The same application, worked through conversation.

It is a conversational interface embedded in a published Blazorly application, so you work the same app through conversation instead of navigating screen by screen. You can ask in plain language what needs attention, list, find, retrieve, and summarise records, and prepare changes through a command-deck interface grounded in the application's schemas, data, and configured actions. Conversation history persists, and voice input or spoken responses are available where browser support allows.

All three work with the same published application: Builder configures and publishes it, while the SaaS Client and Conversational Client are the two ways to work it. The SaaS Client is the familiar screen-based workspace with dashboards, lists, forms, and detail views; the Conversational Client covers the same records and actions through conversation, which suits exception handling and rapid record retrieval. They complement each other rather than replace one another.

No. Supported data-changing actions — create, update, delete, or running configured actions — go through an explicit approval step: the client presents the proposed values, you can review and edit them, and you approve or reject before anything executes. Reading and summarising records works within the data available in the application, with results shown as schema-aware cards you can inspect.

It is an application interface, not a general-purpose agent builder. It is grounded in one published Blazorly application and complements that app's SaaS Client; it does not build or deploy standalone agents. If you need a broader tool-using agent with its own knowledge, connectors, tests, and channels, that is Blazorly Agent.

Blazorly is in private invitation beta, so there is no public signup, free tier, or trial for the Conversational Client. Request access, describe the work you want to change, and fit is assessed together; if there is a fit, access is arranged directly, with beta terms discussed individually.