I'm in the process of launching my own freelancing software development venture and I'm looking for feedback on my initial infrastructure plan. I've set up two domains and have two VPS/root servers to host my projects. Here's the current breakdown:
- **myCompany.com** (BaseFort01): A server with a 4c AMD EPYC 9645, 8 GB DDR5 ECC, and 256 GB NVMe SSD, used for admin/control and my company website.
- **myCompany.cloud** (BaseCamp01): A more powerful server with an 8c AMD EPYC 9645, 16 GB DDR5 ECC, and 512 GB NVMe SSD, dedicated to client SaaS applications.
I plan to scale by adding more BaseForts in the future for high availability and will map subdomains for each client's applications (e.g., app1.client1.myCompany.cloud).
I'm mainly concerned with whether this initial strategy is reasonable, how professionals would approach a similar setup, and what considerations I need to make for using Dokploy. Would greatly appreciate any pointers or critiques of my setup before I dive deeper.
5 Answers
You might want to rethink how much storage you're allocating right on the servers. What's your plan for databases and file storage with the apps you're building?
The setup looks good for a start! Just remember to keep it simple at first—only scale when necessary. Also, don’t forget about backups and monitoring from the get-go!
Consider having clients pay for their infrastructure. This way you can keep their setups isolated, which will help avoid issues if one client uses too many resources. It's also risky if they stop paying you!
I get that! But most of my clients have little IT knowledge, so I can’t expect them to handle that. I do charge maintenance fees, which is more understandable for them. I’m aware of the resource issue and I have limits set, but I'm also worried about the management overhead for separate clients—any advice?
Your server choices seem overpowered for basic websites and a client platform. I’ve managed similar setups for much less—like $10 or $20 a month!
Haha, my costs are even lower! These apps are more complex than just websites, like ERP and team chat modules.
Best of luck getting clients!
Thanks—your positivity is noted! I’m actually working on two pretty complex projects, one for a manufacturing company and the other for a hospital, so my approach is a bit complicated to meet specific client needs.
Good point! The storage came bundled with the cheap server plan. While I don’t strictly need all of it, I figured having extra wouldn’t hurt. Each app will run in its own "container" with a separate database and dependencies. For file storage, I’ll follow the same separation approach unless clients have different requirements.