Straight answers about Blazorly.

Builder plans, configures, refines, and publishes business applications. The SaaS Client and Conversational Client are the two interfaces for working a published app — through familiar screens, or through conversation. Blazorly Agent is for building, testing, deploying, and operating tool-using AI agents. Crew is the product-operations control plane for teams of Agent-powered AI Mates. One shorthand: Builder configures apps, the Clients run them, Agent executes, Crew coordinates.

No. Builder produces an explicit application configuration — schemas, forms, lists, detail views, rules, actions, navigation, themes, and dashboards — and publishes it to Blazorly's shared runtime. You can inspect everything in Project Studio, including a JSON view, and every publish has version history. There is no generated codebase, terminal, or deployment pipeline to manage.

On Blazorly's shared runtime. Builder previews against it while an application is being refined, and published versions are served to the SaaS Client and Conversational Client from the same runtime.

Supported data-changing actions go through an approval step: the client presents the proposed values, you review and can edit them, and you approve or reject before anything executes. The Conversational Client is grounded in one published application — it is an application interface, not a general agent builder.

Blazorly Agent. It covers outcome-driven creation, tools and isolated workspaces, knowledge, skills, and memory, connected applications with explicit grants, testing and evaluation before release, and versioned deployment with observability.

Crew gives each product a team of AI Mates that share reviewed product knowledge, work in a team room or direct chats, hand off bounded work, and hold sensitive actions for founder approval. Connected applications use narrow grants, with Blazorly Agent retaining credentials and execution authority. Crew is built for founders and product teams who want coordinated AI teammates with visible control. Crew coordinates; Agent executes.

Blazorly is in private invitation beta, so there is no public signup, free tier, or trial. Request access, describe the work you want to change — an application, an agent, or a Crew — and we will assess fit together. Access is arranged directly if there is a fit.

There is no public pricing during the private beta. Beta terms are discussed individually as part of the access conversation, and the plan is to publish pricing at general availability.

An agent can only use the tools, knowledge, connections, and release settings made available to it. Capabilities are explicit, workspaces are isolated, behaviour is tested and evaluated before release, deployments are versioned, and sensitive actions can be held at configured approval boundaries.

Security is expressed through product-specific controls: authenticated access, managed runtime and data services, supervision and approvals, and credential separation between Agent and Crew. Blazorly does not currently claim SOC 2, ISO 27001, or HIPAA certification. Read the security page for current boundaries, and ask about the architecture relevant to your use before placing sensitive work in a beta environment.

The use cases page shows example patterns for operational applications, standalone agents, connected agents, and supervised Crews — including what gets modelled, what people use, and where the agent helps. They are patterns, not pre-built promises.