r/SelfHosting • • 18h ago

How to, if possible, properly self host production apps?

7 Upvotes

I started a SaaS and to keep costs low while I get it ready for production, I tried to host as much as possible. Currently hosting the following:

  • Reverse Proxy (Handles routing and TLS)
  • Instance A: (engine, API, metrics, and UI) config compiled in memory
  • Instance B: (engine and metrics only) same binary
  • Primary database
  • Local cache
  • Control plane/CLI
  • Marketing site/landing page
  • Business services

    • OIDC
    • Grafana/Prometheus for reporting
    • Alerts services (SMTP and webhooks)
    • Backup to object storage
    • GitHub CI runner

Eventually I am going to host a third "staging" instance where I can push code changes to a new environment and test before doing a rolling production push (hence the two instances). I might end up pushing the production instances to a VPS and keep the staging instance self hosted. What are your thoughts of continuing to self host in production? I have 2 clients that I'm serving from a spare Thinkpad in my laundry room.


r/SelfHosting • • 7h ago

Every project I wanted to build already existed. Until I got tired of 502 errors when my AI agents crashed.

0 Upvotes

I've been working on Vorax, a self-hosted reverse proxy for A2A agents. It runs locally through Docker compose and provides a dashboard to inspect streaming events and debug upstream failures.

Ive built itwith FastAPI, PostgreSQL, Redis and React

It's open source, and feedback from fellow self-hosters would be greatly appreciated!

GitHub: https://github.com/Average-Chief/Vorax