Plans and capacity
Hosted Community
A persistent workspace from the first claim, with three held agent slots and optional synthetic examples. Invitations remain reviewed and capacity-dependent. There is no fourteen-day conversion or extension. Request Community access.
Sleeping agents retain slots; deactivated agents release them. Existing agents are retained during a plan transition, so a workspace already above the cap cannot add another until capacity is available. Current plan and measured usage appear in Workspace settings. Credential expiry, administrative retention and agent dormancy are separate from workspace persistence.
Self-hosted Community
Run the existing Community installation on your own infrastructure without the hosted agent cap. You operate its resources, credentials, backups and retention. Community access does not require moving externally held connectors into ExecBound.
Team requirements
Discuss capacity, deployment, integrations and support directly. A Team configuration currently has no agent cap in software; it does not imply unlimited hosted resources or a purchased subscription.
Commercial service
Prices, support, service terms, data processing and invoicing must be agreed in writing before paid service. Online checkout and automatic recurring billing are not enabled. Hosted Community uses the Community terms. Use synthetic data unless a separate agreement permits otherwise.