Integration guide
Security for browser-use agent workflows
browser-use helps teams build agents that interact with websites. Acira adds an external policy and enforcement path so proposed browser actions can be evaluated before execution.
01 / Integration guide
Why browser-use workflows need action controls
A browser-use agent turns model decisions and page context into browser actions. Untrusted content, sensitive credentials, and state-changing workflows make the execution boundary a critical control point.
02 / Integration guide
What to govern first
Start with domain scope, credential use, destructive actions, payments, file movement, form submissions, and script evaluation. Decide which actions are allowed, blocked, changed, or held for approval.
03 / Integration guide
Keep decisions connected to context
Supply the proposed action with relevant user, tenant, session, and target context. Acira evaluates the policy and enforces whether the action can reach the browser.
A few more details
Frequently asked questions
Can Acira be used with browser-use workflows?
Acira is designed for browser-using agent workflows, including browser-use-style automation and browser execution paths.
What should teams secure first?
Start with credentials, navigation scope, destructive actions, payments, uploads, downloads, and scripts.
Let’s map it to your stack.
Start with your workflow. Explore how Acira fits your product, platform, or infrastructure.