







01
Sigma Agents run on business logic your team already built. Skip the vector databases and RAG pipelines and begin capturing human-in-the-loop insights directly today.
02
Writeback, webhooks, API actions, input tables, and scheduled triggers are trusted, proven methods across thousands of apps. Accelerate worklflows today.
03
Every Sigma Agent action respects existing read and write permissions so no one sees or updates the wrong data. No shadow AI or compliance surprises.
04
Stop settling for basic text markdown responses. Sigma Agents produce live AI Apps connected to your warehouse and can even help you build more Agents.


The questions we think every enterprise should ask when evaluating AI Agents.
Yes. Every write from a Sigma Agent is executed natively within the warehouse using the Sigma Actions framework. All operations inherit existing row-level and column-level security policies. Every action is logged in the warehouse's audit trail, giving compliance teams an immutable record of who accessed what, when, and what was changed.
Security is entirely inherited. Sigma passes the authenticated user's identity directly to your warehouse via OAuth Passthrough. The agent physically cannot reason over data the executing user is restricted from viewing. There are zero duplicate permission models to maintain.
Because Sigma compiles every agent action to SQL against your warehouse's semantic layer, changes to your data model are reflected automatically. Unlike custom Python agents or LangChain scripts, there is no brittle code to rewrite when a table schema evolves.
Absolutely. Sigma Agents operate across three modes: Interactive (chat-driven with human approval), Autonomous (scheduled monitoring and execution), and External Actions (API calls to third-party systems). You can start fully supervised and scale autonomy as institutional trust grows.
A copilot answers questions — an agent takes action. Sigma Agents don't just surface insights; they execute writes, trigger REST API calls, fire webhooks, and interface with external systems like Salesforce, Jira, and Slack. The critical distinction: Agents act, everything else informs.
No. All agent processing runs on your warehouse compute. Sigma compiles agent operations into SQL or native platform functions and pushes them to the warehouse. No data is sent to external AI services unless you explicitly configure an external function.
Sigma will operate as both an MCP client and an MCP server. As a client, agents pull context from external CRMs and document stores. As a server, Sigma exposes governed data, dbt semantic models, and tested workflows to external AI tools to act as a single governed endpoint.
Most aren't. Build confidence by identifying and beginning to iteratively automate your enterprise's most high-value workflows. Enhance and accelerate them with AI to guide where building Sigma Agents could add the most value. Leverage the business logic already built and integrate agents that detect anomalies, trigger API actions, and fire webhooks depending on the use case to complete your agentic enterprise evolution when ready.