# Aisera Agent Composer (Agent Studio) — Conversational, no-code builder for enterprise AI agents on the Aisera platform.

> Source: The Agents Index — https://theagentsindex.com/aisera-agent-studio (structured, researched, re-verified)
> Facts last verified: 2026-09-24

Agent Composer is the builder in Aisera's enterprise agent platform, where admins describe an agent in natural language instead of drawing flows or writing code. It configures data sources, tools, triggers and guardrails, then tests and publishes the agent to enterprise channels.

| Fact | Value |
| --- | --- |
| Website | https://aisera.com/platform/agent-studio |
| Price | See it in action |
| Free tier | Not applicable |

No free plan and no trial. /pricing returns HTTP 404, no pricing page appears among the 104 URLs in the page sitemap, and every call to action on the site is 'Get a demo', 'Contact Us' or 'Submit RFP'. The Automation Anywhere Cloud Community Edition that is free is the acquirer's RPA product, not Aisera Agent Studio.

## What it does

**Writes code** · Partly — Agent Composer generates the agent itself from a natural-language description and exposes the auto-generated code for editing, but it authors agent and workflow logic rather than application source files.

> Access the underlying auto-generated code of any agent code for deeper customization, allowing developers and admins to fine-tune every detail to perform exactly as needed.
> — https://aisera.com/platform/agent-studio/ · 'Elevate agent building with the complete toolkit' section, 'GO FROM NO-CODE TO PRO-CODE WITH EASE' card

**Debugs and fixes** · Partly — Debugging is a separate Aisera product line, AI Code Generation, not a documented capability of Agent Composer; it corrects supplied code rather than diagnosing and landing a fix in a repository.

> Automatically debug and correct code using GenAI. Using domain-specific LLMs for engineering, Aisera identifies and fixes errors to improve code quality while reducing debugging times.
> — https://aisera.com/products/ai-code-generation/ · 'Code Debugging & Correction' section

**Writes tests** · Partly — It generates test cases, but conversational ones: the documented Test Suite turns historical requests and knowledge-base articles into replayable cases that check agent behaviour, not unit tests for source code.

> You can generate a test case from a conversation request between a user and a chatbot.
> — https://docs.aisera.com/aisera-platform/ai-workbench-optimize-conversations/test-suite.md · Test Suite, Types of Test Cases, Request to Test Case bullet

**Reviews code** · No — The only sentence Aisera writes about code review is about generating cleaner code so review is easier; nothing anywhere on the site or in the docs describes reading a diff someone else wrote.

> Streamline the code review process by generating high-quality code that adheres to best practices with Generative AI, resulting in cleaner and more maintainable code.
> — https://aisera.com/products/ai-code-generation/ · Enhance Code Quality benefit card

**Whole-codebase work** · Partly — The granularity the vendor claims is lines and files, not repositories: conversion works on lines of code and codebase support is explanation and summarisation, with no repo-wide migration claim.

> Aisera can convert lines of code into any language, helping developers work across different systems and languages with ease.
> — https://aisera.com/products/ai-code-generation/ · Multi-Language AI Code Generation & Conversion section

**Ships it** · Yes — Built agents and workflows are deployed by the builder itself: publishing is a mandatory, version-controlled step in the Admin UI with rollback, so work does not stop at a draft.

> After you've saved, the Save button is grayed out and the Publish button becomes available to deploy the workflow.
> — https://docs.aisera.com/aisera-platform/what-can-my-bot-do/ai-automation-optimize-flow/ai-workflow-studio/publishing-workflows · Opening paragraph and 'Versioning' section

**Done-for-you service** · No — Aisera sells software the customer's own admins operate; the FAQ frames Agent Composer as a tool for IT, HR or support admins rather than a service Aisera staff run for you.

> Agent Composer is purpose-built so IT admins, HR admins, or support managers – can build AI agents without writing code.
> — https://aisera.com/platform/agent-studio/ · Agent Studio FAQs, 'Can Agent Composer build AI agents with no coding?'

## How much it does unattended

**Runs autonomously** · Yes — Event Studio lets agents be triggered by system events and resolve issues without a person starting the task, and the orchestration engine plans and executes multi-step fulfilment itself.

> Build proactive triggers that enable autonomous issue resolution and reduce response times.
> — https://aisera.com/platform/agent-studio/ · 'Democratize AI agent creation using agent composer' tabs, Event studio tab

**Multi-agent** · Yes — Native orchestration between domain-specific agents is shipped and documented; coordination with third-party agents over A2A is a separate, unreleased capability held in Aisera Unify.

> Create domain-specific agents and orchestrate between them with universal AI agent orchestration. Federate bot development among multiple providers while maintaining governance and control.
> — https://aisera.com/platform/ai-agent-orchestration/ · Universal Orchestration section

**Agent permissions** · Partly — Guardrails bound what an agent may do and a workflow can be forced to pause for a named human approver, so autonomy is configurable per flow rather than unrestricted or fully hands-off.

> Use the Ask Approval node to send email for approval through a channel such as Slack, MS Teams, or Webchat.
> — https://docs.aisera.com/aisera-platform/what-can-my-bot-do/ai-automation-optimize-flow/ai-workflow-studio/workflow-reference-guides/workflow-nodes/action-nodes/ask-approval · 'Ask Approval' node description

## Which models it runs on

**GPT** · Yes — OpenAI models are named among the selectable third-party foundation models, and the Prompts Studio documentation exposes editable prompts for an Azure OpenAI GPT model, so GPT is a first-class option.

> or select third-party FMs (like Azure AI, Open AI, Google Vertex AI, Llama 3, AWS Bedrock, and more) to build a robust AI stack that is suited to your enterprise needs.
> — https://aisera.com/products/llm/ · 'Select Your Foundational Model (FM) of Choice' section

**Open models** · Yes — Open-weight models are supported both as a customer choice (Llama 3 in the selectable model list) and internally, since Aisera's own domain LLMs are built on open-source models.

> These domain-specific LLMs use open-source models and proprietary datasets
> — https://docs.aisera.com/aisera-platform/llm-operations/aiseras-domain-specific-llms · 'Aisera's Domain Specific LLMs' opening paragraph

**Model choice** · Yes — The buyer picks the foundation model, Aisera's own or a third party's, and the LLM Gateway can also route automatically between open and closed models for cost and latency.

> select third-party FMs (like Azure AI, Open AI, Google Vertex AI, Llama 3, AWS Bedrock, and more) to build a robust AI stack that is suited to your enterprise needs.
> — https://aisera.com/products/llm/ · 'Select Your Foundational Model (FM) of Choice' heading and body

_Not established: Claude_

## Where you use it

**In your editor** · No — The vendor positions the absence of an IDE as the point of the product: agents are built conversationally in the browser Admin UI, so there is no editor plug-in to install.

> Code- and flow-based agent builders are a thing of the past. The new era of agent building is here – conversational, and lightning-fast. No IDEs, no coding, no expertise required.
> — https://aisera.com/platform/agent-studio/ · Hero paragraph under the 'Agent Composer' heading

**On the command line** · Partly — A terminal surface exists but not for agent building: the documented CLI belongs to the LLM Gateway developer tooling and covers managing applications, deploying models and monitoring usage.

> Command-Line Interface (CLI): Offers a set of command-line tools for managing applications, deploying models, and monitoring usage.
> — https://docs.aisera.com/aisera-platform/llm-operations/llm-gateway.md · Architecture Components, item 5 Developer Tools

**In your pipeline** · No — The closest the vendor gets to CI is telling a developer that a build broke. No pull-request action, no pipeline step, and no repository integration appears on the site or in the docs.

> Keep developers up to date with proactive notification of critical events, such as code review requests and build failures.
> — https://aisera.com/products/ai-code-generation/ · Proactive Notifications for Critical Events section

**In a browser** · Yes — Everything is done in a hosted browser console: agents, workflows, MCP servers and tenant settings are all configured from the Aisera Admin UI, which is where the studios live.

> The Aisera Admin UI enables you to manage administrators, developers, and other team members responsible for configuring and maintaining Aisera Applications.
> — https://docs.aisera.com/aisera-platform/tenant-setup/aisera-platform-configuration/aisera-platform-roles-and-permissions · 'Introduction to Aisera Permissions' paragraph

## Whose machine it runs on

**Self-hosted** · Partly — The vendor claims VPC, hybrid and on-premises deployment alongside the public clouds, but publishes no installation documentation; the only on-prem component documented is the Remote Executor connector.

> Aisera provides seamless deployment options across major cloud providers (AWS, Azure, GCP), VPCs, hybrid clouds, and on-prem environments.
> — https://aisera.com/traps/ · 'Flexible deployment options' card

**Open source** · No — Aisera describes its platform and tooling as proprietary and publishes no repository, licence or source distribution anywhere on the site or in the documentation portal.

> Aisera provides a proprietary security system that uses a Trusted, Responsible, Auditable, Private, and Secure (TRAPS) framework to protect your applications against attacks.
> — https://docs.aisera.com/aisera-platform/tenant-setup/security-and-privacy-traps · 'Security and Privacy (TRAPS)' opening paragraph

## What it costs to run

**Free tier** · No — Every entry path is a sales conversation - demo, contact or RFP form - and no free plan, self-serve signup or time-limited trial is offered anywhere on the site.

> We would love to hear from you on how Aisera can be the vendor of choice for your AI and automation journey, and send a quote tailored to your requirements.
> — https://aisera.com/rfp/ · Get a personalized quote, opening paragraph

**API access** · Yes — A documented API surface exists for driving the product from your own stack: conversation and workflow APIs for custom front ends, plus ingestion APIs and listener channels that let external systems trigger agent workflows.

> You can utilize Conversation & Workflows APIs to build custom conversational interfaces, while Ingestion APIs enable seamless data transfer and trigger AI workflows from external systems.
> — https://docs.aisera.com/apis/apis · 'Overview' and 'Types of APIs' sections

**MCP server** · Partly — MCP is supported in one direction only: Aisera acts as an MCP client consuming external servers' tools, capped at ten per tenant, and no MCP server endpoint is documented for another agent to query Aisera.

> Connect external tools to Aisera using the Model Context Protocol (MCP). Registered MCP tools become available as fulfillment sources in your AiseraGPT applications
> — https://docs.aisera.com/aisera-platform/what-can-my-bot-do/mcp-client · 'MCP servers' section

**Bring your own key** · Partly — You can bring your own foundation model and run in your own cloud, VPC or on-prem estate, but the vendor documents no bring-your-own-inference-key mechanism for the models it hosts.

> or select third-party FMs (like Azure AI, Open AI, Google Vertex AI, Llama 3, AWS Bedrock, and more) to build a robust AI stack that is suited to your enterprise needs.
> — https://aisera.com/products/llm/ · 'Select Your Foundational Model (FM) of Choice' section

_Not established: How it meters_

## Buying it for a team

**A company can buy it** · Yes — This is an organisational purchase by construction: the unit of deployment is a tenant with administrators, developers and role-managed team members, and no individual self-serve path exists.

> The Aisera Admin UI enables you to manage administrators, developers, and other team members responsible for configuring and maintaining Aisera Applications.
> — https://docs.aisera.com/aisera-platform/tenant-setup/aisera-platform-configuration/aisera-platform-roles-and-permissions · 'Introduction to Aisera Permissions' paragraph

**Admin controls** · Yes — Role-based access control with Write, Read, Restricted and None privilege levels per feature lets an admin decide who may touch intents, fulfilments, integrations and data sources, and guardrails bound agent behaviour.

> It offers comprehensive tools for creating, managing, and restricting team members using a Role Based Access Control System (RBAC).
> — https://docs.aisera.com/aisera-platform/tenant-setup/aisera-platform-configuration/aisera-platform-roles-and-permissions · 'Introduction to Aisera Permissions' paragraph

**Audit log** · Yes — A tenant-wide Audit Trail records system events, ingestion, processing and user-initiated actions with the initiator recorded, and those logs can be exported to third-party systems such as Splunk.

> The logs document system events, data ingestion, processing, and user-initiated actions. They include details about the initiator of actions, enabling comprehensive auditing and accountability.
> — https://docs.aisera.com/aisera-platform/tenant-setup/aisera-platform-configuration/audit-trail · 'Logs' section

**Single sign-on** · Yes — SAML single sign-on is configurable for the Admin UI against any IdP that supplies login URL, logout URL and an X509 certificate, with step-by-step guides for Entra ID and Okta.

> This guide details the steps required to configure Security Assertion Markup Language(SAML) Single Sign-On (SSO) for accessing the Aisera Admin UI.
> — https://docs.aisera.com/aisera-platform/tenant-setup/aisera-platform-configuration/setting-up-sso-authentication · 'Overview' and 'SAML Application Configurations' sections

_Not established: Seat model, Pooled budget_

## What happens to your code

**Opt out of training** · Yes — Aisera states as a blanket commitment, not a setting you must find, that it neither retains customer data nor trains other models on it; the TRAPS page repeats this for other customers' models.

> With Aisera, your data remains yours. Aisera does not retain your data and does not use your organization’s data to train other models.
> — https://aisera.com/traps/ · 'Ensure trust & confidentiality' card

**Data residency** · Partly — The hosted default is the United States under the EU-US, UK and Swiss-US Data Privacy Framework, with no published region menu; choosing a jurisdiction means taking the VPC, hybrid or on-premises deployment instead.

> Your Personal Data may be collected, transferred to and stored by us in the United States and by our affiliates and third parties that are based in other countries.
> — https://aisera.com/privacy-policy/ · International transfer of Personal Data

**Getting out** · Partly — Configuration is portable: workflows export as downloadable files for import into another app, and audit logs and request transcripts export to external systems. No full-tenant data export or credit-expiry policy is published.

> AI Workflow Studio supports a new job-based export and import process for workflows, powered by App Sync.
> — https://docs.aisera.com/aisera-platform/what-can-my-bot-do/ai-automation-optimize-flow/ai-workflow-studio/export-and-import-workflows · 'To export Workflows' procedure

**Certifications** · Yes — Aisera names a full certification set covering security and privacy frameworks, and adds PII anonymisation; certificates themselves are not published on the page, so the claim rests on the vendor's own statement.

> Aisera is ISO/IEC 27001 and CSA Star Level 1 certified, and is also SOC 2, GDPR, HIPAA/BAA, and CCPA compliant.
> — https://aisera.com/traps/ · 'Security & compliance' card

## Provenance

Every fact above comes from the vendor. Nothing here is independently corroborated yet.

## Coverage elsewhere

None recorded. Every fact above comes from the vendor and is not independently corroborated yet.

## What changed

- 2026-09-24 — Capabilities · Commercial terms · Free tier · Price
- 2026-09-03 — Capabilities · Commercial terms · Free tier

## Correcting this record

Anything marked "Not established" is a question we have not answered — it is not a No. If you represent Aisera Agent Composer (Agent Studio), or anything here is wrong or out of date, you can supply it with a source: the operations this site accepts from an agent are listed at https://theagentsindex.com/.well-known/agents.json — that catalogue needs no key to read, and each entry states its own auth.

Supplying evidence is free. Nothing that can be bought here changes what a field says, whether a gap is closed, or how this record is scored.
