# StackAI — No-code enterprise platform for building, deploying and governing AI agents across business systems.

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

StackAI is a no-code enterprise platform for building AI agents in a drag-and-drop workflow builder, connecting them to company systems and knowledge bases, and publishing them as chat, form, Slack or API interfaces. It is aimed at IT teams in regulated organisations.

| Fact | Value |
| --- | --- |
| Website | https://www.stackai.com |
| Price | Enterprise Custom /month For teams who want a custom experience with advanced security and support. |
| Free tier | Yes |

500 runs per month, 2 projects, 1 seat, community support on Discord. The comparison table marks API Access, Analytics, Custom Domain, SSO, Access Control, on-prem and VPC deployment, BAA and email support as not included on Free.

## What it does

**Writes code** · Partly — Only inside a workflow node: the Code Node ships an AI assistant that drafts Python or TypeScript that runs in a sandbox, not application source in a repository.

> The Code Node lets you write and run custom Python or TypeScript code directly inside a Stack AI workflow, with the help from an AI code assistant.
> — https://docs.stackai.com/workflow-builder/utils-logic-and-others/logic/code-node · Code Node page, opening paragraph

**Done-for-you service** · Partly — You run the software yourself, but enterprise buyers also get StackAI people: forward-deployed engineers, weekly co-building sessions and dedicated solution engineers on the Enterprise plan.

> StackAI provides the platform and forward-deployment engineers to help customers build complex use cases and deploy those with confidence.
> — https://docs.stackai.com/welcome-to-stackai/overview/what-makes-stackai-unique · What Makes StackAI Unique, Implementation Support section

## How much it does unattended

**Runs autonomously** · Yes — Trigger nodes start workflows on external events or on a schedule with no operator present, and human review is an optional node rather than a requirement.

> A Trigger Node is the starting point for any automated workflow. Once a specific event happens, the trigger automatically run your StackAI workflow.
> — https://docs.stackai.com/workflow-builder/inputs/trigger-node · Trigger Node page, opening paragraph

**Multi-agent** · Yes — Subflow Tools let one orchestrating agent call other agents as named specialists, in parallel or in sequence, each with its own workflow and output node.

> Subflow Tools enables orchestrations across a fleet of AI agents.
> — https://docs.stackai.com/workflow-builder/core-nodes/ai-agent-node/subflow-tools · Subflow Tools page, opening paragraph

**Agent permissions** · Yes — Builders choose the stop points: an Ask Human tool pauses a run for approval, while admins allow or block individual tools, connectors and LLMs org-wide.

> It allows an AI workflow to pause execution, request input from a human in the Chat Assistant interface, and then resume execution once the user responds.
> — https://docs.stackai.com/workflow-builder/core-nodes/stackai/human-in-the-loop · Human in the Loop page, Overview section

## Which models it runs on

**Claude** · Yes — Anthropic is one of the providers StackAI supplies hosted keys for, and the agent node's own settings document Claude-specific behaviour such as required streaming on long responses.

> By default, Stack AI provides hosted API keys for popular providers (like OpenAI, Anthropic, etc.) so users can get started quickly.
> — https://docs.stackai.com/workflow-builder/core-nodes/ai-agent-node/llm-hosting-and-governance/llm-provider-governance · LLM Provider Governance page, Turning Off Stack API Keys section

**GPT** · Yes — OpenAI models are selectable directly, and the docs also describe adding them through an Azure OpenAI private-cloud connection for latency and compliance reasons.

> Microsoft Azure and AWS Bedrock offer the ability to host private clouds with OpenAI models. You can add these models in Stack AI using an "Azure" node or "Bedrock" node.
> — https://docs.stackai.com/workflow-builder/core-nodes/ai-agent-node/llm-hosting-and-governance/llms-hosted-on-azure-and-aws-bedrock · LLMs Hosted on Azure & AWS Bedrock, opening paragraph

**Open models** · Yes — Open-weight models are reachable two ways: Llama-family models through a Cerebras key, and any model you host yourself through the Local provider connection.

> Stack AI integrates natively with Cerebras, letting you connect your Cerebras API key and use Llama-family models directly inside your workflows through both the LLM node and the Cerebras action node.
> — https://docs.stackai.com/workflow-builder/apps/cerebras · Cerebras page, What is Cerebras section

**Model choice** · Yes — The buyer picks provider and model per agent node and can switch later from a dropdown; admins may narrow that list but the vendor does not fix one model.

> StackAI is provider-agnostic, just choose your favorite provider and select the model you'd like to use in your project.
> — https://docs.stackai.com/workflow-builder/core-nodes/ai-agent-node · AI Agent Node page, opening paragraph

## Where you use it

**In your editor** · Partly — There is no StackAI editor plugin; the account is reachable from Cursor or Claude via the hosted MCP endpoint, which is an assistant integration rather than an IDE surface.

> The StackAI MCP server connects your AI assistant — Claude, Cursor, or any assistant that supports the Model Context Protocol — directly to your StackAI account.
> — https://docs.stackai.com/interface-and-deployment/mcp-reference/stackai-mcp-server · StackAI MCP Server page, opening paragraph

**On the command line** · Partly — The published CLI installs and maintains the self-hosted platform on customer servers; it is an operations tool for on-prem deployments, not a way to drive an agent from a terminal.

> Enterprise-grade command-line interface for auto-deploying, managing, and maintaining StackAI's platform on customer infrastructure.
> — https://docs.stackai.com/stackai-auto-cli/readme · StackAI Auto CLI page, Overview section

**In your pipeline** · Partly — A GitHub node can read repositories and act on pull requests from inside a workflow, but nothing documents StackAI running as a step in a CI pipeline.

> This node connects your StackAI automation to Github’s powerful API, making it easy to interact with repositories, pull requests, workflows, and more.
> — https://docs.stackai.com/workflow-builder/apps/github · Github page, opening paragraph

**In a browser** · Yes — Everything happens in the browser: a drag-and-drop canvas to build the agent and prebuilt hosted interfaces such as chat, forms and website chatbots to publish it.

> Canvas: the main component of the Stack AI tool, a 2D canvas where you can drag and drop nodes and connect them to build your workflow.
> — https://docs.stackai.com/welcome-to-stackai/overview/platform-overview · Platform Overview page, Workflow View section

## Whose machine it runs on

**Self-hosted** · Partly — On-premise and VPC deployment exist but sit in the Enterprise column of the plan table; the free tier is multi-tenant cloud only, and deployment needs a licensed CLI.

> StackAI's on-premise deployment offers enterprise-grade control, performance, and security by running entirely within your organization's infrastructure.
> — https://docs.stackai.com/welcome-to-stackai/security-and-governance/on-premise · On-Premise page, opening paragraph

**Open source** · No — Even the self-hosted build is proprietary: installing it requires a licence key and private registry credentials issued by an account manager, and the repository linked from the On-Premise page is not public.

> StackAI License Key (provided by StackAI Account Manager)
> — https://docs.stackai.com/stackai-auto-cli/readme · StackAI Auto CLI page, Prerequisites, Required Credentials list

## What it costs to run

**How it meters** · Yes — Consumption is metered in runs, where a run is one workflow execution; seats and projects are counted separately and the Enterprise run allowance is negotiated.

> In StackAI, a run represents the execution of a workflow instance.
> — https://www.stackai.com/pricing · Pricing FAQ, 'What is a run in StackAI?' answer

**Free tier** · Yes — A standing zero-cost plan with 500 runs a month, two projects and one seat lets you build without talking to sales, though support is Discord only.

> Start for free. Upgrade to get the capacity that exactly matches your team's needs.
> — https://www.stackai.com/pricing · Plan cards, Free plan column

**API access** · Partly — Any published flow can be called as a REST endpoint with an org token, but the plan comparison marks API Access as an Enterprise row while ticking the REST API plugin on Free.

> Once your flow is ready for production, you can deploy it as an API. Just click on deploy to get a production-ready version of your model.
> — https://docs.stackai.com/interface-and-deployment/end-user-interfaces/api · API page, Get your RestAPI section

**MCP server** · Yes — A hosted MCP server lets another assistant list, read, run and edit your workflows after an OAuth sign-in, and a MCP node lets your agents call outside MCP servers.

> The connection URL is https://mcp.stack.ai/mcp, the same for everyone.
> — https://docs.stackai.com/interface-and-deployment/mcp-reference/stackai-mcp-server · StackAI MCP Server page, Connect your assistant section

**Bring your own key** · Yes — Organisations can attach their own provider API keys, make them the workspace default, and switch off StackAI-supplied keys so all inference bills to their own accounts.

> Once disabled, users must add their own connection (API key) to use that provider in workflows.
> — https://docs.stackai.com/workflow-builder/core-nodes/ai-agent-node/llm-hosting-and-governance/llm-provider-governance · LLM Provider Governance page, Turning Off Stack API Keys section

## Buying it for a team

**A company can buy it** · Yes — The Enterprise plan is sold to organisations by quote and bundles seats, access control, SSO and compliance paperwork; there is no self-serve paid individual plan.

> For teams who want a custom experience with advanced security and support.
> — https://www.stackai.com/pricing · Plan cards, Enterprise column description

**Seat model** · Partly — Seats are counted - one on the free plan, a negotiated number on Enterprise - but no per-seat price, floor or ceiling is published anywhere on the site.

> Custom number of seats
> — https://www.stackai.com/pricing · Plan cards, Enterprise key features list

**Admin controls** · Yes — Admins constrain the agents centrally: enable or disable individual LLMs, apps and tools, force org API keys, restrict who may publish and require SSO on interfaces.

> Feature access allows admins to manage Multi-Factor Authentication, Knowledge Bases, LLM access, and more.
> — https://docs.stackai.com/welcome-to-stackai/security-and-governance/security-in-stackai/feature-access · Feature Access page, opening lines

**Audit log** · Partly — Run-level activity and project version history are recorded and downloadable, but no page documents an audit trail of administrative actions such as role or policy changes.

> Downloadable project analytics show who ran what, when, with which models, token counts, latency, and per-step traces (inputs, KB hits, outputs).
> — https://docs.stackai.com/welcome-to-stackai/security-and-governance/ai-governance · AI Governance page, layer 7 Production Analytics and Auditing

**Single sign-on** · Partly — SAML SSO with Okta or Entra plus SCIM provisioning is documented, but the plan comparison shows SSO unavailable on Free and included only with Enterprise.

> Connect your Identity Provider to enable login and role-mapping through SAML protocol.
> — https://www.stackai.com/security · Security page, Custom SSO card

_Not established: Pooled budget_

## What happens to your code

**Opt out of training** · Yes — No opt-out toggle is needed because the vendor states training is contractually excluded through DPAs with the model providers; its OpenAI and Anthropic DPAs are published.

> We ensure that your data is not used for training AI models through data processing addendums (DPAs).
> — https://www.stackai.com/security · Security page, No Training on Your Data card

**Data residency** · Partly — Residency is solved by moving the software, not by picking a region: on-premise and VPC deployments are offered, while no region list is published for the hosted cloud.

> For organizations with strict data residency or sovereignty requirements, StackAI offers On-Premise deployment options, critical for industries like defense and finance.
> — https://docs.stackai.com/welcome-to-stackai/overview/what-makes-stackai-unique · What Makes StackAI Unique, AI Governance section

**Getting out** · Yes — Projects export to a JSON file you can keep or re-import, and analytics are downloadable; runs are a monthly allowance rather than credits that accrue.

> A JSON file will be downloaded, this is the workflow that can be imported or saved locally.
> — https://docs.stackai.com/interface-and-deployment/end-user-interfaces/exporting-and-importing-projects · Exporting and Importing Projects page, Exporting a Workflow step 3

**Certifications** · Yes — The docs claim SOC 2 Type II, HIPAA, GDPR, CCPA-CPRA and ISO 27001, a SOC 2 report is requestable and a BAA is listed as an Enterprise-only row.

> StackAI is SOC 2 Type II, HIPAA, GDPR, and CCPA-CPRA compliant, with ISO 27001 certification.
> — https://docs.stackai.com/welcome-to-stackai/overview/what-makes-stackai-unique · What Makes StackAI Unique, AI Governance section

## 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-09 — Capabilities · Commercial terms · Free tier · Price

## Correcting this record

Anything marked "Not established" is a question we have not answered — it is not a No. If you represent StackAI, 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.