Question 1

Will Acira replace any part of our existing stack?

Accepted Answer

No. Acira is designed to work with your existing model, agent framework, orchestrator, interface, and browser stack. You connect it to the action points you want to protect.

Question 2

Does Acira actually stop actions, or only return a decision?

Accepted Answer

Acira evaluates the policy and enforces what happens at each connected action point. It allows the action, holds it for approval, or blocks it before browser execution.

Question 3

What happens if the model ignores its prompt or instructions?

Accepted Answer

Acira sits outside the model. At every action point connected to Acira, the proposed browser action is checked against policy before it continues, so enforcement does not depend on the model remembering or following an instruction.

Question 4

What kinds of browser actions can we protect?

Accepted Answer

Depending on the integration, Acira can protect navigation, clicks, typing, form submissions, uploads, downloads, credential use, messages, purchases, deletions, and account changes. General policies cover shared risks, while specific policies protect exact pages, controls, or workflows.

Question 5

Can each customer have its own policies and approval rules?

Accepted Answer

Yes. Acira is designed for customer-defined controls. Each customer can decide which actions are allowed, blocked, or sent for approval, while those controls remain inside your product experience.

Question 6

Can OEMs and ISVs run Acira entirely on-premises?

Accepted Answer

Yes. For OEM and ISV integrations, Acira runs on-premises, completely within your or your customer's deployment. Policy evaluation and enforcement stay local, so browser-action context does not need to go to an Acira-hosted service for those decisions. Your agent's connections to models, websites, and approval tools remain part of your own architecture.

Question 7

Is Acira for software vendors or teams running their own agents?

Accepted Answer

Both. OEMs and ISVs embed Acira in products they sell, giving their customers policy and approval controls inside their own product and brand. Internal teams use Acira to govern their organization's agents, workflows, and reviewers. The distinction is who sets the policies and who uses the controls.

Question 8

Can we start with one workflow and expand later?

Accepted Answer

Yes. You can begin with the action points that matter most, attach the relevant policies, and add more protected actions and workflows as your product grows.

Question 9

Can Acira stay inside our product and brand?

Accepted Answer

Yes. Acira is built for embedded integrations, so policies, approvals, and security controls can remain part of your product and customer experience.

Time	Action	Decision	Details
10:18:42		Needs approval
Matched policy Ask before sending emails Agent / run Hermes · R-2481 Target Account handoff summary Sending the message requires your approval. The action is paused before the email leaves Outlook.
10:16:11		Blocked
Matched policy Block destructive actions Agent / run Hermes · R-2481 Target Original handoff message The policy prevents deleting emails. Acira stopped the action before the message was removed.
10:15:28		Allowed
Matched policy Chrome access Agent / run Hermes · R-2481 Target Customer account history Reading the account notes is permitted within this agent’s configured browser access.
10:14:36		Allowed
Matched policy Chrome access Agent / run Hermes · R-2481 Target Customer record Opening this page is within the agent’s allowed browser scope.
10:14:02		Allowed
Matched policy Outlook access Agent / run Hermes · R-2481 Target Account handoff thread The email is within the agent’s permitted Outlook access.
10:12:19		Allowed
Matched policy Slack access Agent / run Claude · R-2480 Target Research summary Sharing this summary in the approved team channel is permitted by the agent’s Slack access policy.
10:11:06		Blocked
Matched policy Block destructive actions Agent / run Claude · R-2480 Target Research documents The deletion policy protects this folder. Acira blocked the action before any files were removed.
10:10:24		Allowed
Matched policy File Explorer access Agent / run Claude · R-2480 Target Research brief Reading this document is within the agent’s configured file access.

Control what youragents can do.

Set the boundaries for your agent.

Control purchases

Protect your sign-ins

Control what gets shared

Prevent unwanted deletions

Put a rule on any action.

Every action follows your rules.

Allow

Ask for approval

Block

Test your rules before a live run.

Every action. A clear record.

Make Acira part of your setup.

Frequently asked questions