Prompt and file coverage varies by site and input path.
AI website · supported path•••
EMPLOYEE PROMPT
Draft a renewal note for Maya Patel. Account 481-209.
Aona policy check
A checkpoint before sending.
Review a sensitive-data rule on this supported submission path.
Text and identifiers ready for evaluation
Inside the browser interaction
InputCheckResponse
Synthetic illustration · no prompt is sent.
Example ready. No prompt is sent.
Protect AI use in the browser where the plugin is installed.
COMPARE THE THREE PRODUCTS
Different entry points. A clearer decision.
You can combine products. Match each one to an AI use case, then verify the coverage that matters to you.
Browser plugin, Windows/macOS apps and APIs: coverage, advantages, things to consider and rollout.
Your decision
Browser plugin
Windows / macOS apps
APIs
Best fit
Employees using AI websites
Managed computers using native AI
Teams building an AI integration
Platforms & scope
Google Chrome · Microsoft Edge · SafariPolicy checks for supported prompts and file uploads in ChatGPT, Claude, Gemini and Copilot / Bing web experiences.
Windows x64 · macOS · Apple SiliconCoverage for supported browser and native AI apps, with local AI-agent visibility.
Your applications · Scripts & agents · Backend workflowsCalls explicitly integrated with Aona evaluation APIs. Your application receives the verdict and applies the resulting decision.
Advantages
Policy feedback inside the AI page
Prompt checks and supported file redaction
Focused rollout for browser-based AI use
Coverage beyond browser-only interactions
Device-level protection for supported AI traffic
Local agent and MCP visibility, available in selected rollouts
Choose the checkpoint in your own workflow
Evaluate text and supported files
Use returned verdicts and redactions in your application
Things to consider
Browser-focused protection; add desktop apps for wider coverage
Install the plugin in each browser you use
More setup than a browser plugin
Coverage varies by app and operating system
Developer integration and response handling
Applies to workflows your application sends to Aona
Evaluation and activity reporting are separate
Rollout
Install the extension in Chrome, Edge or Safari.
Roll out on Windows and macOS with your IT team’s preferred software deployment tools, or install directly.
Connect the evaluation call and implement the response handling.
Browser plugin
Employees using AI websites
Google Chrome · Microsoft Edge · Safari
Policy checks for supported prompts and file uploads in ChatGPT, Claude, Gemini and Copilot / Bing web experiences.
Advantages
Policy feedback inside the AI page
Prompt checks and supported file redaction
Focused rollout for browser-based AI use
Things to consider
Browser-focused protection; add desktop apps for wider coverage
Install the plugin in each browser you use
Rollout details
Install the extension in Chrome, Edge or Safari.
Windows / macOS apps
Managed computers using native AI
Windows x64 · macOS · Apple Silicon
Coverage for supported browser and native AI apps, with local AI-agent visibility.
Advantages
Coverage beyond browser-only interactions
Device-level protection for supported AI traffic
Local agent and MCP visibility, available in selected rollouts
Things to consider
More setup than a browser plugin
Coverage varies by app and operating system
Rollout details
Roll out on Windows and macOS with your IT team’s preferred software deployment tools, or install directly.
APIs
Teams building an AI integration
Your applications · Scripts & agents · Backend workflows
Calls explicitly integrated with Aona evaluation APIs. Your application receives the verdict and applies the resulting decision.
Advantages
Choose the checkpoint in your own workflow
Evaluate text and supported files
Use returned verdicts and redactions in your application
Things to consider
Developer integration and response handling
Applies to workflows your application sends to Aona
Evaluation and activity reporting are separate
Rollout details
Connect the evaluation call and implement the response handling.
Choose coverage around the apps, devices and AI activity your team uses.
ONE ORGANISATION. DIFFERENT PATHS.
You don’t have to choose only one.
A browser-based team, a native AI application and an internal agent can need different control points.
For reporting integrations, not prompt evaluation instructions.
Which Aona product should we start with?
Start with the workflow you need to protect. Choose the browser plugin for supported AI websites in Chrome, Edge or Safari, the Windows/macOS app for supported desktop traffic, or APIs when your team owns the application checkpoint. A mixed environment may need more than one product. Validate a representative prompt or file before expanding the rollout.
Can the browser plugin and desktop app run together?
Yes. They are separate endpoint products designed to run together. Supported coordinated paths mark requests already processed by the plugin so the native app can avoid processing them again. Confirm this behavior with the client versions and specific request path in your rollout.
Which AI platforms can the desktop app secure?
The desktop app protects supported workflows across browser and native AI applications. Coverage varies by app, action and operating system. We’ll help map your team’s tools to the right setup. Local agent and MCP visibility is available in selected rollouts.
Does an API integration automatically block unsafe AI calls?
No. Framework and guardrail APIs evaluate submitted text; framework APIs also check supported files. Your application must apply the verdict, use any returned redaction, and decide how to handle timeouts or errors before continuing. Calls that bypass your integration are not covered. These stateless evaluation endpoints do not automatically record an analytics event.
Are policy evaluation APIs the same as the event API and webhooks?
No. Evaluation APIs check supplied text against a framework or guardrail, or supported files against a framework. The event API and outbound webhooks deliver existing security-event evidence to your systems. Reading events or receiving a webhook does not, by itself, intercept or block an AI request.
Which browsers and operating systems are supported?
The browser plugin supports Chrome, Edge, Firefox and Safari. Desktop apps are available for Windows x64 and Apple Silicon Macs. Prompt and file coverage varies by AI application and workflow. For custom applications, APIs add policy checks to the workflows you integrate.
Can Aona run in our cloud or on-premises?
Yes. Aona backend hosting can use your cloud, your on-premises environment or Aona-managed servers. Separately, prompt processing can run on the user device (edge), in your cloud or on-premises, or on Aona-managed servers. Confirm the supported feature and integration configuration; the options do not imply identical capabilities everywhere. A third-party AI provider's processing remains a separate consideration.
A DEMO BUILT AROUND YOUR SECURITY NEEDS
Bring one AI use case. Find your fit.
Tell us the AI tool, the device and the action you want to protect. Compare the right product and see what needs validating.
