Skip to main content

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

GoalRead
Select SaaS or a customer-controlled environmentDeployment Models
Prepare and validate a customer-controlled Azure environmentAzure Deployment Guide
Understand the platform service boundariesReference Architecture and Runtime Services
Review network and service authenticationNetwork Security and Identity and Access
Prepare configuration and credentialsSecrets and Configuration
Plan logs, alerts, and external accessObservability and Firewall and Egress
Review repeatable provisioningInfrastructure as Code
Run a customer implementationDeployment Lifecycle and Rollout and Handover
Review third-party componentsOpen-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.