Roadmap

Public roadmap

Sifat.cloud is in active development. The state of every phase and deliverable is shown here openly, and updated after each notable release.

Last updated: 17 November 2026

DoneIn progressTo do
67%Complete
1Self-hosted foundation and CI/CD100%
2Dashboard and Git-based deploys93%
3Configuration, CLI and mail stack71%
4Data, reliability and observability58%
5Codebase consolidation13%

How it is counted: completed deliverables count in full, deliverables in progress count as half. The total is the average of the five phases.

The five phases

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.

100%

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.

93%

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.

71%

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.

58%

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.

13%

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

Next

Next goal: managed hosting in Bangladesh

Once the platform is stable, it will power a hosting service for Bangladesh, billed in taka.

  • BDT payments: bKash, Nagad and cards
  • Usage-based metered billing
  • Managed web hosting plans
  • VPS plans
  • Public self-service sign-up
  • Bengali locale for the dashboard
  • Open source release

Recent releases

    • Company website and public progress page (about.sifat.cloud)
    • The "sifat." brand identity across the dashboard
    • Live data in the backup policy overview and Logs view
    • Deploy diagnostics: secret generation and crash cause detection
    • A read-only Admin view for instance administrators
    • Security review: findings fixed and deployed
    • Scheduled backups on, restore verified
    • Database workspace with health checks and disk usage
    • Automatic subdomains for every new service
    • Event notifications switched on
    • Control plane fully self-hosted
    • New design system and authentication screens
    • Host observability page redesigned