Deployment and Operations
This section describes the customer-safe deployment and operating model for Siesta AI. It covers architecture, identity, networking, secrets, monitoring, infrastructure as code, rollout, and handover without exposing production resource names, credentials, private addresses, or customer-specific topology.
Choose a Path
| Goal | Read |
|---|---|
| Select SaaS or a customer-controlled environment | Deployment Models |
| Prepare and validate a customer-controlled Azure environment | Azure Deployment Guide |
| Understand the platform service boundaries | Reference Architecture and Runtime Services |
| Review network and service authentication | Network Security and Identity and Access |
| Prepare configuration and credentials | Secrets and Configuration |
| Plan logs, alerts, and external access | Observability and Firewall and Egress |
| Review repeatable provisioning | Infrastructure as Code |
| Run a customer implementation | Deployment Lifecycle and Rollout and Handover |
| Review third-party components | Open-Source Licenses |
Documentation Boundaries
Public documentation explains architecture and required controls. Customer handover documentation may additionally contain approved resource inventories, endpoints, owners, operational thresholds, and environment-specific runbooks. Exact network ranges, secret names, firewall destinations, internal identifiers, and recovery targets belong in access-controlled customer or engineering documentation.