Operations
The Delphi platform deploys as nine services plus a bastion host, each running on its own cloud instance. Each service has its own operations page covering runbook, configuration, and troubleshooting in tabs.
For first-boot mechanics (init.sh, S3 config sync, fetch-env.sh, and Docker Compose startup), use Bootstrap and init. This section starts once hosts exist and you need to operate or debug a specific role.
Instance vCPU and RAM are in Provision instances.
The generic docs describe the service roles and optional containers that can appear in a Delphi deployment. A customer's exact container inventory comes from the generated deployment configuration, enabled feature flags, image tag, and generated Docker Compose files. Use Release compatibility to see which service roles changed in each release; keep the customer-specific inventory with the deployment handover or runbook.
Use the cards below as the central firewall checklist by service role. They intentionally stay high-level; per-container ports and env variables live on each service page. TelPro entries marked webrtc apply only when the Featurewebrtc flag is enabled. In this platform release, those TelPro WebRTC entries are the only feature-flagged port requirements; the other flags change containers, env, or UI surfaces without adding public firewall rules.
Service grid
TelPro
Public-facing telephony and WebRTC gateway. Single instance, static IP.
Voice
Asterisk PBX plus the AI conversation engine. Horizontally scalable.
API
TelAPI HTTP/WebSocket server. Multiple instances behind a managed load balancer with sticky sessions.
Web
TelWeb management dashboard behind Caddy with automatic Let's Encrypt HTTPS. Also reverse-proxies SigNoz.
Database
Central Postgres and Redis with attached block storage at /mnt/data. Single instance; data
survives instance recreation via volume reattach.
Media
Private TTS media cache. HTTPS at static private IP 10.0.1.30. Stores generated audio for TelPhi
/ TelAPI reuse.
Ops
Scaler autoscales Voice and API instances. Tasker runs background jobs, cron, DB backups, and email notifications.
SigNoz
Observability backend on static private IP 10.0.1.10. Receives traces, metrics, and logs from
every service.
Squid
HTTP/HTTPS proxy for every private-network instance. First service to deploy.
See also
- Instance and container debugging — shared SSH / Docker / collector checks when telemetry is missing.
- Getting started — bring up a brand-new deployment from zero.
- Configuration model — bootstrap env, SSM, Secrets Manager, vars.yaml, fetch-env.sh.
- Third-party version sources — pinned upstream versions (Kamailio, Asterisk, Postgres, OTel, etc.) and where they're declared.
- Release compatibility — which Delphi releases are current and which services changed in each.
- Monitoring in SigNoz — dashboards, alerts, SIP capture, trace IDs, and call-ID correlation.