Feature Matrix
This matrix summarizes the main Siesta AI product modules from a product specification perspective. It is intended as a quick orientation layer before reading the detailed feature pages.
| Module | Availability | Primary Roles | Main Use Case | Dependencies | Known Limitations |
|---|---|---|---|---|---|
| Agents | Core | Admins, agent owners | Create and manage AI agents with instructions, models, data, tools, access, templates, analytics, and history. | Model connection, optional data collections, optional tools, access policies. | Agent quality depends on configuration, data quality, model choice, and tool governance. |
| Chat | Core | Users, admins | Interact with configured agents, attach files, provide feedback, and review conversation history. | At least one available agent. | Access and available agents depend on user role and sharing policies. |
| Public Chat | Configurable | Admins, external visitors | Expose an agent through a public URL for unauthenticated users. | Agent interface settings, tenant public chat setting, optional privacy link. | Should not be enabled for sensitive scenarios without reviewing security, safety, and data exposure. |
| Widget | Configurable | Admins, website visitors | Embed an agent into an external website or portal. | Agent interface settings, embed configuration, optional OAuth client. | Public widget behavior depends on public chat and authenticated widget configuration. |
| Realtime | Configurable | Users, external app users | Run interactive voice or realtime sessions with an agent over WebSocket. | Realtime-enabled model, conversation, realtime session, supported audio format. | Sessions expire, have idle and duration limits, and currently use supported formats such as pcm16. |
| Workflows | Beta | Admins, process owners | Compose multi-step automation using triggers, tools, agents, conditions, and history. | Connections, tools, access policies, optional webhooks. | Workflow behavior depends on external service reliability, permissions, and node configuration. |
| Tasks | Beta | Users, teams, admins | Track work created from conversations, agents, or integrations and process it with an assigned/default agent. | Task workspace, optional source conversation, optional assigned agent. | Auto-execution and workspace behavior should be validated before high-volume integrations. |
| Skills | Core | Admins, agent owners | Define reusable abilities, instructions, and tool bindings that can be assigned to agents. | Available tools/functions, agent configuration. | Poorly scoped skills can make agent behavior less predictable. |
| Memory | Core | Admins, agent owners | Maintain long-term organization knowledge pages and collections for agent context. | Memory collections/pages, agent assignment. | Must be curated and attached intentionally to avoid irrelevant context. |
| Data | Core | Admins, knowledge owners | Create data collections from files and integrations, process documents, inspect chunks, and attach sources to agents. | Source content, provider connections, parsing/indexing pipeline. | Failed sync, unreadable documents, empty chunks, or strict retrieval settings can reduce answer quality. |
| Connections | Core | Admins, integration owners | Manage model connections, external tools, credentials, shared/private access, governance, and token limits. | Provider credentials, OAuth/API keys, organization policies. | External service permissions, rate limits, and governance settings affect availability. |
| External API | Configurable | Developers, integration owners | Let external systems call Siesta AI agents, files, tasks, workspaces, connections, data collections, and audit logs. | API key, organization ID, target resources. | API keys must be protected server-side; realtime requires WebSocket client support. |
| Security | Core | Owners, admins | Manage tenant-wide sharing, profile editing, retention, prompt shield, content safety, and connection governance. | Organization settings, roles, access policies. | Disabling public or unsafe behavior can intentionally block previously available actions. |
| Analytics | Core | Admins, managers | Review usage, costs, recordings, workflows, data activity, and agent performance. | Conversation, token, recording, workflow, and feedback data. | Analytics are historical and should be paired with limits/governance for prevention. |
| Billing | Configurable | Owners, admins | Manage subscription plan, billing sessions, pricing, and usage visibility. | Billing provider configuration and organization subscription state. | Billing availability depends on configured payment provider and plan. |
| Audit Logs | Core | Admins, compliance reviewers | Review administrative and system changes, including who changed what and when. | Audit logging and retention settings. | Available history depends on configured audit log retention. |
Reading Order
Start with Agents, Chat, Connections, and Data for the core platform model. Then review Organization, Tool Executions, and External API for enterprise controls and integration behavior.