Amazon Q Business is AWS's managed, permissions-aware assistant over company data, now closed to new customers in favor of Amazon Quick. Pages here cover replacing it with a self-hosted assistant such as Onyx.
Moving an Amazon Q Business application to self-hosted Onyx: inventorying data sources and plugins with the AWS CLI, reconnecting S3, SharePoint, Confluence and Salesforce with Onyx permission sync, choosing models, and replacing Q Apps and guardrails.
Comparing Amazon Q Business with Onyx: permission-aware retrieval, connectors, identity through IAM Identity Center against Onyx SSO and SCIM, model choice, a frozen AWS feature set against an actively developed open-source project, and operating effort.
Cost of ownership by component: Lite and Pro subscriptions and Starter or Enterprise index unit-hours, against Onyx on your own infrastructure with its index, database and model serving, GPU or API model costs, support and staff time.
AWS now offers only fixes for Q Business and points customers to Amazon Quick, whose index bridge drops Q Apps, Actions and guardrails and can flatten permissions. This page compares that path with moving to a self-hosted Onyx deployment you control.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.