UI Bakery

The agent takes authenticated action in outside systems through documented tools. It applies migrations to the app database, executes actions against connected data sources (query a database, check system state, call an API), syncs data source structure, and connects generated apps to 45+ data sources and a Git repository. The executing actions tool is scoped to inspection for answering requests.

Sourcedocs.uibakery.io/build-with-ai/features.mdread 2026-10-02

A single agent runs multi step execution. It shows each step it takes while generating an app, reads logs to address issues and applies migrations along the way. No multi agent execution, subagents or orchestration of the agent inside workflows is documented. Platform automations schedule app actions, not the agent.

Sourcedocs.uibakery.io/build-from-scratch/custom-appread 2026-10-02

The agent assembles context from the app itself. It knows the app's schema, code and configuration, keeps a synced model of each data source's structure, and can inspect real data through actions. No maintained retrieval structure over the customer's documents or knowledge (index, embeddings layer or knowledge base) is documented for the agent.

Sourcedocs.uibakery.io/build-with-ai/features.mdread 2026-10-02

The vendor ships approval before an action commits. Each agent tool (migrations, screenshots, executing actions, syncing data sources) can be set per app to Always ask, which pauses the agent in the chat for Execute or Reject on migrations and Always allow, Allow once or Deny once on the others. Executing actions against data defaults to Always ask. Checkpoints revert the app and releases are an explicit step.

Sourcedocs.uibakery.io/build-with-ai/features.mdread 2026-10-02

Both halves of the bar are documented. On access, Builder has built in roles, Team adds role based access control and audit logs, and Enterprise adds SSO through Okta, Azure AD, SAML, OpenID and OAuth 2.0 with role mapping and SCIM 2.0. Generated apps can inherit workspace SSO, RBAC and audit logs. On compliance, a SOC 2 Type 2 badge sits in the site footer, with security and AI security pages in the docs. The attestation rests on the badge, so ask the vendor for the SOC 2 report.

Sourceuibakery.io/pricingread 2026-10-02

The builder keeps a runtime record of agent work. It shows each step the agent takes while generating an app, tool permission prompts appear in the chat history, a Logs panel shows current app logs, checkpoints record each prompt's resulting state, release history lists every released version, and audit logs record user actions on Team and above. Retention of agent step history is not stated.

Sourcedocs.uibakery.io/build-from-scratch/custom-appread 2026-10-02

The agent keeps conversation state within a chat, with checkpoints to revert the app to an earlier state and a New chat option to start fresh. AGENTS.md holds app level instructions the agent applies on every build, which are instructions the product applies rather than memory. No memory layer with a stated scope and lifetime is documented.

Sourcedocs.uibakery.io/build-with-ai/agentread 2026-10-02

UI Bakery offers named customer environment options. Enterprise runs a dedicated execution environment and database in the region of the customer's choice, and the platform self hosts on Docker, Kubernetes and cloud VMs, including air gapped and multi instance deployments. Self hosted installations still draw AI credits from a linked cloud workspace unless an Enterprise customer brings its own model provider key, and the Custom App feature on premises requires contacting support.

Sourceuibakery.io/pricingread 2026-10-02

Builders get customer adoptable starting points for the agent's work. The Build with AI flow lets a builder select from ready made templates instead of writing a prompt, and the site publishes app recipes (pre built templated apps) for internal tools, dashboards and portals.

Sourcedocs.uibakery.io/build-with-airead 2026-10-02

Work reaches the agent only when someone starts it, through prompts in the builder chat, and external AI agents can drive the workspace through the MCP server (beta). No autonomous wake for the agent on an event, schedule or webhook is documented. Scheduled jobs and webhooks run app actions, not the agent.

Sourcedocs.uibakery.io/build-with-ai/agentread 2026-10-02

Customer control of the model is limited. Enterprise can bring its own AI model provider key, but no customer selection of the model the agent uses is documented, and the Build with AI guide says only that UI Bakery runs on third party LLMs. The replaceable AI datasource applies to AI actions inside generated apps, not to the agent.

Sourceuibakery.io/pricingread 2026-10-02

UI Bakery documents interfaces to its own platform. An Instance API automates app releases and a SCIM 2.0 API manages user accounts on self hosted installations, webhooks let other services start app actions, and an MCP server (beta) lets external AI agents build apps and manage the workspace.

Sourcedocs.uibakery.io/llms.txtread 2026-10-02

The agent checks its own work rather than running evaluations. It reads app logs to fix the issues it finds and uses the screenshot tool to compare rendered UI against intent, and builders can revert to checkpoints. No evaluation harness, scored test cases or quality gate in the release path is documented.

Sourcedocs.uibakery.io/build-with-ai/features.mdread 2026-10-02

No browser, desktop or remote computer control by the agent is documented. The screenshot tool comes closest, letting the agent inspect the rendered state of the app it is building, but that is viewing its own output rather than operating an interface.

Sourcedocs.uibakery.io/build-with-ai/features.mdread 2026-10-02