> ## Documentation Index
> Fetch the complete documentation index at: https://ona.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Automation guardrails

> Safety controls and policies for Automations

Guardrails keep Automations running securely and within defined boundaries. For general Ona guardrails (policies, SSO, audit logs), see [Ona Guardrails](/ona/guardrails/overview).

## Environment isolation

Each Automation runs in an isolated environment with dedicated resources. No access to other Automations or user environments. See [Environments](/ona/environments/overview).

## Command deny lists

Prevent Automations from executing dangerous commands (`sudo`, `rm -rf /`, cloud CLIs). Blocked commands fail immediately. Configure at the organization level.

See [Command deny lists](/ona/command-deny-list).

## Executable deny list

Block specific binaries from running inside Automation environments using kernel-level enforcement. Unlike command deny lists, executables are identified by content hash and cannot be bypassed by renaming.

See [Executable deny list](/ona/organizations/policies/executable-deny-list).

## Audit logging

Every execution is logged: commands, file changes, PRs created, errors. Use for debugging and compliance.

See [Audit logs](/ona/audit-logs/overview).

## Concurrency limits

Control parallel execution to manage costs and prevent Automations from running excessively. Maximum values depend on your [plan](/ona/automations/plans-and-limits).

| Limit          | Core | Enterprise |
| -------------- | ---- | ---------- |
| Max concurrent | 10   | 25         |
| Max total      | 50   | 100        |

Core plans enforce the caps listed above. Enterprise plans are unrestricted by tiering but are subject to the current system-wide ceiling of 25 concurrent and 100 total actions per Automation. [Contact sales](https://ona.com/contact/sales) if you need higher limits.

Setting values above your plan's cap returns an error. Existing Automations are not retroactively affected. Only new creates and updates are validated.

### Per-execution time limit

Each execution action can have an optional maximum duration. When set, actions that exceed this time are stopped automatically. Configure this in the Automation's action limits.

### Queue behavior

When the concurrent limit is reached, additional actions queue and start as others complete. When the total limit is reached, the Automation stops. Increase limits and re-run to process remaining targets.

## Next steps

* [Command deny lists](/ona/command-deny-list)
* [Executable deny list](/ona/organizations/policies/executable-deny-list)
* [Audit logs](/ona/audit-logs/overview)
* [Service accounts](/ona/organizations/service-accounts)