How do you handle database hosting for client apps sold on a one-time fee (outgrowing Supabase free tier)?
retained text
<!-- SC_OFF --><div class="md"><p>Hey everyone,</p> <p>I'm a student developer who has been doing this for a while now. Last year, I've built and deployed custom web applications for 4 different small/medium-sized business clients, ranging from a POS and internal management systems to a photo studio tracking app with google drive integration.</p> <p>The situation is that I only bill clients for a one-time project deployment and have no recurring revenue streams, only factoring in maintenance if a client requests any monthly backend updates.</p> <p>Therefore, being a sole proprietor with no one to outsource my database management to, I cannot afford to pay for an ever-growing monthly bill from a service like Supabase, which already puts a strain on my initial project deposits:</p> <p>The 2 database project limit (having to manually pause projects when taking on new clients)</p> <p>The 500MB database size limit per project</p> <p>I really don't want to have to pay for a Supabase Pro tier ($25/mo per project) because it means paying $100+)/month out of pocket for something that is supposed to be a one-time payment for my clients. I actively seek to acquire more local SMB clients and want to be able to host their database somewhere as a long-term investment with a fixed, steady cost that I can base my own pricing around, or ideally, have it's costs transparently passed to the client.</p> <p>I was considering deploying a self-hosted postgres instance either on Dokploy or Coolify (probably dokploy as it has a free tier on hetzner), which would allow me to put all databases on separate docker containers either on the same server and be billed around $5-10/month for the server, or potentially scale up if needed, or even use a usage-based serverless provider such as Neon, Railway, or Turso which would allow me to only pay for the resources I use, which would be next to nothing for a single database running on the backend of a simple app</p> <p>Now, for someone in my position, selling a one-time software product to a local SMB with no recurring revenue, but having to upkeep databases, what would be the best way to do it without spending too much on monthly subscriptions?</p> <p>If I were to go the self-hosted Dokploy/Coolify route, what would be the best way to make sure that backups are regularly and automatically saved elsewhere and databases are isolated from one another?</p> <p>Any advice or recommendations are welcome!</p> </div><!-- SC_ON -->   submitted by   <a href="https://www.reddit.com/user/yellowwwcum"> /u/yellowwwcum </a> <br /> <span><a href="https://www.reddit.com/r/SaaS/comments/1vl8yxa/how_do_you_handle_database_hosting_for_client/">[link]</a></span>   <span><a href="https://www.reddit.com/r/SaaS/comments/1vl8yxa/how_do_you_handle_database_hosting_for_client/">[comments]</a></span>
document fetched 2026-08-11 07:10 · canonical https://reddit.com/r/SaaS/comments/1vl8yxa/how_do_you_handle_database_hosting_for_client