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.
Self-hosted cloud platform·Built in Bangladesh
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%Figures as of 17 November 2026.
Features
No stitching tools together. Each feature says whether it is in production, in development, or on the roadmap.
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.
Every service gets its own subdomain on wildcard DNS. Add custom domains; TLS certificates are issued and renewed automatically over ACME.
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.
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.
PostgreSQL, MySQL, MariaDB, Redis and MongoDB. One workspace view of health checks, disk usage, internal connection addresses and backup coverage.
Cron-scheduled backups with retention policies. Restore has been verified from real backups. Off-site replication is on the roadmap.
Live CPU, memory, disk, temperature and network metrics, threshold alerts and a geo request map, each reading explained in plain language.
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.
Workspace members with role-based access control. Instance-wide operations are limited to instance administrators, and every action is recorded in the audit log.
Run GitHub Actions jobs on your own servers with just-in-time, ephemeral runners that are removed when the job finishes.
A separate preview deployment and URL for every pull request, to review changes before merge.
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.
S3-compatible object storage for files, media and backups.
Pay in taka through bKash, Nagad or card. Metered billing: pay for the compute and storage you use.
Architecture
One control plane manages build, routing, runtime, data and monitoring on your servers. Every part runs on your own infrastructure.
REST API and dashboard. State lives in PostgreSQL; job queues run on Redis.
From a Git webhook to framework detection, then a Dockerfile, buildpack or static build, with a readiness check before release.
A reverse proxy routes each domain to its service, terminates TLS and renews certificates by itself.
Each service runs in its own container, with its own environment variables, secrets and persistent volumes.
Managed databases, scheduled dumps, retention policies and verified restores.
Everything is available through the API, plus a CLI and an MCP server for AI agents.
Workflow
Step 1
Install the GitHub App and your repositories appear in the dashboard, with push webhooks set up for you.
Step 2
Framework, build command, output directory and port are detected. In a monorepo, each app becomes its own service.
Step 3
Build, health check, then subdomain and TLS. Every later push goes to production by itself.
Step 4
Scheduled backups, metrics, alerts and an audit log. If something goes wrong, roll back to an earlier deployment in one click.
Product principle
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.
Beside a raw error code: what happened, and why, in plain language.
CPU at 90% comes with whether it matters and what to do about it.
When a deploy fails, the missing environment variable or dependency is shown before you dig through logs.
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
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.
Billing and the hosting service are not open yet; they open once the platform is stable.
Plans
Pricing is not set yet. Every plan will be billed in taka.
Portfolios, business websites, small projects
Apps, APIs and startups
When you need dedicated resources
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
FAQ
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.
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.
The plan is payment in taka through bKash, Nagad and cards, so no USD card is needed. This is still in development.
Instead of renting a whole server, you pay only for the CPU, memory and storage your application uses, so small projects cost less.
Applications and databases run on our infrastructure. They are backed up daily, and you manage backups and restores yourself from the dashboard.
Node.js, Next.js, React, Vite, static sites, Python, PHP, Go, Dockerfiles and Docker Compose. Databases: PostgreSQL, MySQL, MariaDB, Redis and MongoDB.
Yes. Everything is available through a REST API, plus a CLI and an MCP server for AI agents.
Yes, that is the plan. It will be released once the platform is stable.
Follow every phase on the public roadmap. Anything new that reaches production is added there.
View the roadmap