30 jours d'essai gratuit, risques IA générative :Commencer
Aller au contenu principal

AI security deployment

Choose backend hosting and prompt processing independently.

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

Backend hostingCustomer cloudOn-premisesAona-managed
Prompt processingUser deviceYour environmentAona-managed

Confirm the supported feature and integration combination for the required configuration.

Deployment choices

Backend hosting and prompt processing are not the same choice.

01

Place the backend

Consider customer cloud, on-premises, or Aona-managed backend hosting.

02

Place prompt processing

Consider user-device, customer-environment, or Aona-managed prompt processing.

03

Validate the combination

Confirm the required features, integrations, and managed client route for the intended configuration before rollout.

Architecture review

A configuration discussion, not a reference architecture

A security architect may prefer customer-cloud backend hosting while evaluating user-device prompt processing. The combination needs feature and integration confirmation.

Independent placement

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

Deployment questions to resolve before a pilot.

Do all combinations have the same capability?

No. Do not assume feature or integration parity across every combination or deployment. Confirm the supported configuration for the required features.

Does this determine third-party AI processing?

No. Aona’s placement does not determine a third-party AI provider’s processing or residency. Confirm that separately with the provider and contract.

Can we deploy without endpoint or browser changes?

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.

Does backend hosting determine where prompts are processed?

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.

Can we host the backend in our environment and process prompts at the edge?

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.

Who owns pilot acceptance and recovery?

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.

Is macOS managed installation available?

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.

What should the pilot prove?

A real managed-install path, representative synthetic actions, acceptance evidence, employee notice, operational ownership, and tested recovery or rollback expectations.

Focused evaluation

Bring one real decision. Leave with the next validation step.

We’ll keep the discussion to your intended workflow, data categories and technical boundaries.

Book a focused demo
Workforce AI Security Deployment: Requirements and Pilot Plan | Aona