# Deploy and operate BullSequana AI (/docs/get-started/deploy-and-operate)



This path is for platform engineers, infrastructure operators, deployment engineers, and SREs responsible for an installation.

## Outcome [#outcome]

You can prepare a target environment, deploy through the supported configuration path, validate the platform, establish operational ownership, and recover or roll back safely.

## 1. Choose the deployment model [#1-choose-the-deployment-model]

[Deployment options](/docs/deployment/deployment-options) explains the supported infrastructure shapes and responsibility boundaries. Record which team owns Kubernetes, networking, DNS, certificates, registry delivery, storage, identity, and accelerators.

## 2. Establish environment context [#2-establish-environment-context]

Use [Before you start](/docs/deployment/setup-context) to capture the target domain, cluster, registry, network, identity, and access assumptions. Select the relevant [environment guide](/docs/deployment/environments) before applying generic configuration.

## 3. Validate prerequisites [#3-validate-prerequisites]

Complete [Prerequisites](/docs/deployment/prerequirements) as evidence, not as a reading exercise. Each required dependency should have an owner, a validation method, and an escalation path. Confirm [minimum requirements](/docs/deployment/minimum-requirements) against the intended workload rather than the cluster total alone.

## 4. Configure and deploy [#4-configure-and-deploy]

Understand the [configuration model](/docs/deployment/configuration-model), then follow the [deployment sequence](/docs/deployment/playbooks/deployment-sequence). Use the supported [GitOps workflow](/docs/deployment/gitops-workflow) and [Platform CLI](/docs/deployment/platform-cli) so the desired state remains reviewable and repeatable.

## 5. Verify service readiness [#5-verify-service-readiness]

Do not stop at healthy Kubernetes workloads. Verify:

* reconciliation completes without persistent failures
* ingress, DNS, certificates, and identity work from a client path
* storage and databases persist expected state
* an authorized user can reach the Portal
* an authorized application can make a BSQAI API request
* metrics, logs, traces, and dashboards are populated
* tenant isolation is preserved

## 6. Establish operations [#6-establish-operations]

Assign ownership for incidents, capacity, tenant administration, security review, upgrades, backups, and service communication. Use [Administration and operations](/docs/administration) and [Troubleshooting](/docs/troubleshooting) to turn technical checks into a repeatable operating model.

## 7. Prepare change and recovery [#7-prepare-change-and-recovery]

Use [Upgrade and release process](/docs/deployment/playbooks/upgrade-and-release-process) for compatibility and rollout decisions. Use [Backup and disaster recovery](/docs/deployment/playbooks/backup-and-disaster-recovery) to define what is protected, how restoration is validated, and when rollback becomes recovery.

## You are done when [#you-are-done-when]

* the deployment is reproducible from reviewed configuration
* user and application acceptance paths succeed
* monitoring and incident ownership are active
* capacity and backup assumptions are documented
* rollback and recovery have explicit decision points