On this page

• Core Capabilities
• Architecture
• Primary Users
• Deployment
• Links

Orcta Runtime

A pull-based deployment automation platform that manages multi-app Docker Compose deployments with health verification, auto-rollback, and automatic TLS routing.

Core Capabilities

• Multi-App Management — Register multiple apps with independent compose directories, health endpoints, and Caddy domains.
• Pull-Based Deploys — CI pushes to GHCR → webhook fires → Orcta pulls and deploys via docker compose.
• Health Verification — TCP/HTTP checks after deploy with auto-rollback to last known healthy SHA on failure.
• Caddy Integration — Auto-registers reverse proxy routes with TLS on successful deploy.
• Pre/Post-Deploy Hooks — Blocking gates (e.g., run migrations before deploy) and async notifications (Slack, Discord, custom webhooks).
• Role-Based Auth — Admin/operator/viewer API tokens + GitHub OAuth with org membership gating.
• React Dashboard — Monitor executions, manage apps, hooks, and cron schedules.
• Cron Scheduling — Schedule recurring actions (backups, maintenance tasks).

Architecture

GitHub Actions → GHCR → Webhook → Orcta Runtime → docker compose pull && up -d → Caddy Route
                                                  ↓
                                            Health Check → Pass / Rollback

Key decisions:

• Pull-based model (not push) — Orcta pulls images, CI doesn’t SSH into servers.
• Per-app mutex locks prevent concurrent deploys to the same app.
• Auto-rollback uses ${DEPLOY_SHA:-latest} in compose image tags.
• Caddy admin API at localhost:2019 for automatic route management.

Primary Users

• Engineering team deploying microservices to shared VPS.
• CI/CD pipelines triggering deploys via GitHub webhooks.
• Operations monitoring deploy health and rollback status.

Deployment

Orcta Runtime runs as a Docker container on the VPS:

# Deploy
docker compose pull && docker compose up -d

# Dashboard
https://runtime.orctatech.com

Links

• GitHub Repository
• Dashboard
• API Reference