Home · About · Services · Industries · Projects · Products · Process · Blog · FAQ · Contact
Private cloud and self-hosting setup on servers you control. Private cloud and self-hosting setup on your own VPS or hardware: Dokploy deploys, MinIO storage, Tailscale private networking, backups and dev/test clouds.
Private cloud and self-hosting setup means running your apps, files and test environments on servers you own or rent, instead of on platforms that bill per build, seat or gigabyte. We install a deployment panel so developers ship without SSH, S3-compatible storage for files, a private network that keeps databases and admin tools off the public internet, and on-demand VMs for development and testing. We run the same kind of setup for our own work, so we know where it breaks.
Why teams ask us to set this up. Managed platform bills grew faster than usage A handful of small apps, staging copies and preview environments now cost more each month than the servers they would need.
Data has to stay on your infrastructure A client or internal policy says documents and databases must live on servers you control, not in a third-party service.
Admin tools are exposed to the internet Database ports, dashboards and SSH are open to the world because there was no simple private network to put them behind.
Dev and test environments are a queue Developers wait for someone to create a VM or share one machine, so testing happens late and environments drift.
What we set up. Deployment platform Dokploy on a VPS with Traefik routing and Let's Encrypt certificates, Git-based autodeploy, and separate projects for production and staging.
Object storage S3-compatible storage for uploads and documents, with per-application credentials and presigned URLs. MinIO community edition no longer ships official binaries or images, so we compare it with Garage or SeaweedFS for each project.
Private networking A Tailscale tailnet with access rules, and subnet routers where installing an agent on every machine is not practical.
Private dev and test cloud Isolated Ubuntu VMs on your own hardware with Multipass or similar, private DNS and a simple web panel to create and reset them.
Domains and TLS Many domains and subdomains served from one entry point, with automatic or wildcard certificates and readable routing configuration.
Databases on your servers PostgreSQL, MongoDB and Redis reachable only over the private network or from approved IP addresses.
Backups and restore tests Scheduled database and file backups copied off the server, with restores tested on a schedule rather than assumed.
Hardening and hand-over Key-only SSH, firewall rules, automatic security updates, monitoring, and runbooks stored in your repository.
Engagement options Self-hosting setup A fixed-scope project to move a set of apps onto your own servers, then run them in-house.
Review of current hosting and costs Dokploy, storage and networking set up Apps migrated and switched over Runbooks and a hand-over session Private dev cloud A fixed-scope build of a development and test cloud on hardware you already own.
VM provisioning on Linux or Windows hosts Tailscale access and private DNS Web panel to create and reset VMs Documentation for your team Managed self-hosting A monthly retainer where we keep the platform patched, backed up and monitored.
Updates to the OS, Dokploy and services Monitoring, alerts and incident response Backup checks and restore tests Coverage hours and response times agreed in the retainer How it works Inventory and fit check We list what you run, where data lives and what it costs, and tell you plainly which workloads should stay on a managed service.
Design and proposal A written design covering servers, network, storage, backups and access, with a fixed-scope proposal and order of work.
Build next to what you have The new platform is built on staging first, apps are moved one at a time, and DNS is switched only once each one is proven.
Hand over or run it You get the documentation and a hand-over session, or we keep it running on a retainer.
Why Infigini We self-host our own work We run apps on Dokploy, keep files in MinIO and reach private machines over Tailscale, so our advice comes from systems we operate.
We have built a private cloud Our multi-node hybrid cloud for dev and test runs Ubuntu VMs on Multipass and WSL2, with Tailscale subnet routing and a private .internal DNS zone.
Honest about trade-offs Self-hosting means you own uptime, disks and backups. If a managed service is the better choice for a workload, we say so in writing.
You own everything Servers, accounts, configuration and documentation are yours from day one. Nothing depends on a login we hold.
Technologies: Dokploy, Traefik, NGINX, Docker, MinIO, Tailscale, Multipass, WSL2, Technitium DNS, Let's Encrypt, PostgreSQL, Ubuntu
Related projects High-Performance Hybrid Cloud — A multi-node private cloud for development and test environments, with mesh networking and a web control plane.
Self-Service Deployment Server — A shared server that lets anyone in the organisation deploy applications through CI/CD to multiple domains and subdomains.
Campus Server Platform — The central server for a college group, hosting every project API, database and subdomain on one instance.
Frequently asked questions Is self-hosting cheaper than AWS, Azure or Vercel? For steady workloads it often is, because a rented VPS or your own hardware has a fixed monthly cost, with no per-build, per-preview or per-seat charges and usually a generous bandwidth allowance. The saving shrinks once you count the time spent on updates, backups and monitoring. We compare your current bill against the full cost of running it yourself before recommending a move, and we leave workloads that are cheaper or safer on a managed service where they are.
What is Dokploy and why use it? Dokploy is an open-source deployment platform you install on your own server. It gives you a web panel to deploy apps and databases from Git or Docker images, uses Traefik for routing and issues Let's Encrypt certificates automatically. For small teams it replaces SSH deploys with a repeatable process, without the overhead of running Kubernetes.
Can you set up a private cloud for development and testing? Yes. We build private clouds on hardware you already own, such as a powerful workstation or a few spare servers. Developers get isolated Ubuntu VMs they can create and reset from a web panel, reachable from anywhere over Tailscale and named through a private DNS zone. Nothing is exposed through port forwarding.
How do you keep self-hosted servers secure? Admin tools, databases and dashboards sit on a private Tailscale network rather than the public internet. SSH is key-only, firewalls allow only the ports the apps need, and security updates install automatically. Ports published by Docker bypass UFW rules, so we bind databases to the private interface instead of trusting the firewall alone. Each app gets its own credentials for storage and databases. We document all of it so your team can check what is open and why.
What happens if the server fails? Databases and files are backed up on a schedule and copied off the server, and we test restores rather than assume they work. The platform configuration is written down, so a replacement server can be rebuilt and the apps redeployed from Git. How quickly that happens depends on the recovery targets we agree with you at the design stage.
How is a private cloud or self-hosting setup priced? Setup work is a fixed-price project, quoted after we have looked at what you run today and what needs to move. Ongoing management is a monthly retainer based on the number of servers and apps and the support hours you need. Tell us about your current hosting and we will send an estimate.
Can we mix self-hosted and cloud services? Yes, and most of our setups do. A common pattern is apps and databases on your own servers, with a managed service kept for email, DNS or off-site backup storage. Tailscale connects machines in different places into one private network, so a server in your office and a cloud VM can reach each other safely.
Will our team be able to run it without you? That is the aim of a setup project. Everything is in your accounts, configuration is in your repository, and runbooks cover deploys, updates, restores and common failures. We finish with a hand-over session. If you would rather not run it yourselves, the same setup can move to a retainer later.
Further reading Dokploy vs Coolify vs CapRover: picking a self-hosted PaaS in 2026
Self-hosting internal tools vs SaaS: what it really costs
Building a private cloud on one workstation
Moving off the public cloud: when self-hosting makes sense
Self-hosted object storage with MinIO
Self-hosting production apps with Dokploy
Reaching private services with Tailscale subnet routing
Infigini IT Services · 11 Kanwali Road, Dehradun 248001, India · info@infigini.com · +91 95684 87789