Place the backend
Consider customer cloud, on-premises or Aona-managed backend hosting.
AI security deployment
Choose backend hosting and prompt processing independently.
Aona offers separate choices for backend hosting and prompt processing. Bring the locations, client routes and required features so the architecture 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.
Place prompt processing
Consider user-device, customer-environment or Aona-managed prompt processing.
Validate the combination
Confirm the required features and integrations 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.
Does one choice determine the other?
No. Backend hosting does not by itself determine prompt-processing placement, and prompt-processing placement does not determine backend hosting.
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?
Do not assume so. The applicable path needs managed browser or endpoint deployment and must be scoped for your environment.
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.
Is macOS managed installation available?
Mac MDM was not shipped at last product verification. Confirm current status before committing a macOS rollout plan.
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