---
title: "Community Plan"
canonical: https://trickest.com/docs/key-concepts/community-plan
description: "Run workflows on self-hosted machines. Community Agent chat uses a verified provider key unless the workspace has Managed AI."
---

# Community Plan

## Included in the Plan

The Community plan lets you build workflows and execute them on your own machines. **Workflow execution does not require an AI provider key.** Agent chat on Community requires a verified provider key, unless the workspace has [Managed AI](/docs/key-concepts/agent/managed-ai).

| Capability | How it works |
|---|---|
| Workflow builder and Library | Build workflows or copy a public workflow into your space. |
| Self-hosted execution | Attach your machines to a self-hosted fleet. |
| Agent | On Community, chat uses a verified provider key. [Managed AI](/docs/key-concepts/agent/managed-ai) is separate, and the plan name does not enable it. |
| Developer access | Use the CLI, SDK, API, or MCP with your account's access. |

Check **Settings > Vault > Plan & usage** for your account's limits and retention, and **Settings > Infrastructure > Fleet** for machine capacity. Export results you need to keep beyond the applicable retention period.

## Your Workflows Run on Your Machines

Attach at least one machine and confirm it is **Online** before executing a workflow on its fleet:

```bash
curl -fsSL https://trickest.io/install.sh | sh
trickest auth login
trickest attach
```

The attach command installs the execution agent and connects the host to your fleet. Review the host requirements and setup in [Using Self-Hosted Machines](/docs/using-the-app/private-execution-networking/using-self-hosted-machines).

An online machine still needs access to the workflow's images, inputs, and targets. Inspect queued or failed tasks rather than assuming an online connection guarantees a successful run.

## The Agent on Community

On the Community plan, Agent chat uses a verified provider key. Add it under **Settings > Agent > Bring your own key**. After the key is verified, choose a model in Agent. Usage bills the provider account that owns the key. People in the vault share that key.

Opening the Agent does not verify a key for you. Follow [Bring Your Own Key](/docs/using-the-app/agent/bring-your-own-key) to finish setup.

A workspace with [Managed AI](/docs/key-concepts/agent/managed-ai) can use the Agent without that key. [The Agent](/docs/key-concepts/agent/the-agent) explains how the two options relate.

## Developer Access

The CLI can sign in through the browser. For integrations that require an API token, open **Settings > Personal > API & apps** at `/settings/credentials`. Credentials authenticate your account; they do not bypass its permissions or plan limits.

- [CLI](/docs/developer-tools/cli): manage workflows from the terminal.
- [SDK](/docs/developer-tools/sdk): integrate the platform from TypeScript.
- [API](/platform/api): use the HTTP endpoints directly.
- [MCP](/docs/developer-tools/mcp): connect a compatible agent client.

## Moving to Enterprise

Enterprise configurations can include managed workflow compute, [Managed AI](/docs/key-concepts/agent/managed-ai) for the Agent, and team access management. Managed AI is enabled per workspace. Agreeing an Enterprise plan does not by itself turn it on. [Contact the team](/demo) to confirm the capacity and features your deployment needs.

---
_Markdown source of https://trickest.com/docs/key-concepts/community-plan._