New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
App Hosting Project Idea
cemalgnlts
Member
in Help
Hi,
I want to build a project similar to PikaPods. I'll be hosting apps like 'Uptime Kuma' and 'Ghost Blog' for potential clients, but I'm not sure how to architect the workflow.
I’m thinking of getting a high-resource VDS and deploying the apps via Dokploy or Coolify. Alternatively, I could spin up a separate VDS for each individual user.
Would VDS providers be bothered by high traffic or heavy CPU & RAM usage? Honestly, rather than incurring the heavy overhead of a bare metal server from the start, I think it makes more sense to begin with 64 GB of RAM and upgrade my resources based on the situation.
I'd love to hear your thoughts on this approach.
Thanks.
Comments
In my opinion, if this is more of a hobby project, then sure, experiment, play around, and learn as you go.
But if this is something that paying customers will rely on, then I think you are going in the wrong direction. Uptime, hardware failures, software failures, backups, monitoring, migrations, support, abuse handling, and resource isolation will become real problems very quickly.
If a user is paying you, they expect a reliable service. If you cannot provide that level of quality, then it is better not to sell it as a serious service.
These things take time, planning, testing, and proper implementation.
Otherwise it feels a bit like opening a hotdog stand and asking the cafe next door if you can borrow napkins every time a customer shows up. It might work once or twice, but it is not a business plan.
Sorry if i sound harsh
Stop vibecoding.
I didn't quite catch what you meant. However, I suspect you're having some issues with AI; you might want to discuss this topic elsewhere in the context of "Vibe Coding."
I think I chose to ignore certain things because I was caught up in the excitement of the project. Hearing you confirm the very things I was unsure about makes me realize it’s probably better not to start without a solid infrastructure and proper planning.
Thank you for your comment; you hit on some very valid points.