Are you interested in this? Help me with a star on GitHub.
Pricing
Choose the tier by who or what can influence official process state. Controlled runs are unlimited because the point is to put more work inside the control loop, not to ration it. You pay for authority, connections, shared roles, governance, and deployment needs.
One local user. Unlimited local controlled runs. No external event intake.
PERSONAL FREE
For Individual agent users who want to learn and use controlled agent runs locally.
Use when you want the agent to follow a real process, ask for local approval, and leave replayable evidence before work counts.
- ✓Use the local FST runtime for one authority user
- ✓Run unlimited local controlled runs
- ✓Start official work from the local user or local agent
- ✓Keep local process profiles, evidence, and replay
- ✓Approve through the local CLI
- ✓Use mock or basic protected-effect preflight
Authority and features
- One user, one local machine, one agent environment, and local authority only
- Runs are started locally by the user or by an agent acting through the local FST interface
- No external event intake, shared authority, or team roles
- Local FST runtime, process profiles, MCP tools, agent skill instructions, evidence store, and replay
- Local CLI approvals, scope checks, gate checks, profile validation basics, and evidence writing
- Mock or shadow materialization and basic protected-effect preflight
- External systems need to start or update runs
- Multiple people need shared roles, shared evidence, or approval separation
or $24/mo billed annually.
PERSONAL PRO
For Power users and solo operators who want local FST connected to email, webhooks, workflow tools, tickets, files, or chat gateways.
Buy when work should begin from the outside world, but approval and protected effects still need to stay under your local authority.
- ✓Run unlimited local controlled runs
- ✓Receive webhooks, email, workflow triggers, tickets, and file events
- ✓Use a local receiver, adapter registry, signed webhooks, and source allowlists
- ✓Normalize external events into controlled run inputs and artifacts
- ✓Keep event received separate from approval granted
Authority and features
- One user, one local FST runtime, and local approval authority
- External events can create inputs, artifacts, or run triggers
- External events do not become approvals unless the profile validates identity, scope, expiry, and format
- Everything in Personal Free
- Local receiver, webhook intake, email intake, workflow-tool trigger intake, and adapter registry
- Event normalization, event-to-artifact mapping, adapter evidence, idempotency, allowlists, signed webhook support, and local adapter config
- Personal/local receiver and adapter scope
- More than one person needs authority inside the same process
- You need shared profiles, role-based approvals, or a team evidence store
or $429/mo billed annually. Includes 10 authority users.
TEAM
For Engineering, operations, support, and compliance teams that need multiple people and agents working from the same controlled process.
Buy when requesters, operators, reviewers, approvers, profile authors, and admins must be distinct roles instead of one local user.
- ✓Use 10 included authority users
- ✓Add authority users for $29/user/mo
- ✓Run unlimited shared controlled runs
- ✓Run shared controlled work in a self-hosted FST service
- ✓Route approvals by role, scope, process, and environment
- ✓Prevent people from approving their own protected effects
- ✓Publish governed profile versions for team use
- ✓Share run state, adapters, evidence, handoffs, and audit export
Authority and features
- Multiple users, multiple agents, shared runtime, shared run state, and shared evidence
- Role-bound approvals with requester, operator, reviewer, approver, profile author, profile publisher, and admin roles
- Team policy can enforce that a user cannot approve their own protected effect
- Everything in Personal Pro
- Docker or self-hosted deployment, shared run store, team process profile catalog, profile versioning, publication gates, and admin UI or API
- Shared adapters, team evidence store, run handoff, audit export, and environment separation for dev, staging, and production
- Standard evidence retention, with additional retention and environments priced separately
- FST needs to follow organization identity, central policy, retention, legal hold, or compliance rules
- Many teams or environments need governed controls from one place
Custom annual contract for governed deployment, compliance, support, and SLA.
ENTERPRISE
For Organizations that need FST inside their identity, policy, audit, retention, deployment, and compliance controls.
Buy when FST must become part of the organization control plane across teams, identities, systems, and environments.
- ✓Run unlimited controlled runs under contracted deployment terms
- ✓Bind FST authority to SSO, SCIM, IAM, directory groups, and policy
- ✓Control who can define, publish, approve, and materialize work
- ✓Separate controls by team, system, and environment
- ✓Export audit data to SIEM and compliance workflows
- ✓Retain evidence with custom retention, legal hold, and signed bundles
- ✓Run with private deployment, HA, backup, KMS options, support, and SLA
Authority and features
- Many teams, many environments, central identity, central policy, central audit, and regulated evidence
- IAM-backed roles and policy decide who can approve authority and which systems can be touched
- Environment controls decide where real materialization is allowed
- Everything in Team
- SAML or OIDC SSO, SCIM provisioning, IAM integration, directory-group mapping, org-level RBAC or ABAC, and centralized policy controls
- SIEM and log export, custom retention, legal hold, audit reports, signed evidence bundles, KMS options, private deployment, high availability, backup and restore, admin approval workflows, and enterprise support
- Contract-defined authority users, protected systems, deployments, environments, support plan, and retention terms
Safety is the baseline. Unsafe-route blocking, scope checks, evidence writing, profile validation basics, materialization preflight, replay basics, and local CLI approvals stay in the core control loop. Scale, integrations, shared authority, governance, deployment, retention, and support are the business.
Get started →See how FST complements other tools →