Place the backend
Consider customer cloud, on-premises, or Aona-managed backend hosting.
AI security deployment
Aona offers separate choices for backend hosting and prompt processing. Bring the locations, managed client routes, and required features so the configuration can be validated together.
Two independent decisions
Confirm the supported feature and integration combination for the required configuration.
Deployment choices
Consider customer cloud, on-premises, or Aona-managed backend hosting.
Consider user-device, customer-environment, or Aona-managed prompt processing.
Confirm the required features, integrations, and managed client route for the intended configuration before rollout.
Architecture review
A security architect may prefer customer-cloud backend hosting while evaluating user-device prompt processing. The combination needs feature and integration confirmation.
Backend: customer cloud
Prompt processing: user device
Illustrative selection, not a feature-parity claim.Pilot input
Bring required locations, client routes and integrations; they are the inputs to configuration validation, not selectable product controls.
Buyer questions
No. Do not assume feature or integration parity across every combination or deployment. Confirm the supported configuration for the required features.
No. Aona’s placement does not determine a third-party AI provider’s processing or residency. Confirm that separately with the provider and contract.
No. Aona enforces on the device, so it needs the browser plugin or the endpoint app on managed devices. That is also why it does not depend on network routing changes: nothing changes in the SSE, DNS or Microsoft 365.
No. Backend hosting and prompt processing are separate choices. Confirm the supported configuration, feature and integration availability, retention, and telemetry rather than assuming every combination behaves identically.
That is a configuration to validate, not an automatic pairing. Record the proposed backend host and user-device prompt-processing choice separately, then confirm the required feature, integration, and client path.
Name an operational owner before testing. Agree the synthetic actions, evidence to review, employee notice, support route, update checks, and rollback or recovery expectations before the cohort expands.
IT teams can deploy the Aona endpoint app on Windows and macOS with their preferred software deployment tools. Intune is one option; direct installation is also available on both platforms.
A real managed-install path, representative synthetic actions, acceptance evidence, employee notice, operational ownership, and tested recovery or rollback expectations.
Focused evaluation
We’ll keep the discussion to your intended workflow, data categories and technical boundaries.
Book a focused demo