Phase 1
Done
Self-hosted foundation and CI/CD
The whole control plane runs on our own infrastructure, and every change on main is built, verified and released automatically.
3 of 3 done
- Control plane runs entirely on our own infrastructure, with no external SaaS dependency
- Continuous deployment: build, health check and automatic rollback on failure
- Container images built and stored on our own servers
Phase 2
In progress
Dashboard and Git-based deploys
A new dashboard design, and a complete pipeline from a GitHub push to production over HTTPS.
6 of 7 done
- Design system with light and dark themes
- New authentication screens and the "sifat." brand identity
- Production deploys from a GitHub push, with TLS
- Automatic per-service subdomains on wildcard DNS
- Host observability: CPU, temperature, network and a geo request map
- Security review, with its findings fixed
- Final UX review of the whole dashboard
Phase 3
In progress
Configuration, CLI and mail stack
Declarative deploy config, environment conventions, a CLI and our mail stack, all under one brand.
4 of 7 done
- Consistent branding across the UI, in 10 locales
- Declarative deploy config: sifat.json
- SIFAT_ environment variables and the sifat CLI
- Self-hosted CI runners (sifat label) and .sifat/workflows
- Mail stack images: built and validated in isolation, not yet in production
- Company website and public progress page
- Mail service rollout, staged on a subdomain first
Phase 4
In progress
Data, reliability and observability
Managed databases, backup and restore, preview environments, storage and logging, each working for real in production.
6 of 12 done
- Database workspace: every database, its health check and disk usage
- Scheduled backups with retention policies
- Restore verified from real backups
- Workspace-wide backup policy overview
- Event notifications: failed deploys, services down, failed backups
- Deploy diagnostics: secret generation and crash cause detection
- Pull request preview environments: implemented, GitHub App permission pending
- Failed build alerts in the dashboard
- Off-site backup replication
- Staging environments
- S3-compatible object storage
- Centralised logging and distributed tracing
Phase 5
In progress
Codebase consolidation
One naming scheme and set of conventions across code, containers and data, each migration with a backup and a rollback plan.
0 of 4 done
- Consistent internal naming across the codebase
- Standard Docker labels and container naming
- Database data migrations with backup and rollback
- Standard server-side directory layout