Self-hosted cloud platformBuilt in Bangladesh

Your own cloud, easier than Windows.

Git-based deploys, automatic TLS, managed databases, scheduled backups and host monitoring: everything production needs, in one control plane on your own infrastructure. Professional capability, with a UX you can run without knowing servers.

Active development · public roadmap 67%
deploy
  1. Push
  2. Build
  3. Verify
  4. Live
$
›
›
✓
✓
✓
●
Host healthy
CPU12%
Backup completedDaily · 03:00
TLS activeAuto-renew
10core features in production (see below)
15feature groups on the roadmap
10dashboard locales
24/7health checks and alerting

Figures as of 17 November 2026.

Features

Everything production needs, on one platform

No stitching tools together. Each feature says whether it is in production, in development, or on the roadmap.

In production

From git push to production

Push to GitHub and it builds, runs a readiness check and releases. Every deployment is kept in history, and you can roll back to any earlier one in one click.

In production

Domains and automatic TLS

Every service gets its own subdomain on wildcard DNS. Add custom domains; TLS certificates are issued and renewed automatically over ACME.

In production

Any stack

Node.js, Next.js, Vite, static sites, Dockerfiles or multi-service Docker Compose. Framework, build command and port are detected from the repository, and everything can be overridden.

Node.jsNext.jsReactViteStatic sitesPythonPHPGoDockerfileDocker ComposePostgreSQLMySQLMariaDBRedisMongoDB
In production

App catalog

One-click deploys of apps such as WordPress, n8n, Uptime Kuma and Metabase, with a check that the host has enough CPU, memory and disk before install.

In production

Managed databases

PostgreSQL, MySQL, MariaDB, Redis and MongoDB. One workspace view of health checks, disk usage, internal connection addresses and backup coverage.

In production

Backup and restore

Cron-scheduled backups with retention policies. Restore has been verified from real backups. Off-site replication is on the roadmap.

In production

Host observability

Live CPU, memory, disk, temperature and network metrics, threshold alerts and a geo request map, each reading explained in plain language.

In production

Alerting and notifications

Events for failed deploys, crash loops, services down, failed backups and expiring domains, delivered in-app or to email, Slack, Discord, Telegram or a webhook.

In production

Teams, RBAC and audit log

Workspace members with role-based access control. Instance-wide operations are limited to instance administrators, and every action is recorded in the audit log.

In production

Self-hosted CI runners

Run GitHub Actions jobs on your own servers with just-in-time, ephemeral runners that are removed when the job finishes.

In development

Preview environments

A separate preview deployment and URL for every pull request, to review changes before merge.

In development

Mail hosting

Mailboxes, aliases, inbound rules and webmail on your own domain, with SPF, DKIM and DMARC records planned for you. The mail stack images are validated in isolation.

On the roadmap

Object storage

S3-compatible object storage for files, media and backups.

On the roadmap

BDT billing, usage-based

Pay in taka through bKash, Nagad or card. Metered billing: pay for the compute and storage you use.

Architecture

Under the hood

One control plane manages build, routing, runtime, data and monitoring on your servers. Every part runs on your own infrastructure.

Control plane

REST API and dashboard. State lives in PostgreSQL; job queues run on Redis.

REST APIPostgreSQLRedisRBAC

Build pipeline

From a Git webhook to framework detection, then a Dockerfile, buildpack or static build, with a readiness check before release.

WebhooksDockerfileBuildpacksRollback

Edge

A reverse proxy routes each domain to its service, terminates TLS and renews certificates by itself.

OpenRestyACMEWildcard DNSHTTP/2

Runtime

Each service runs in its own container, with its own environment variables, secrets and persistent volumes.

DockerComposeVolumesSecrets

Data and backups

Managed databases, scheduled dumps, retention policies and verified restores.

pg_dumpRetentionRestoreCron

Automation

Everything is available through the API, plus a CLI and an MCP server for AI agents.

CLIMCPWebhooksAudit log

Workflow

From repository to production in four steps

  1. shop-frontendmain
    billing-apimain
    GitHub Appconnected

    Step 1

    Connect GitHub

    Install the GitHub App and your repositories appear in the dashboard, with push webhooks set up for you.

  2. frameworkNext.js
    buildnpm run build
    output.next
    port3000

    Step 2

    Import a repository

    Framework, build command, output directory and port are detected. In a monorepo, each app becomes its own service.

  3. buildverifytls
    shop.apps.sifat.cloud

    Step 3

    Deploy

    Build, health check, then subdomain and TLS. Every later push goes to production by itself.

  4. backup ok · 03:00

    Step 4

    Operate

    Scheduled backups, metrics, alerts and an audit log. If something goes wrong, roll back to an earlier deployment in one click.

Product principle

Professional power, simple to use

Our core goal: nothing a professional expects is left out, yet someone who has never run a server can use it as easily as a home computer.

Explanations, not jargon

Beside a raw error code: what happened, and why, in plain language.

Metrics with context

CPU at 90% comes with whether it matters and what to do about it.

Actionable diagnostics

When a deploy fails, the missing environment variable or dependency is shown before you dig through logs.

Safe by default

Destructive actions such as a server restart or delete require typing the name to confirm, and all of it goes in the audit log.

For Bangladesh

Cloud hosting without a dollar card

Foreign cloud providers need a USD card, bills move with the exchange rate, and support works in another time zone. Sifat.cloud sets out to remove these barriers.

The problem today

  • Foreign providers need a USD card that many people do not have
  • When the exchange rate rises, the monthly bill rises with it
  • Running production servers takes a lot of DevOps knowledge
  • Support works in another country's time zone, in English

What Sifat.cloud will offer

  • Pay in taka: bKash, Nagad and cards
  • Prices fixed in BDT, unaffected by the exchange rate
  • A dashboard you can run without DevOps knowledge
  • The dashboard in Bengali, with local support

Billing and the hosting service are not open yet; they open once the platform is stable.

Plans

Three kinds of service, coming soon

Pricing is not set yet. Every plan will be billed in taka.

Coming soon

Web hosting

Portfolios, business websites, small projects

৳—
  • Custom domain and TLS
  • Deploy from GitHub
  • Daily backups
  • Mail hosting (coming)
Coming soon

VPS

When you need dedicated resources

৳—
  • Dedicated vCPU, memory and disk
  • The same dashboard
  • Monitoring and alerting
  • Self-hosted CI runners

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.

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

Last updated: 17 November 2026

FAQ

Questions you may have

What is Sifat.cloud?

A self-hosted platform for deploying applications and managing databases, domains, backups and monitoring from one dashboard, on your own servers, without a command line.

Can I use it now?

The platform runs in production every day, and several of our own sites run on it. Public sign-up and billing are not open yet; the roadmap shows what is coming and when.

How will payment work?

The plan is payment in taka through bKash, Nagad and cards, so no USD card is needed. This is still in development.

What does usage-based billing mean?

Instead of renting a whole server, you pay only for the CPU, memory and storage your application uses, so small projects cost less.

Where will my data be?

Applications and databases run on our infrastructure. They are backed up daily, and you manage backups and restores yourself from the dashboard.

Which stacks are supported?

Node.js, Next.js, React, Vite, static sites, Python, PHP, Go, Dockerfiles and Docker Compose. Databases: PostgreSQL, MySQL, MariaDB, Redis and MongoDB.

Is there an API?

Yes. Everything is available through a REST API, plus a CLI and an MCP server for AI agents.

Will it be open source?

Yes, that is the plan. It will be released once the platform is stable.

Want to hear firstwhen it launches?

Follow every phase on the public roadmap. Anything new that reaches production is added there.

View the roadmap