Self-host Ombi on a VPS
Request and discovery portal for your media library.
A friendly front end where users request media, see what is available and get notified when it lands in the library.
Why self-host Ombi?
Ombi turns a media server into a service others can use without needing access to the admin side.
How to install Ombi
- 1
Provision a VPS
Choose a plan with room for your data as well as the app.
- 2
Install the stack
Install .NET + SQLite/MySQL.
- 3
Deploy the application
Follow the project’s official install guide for your distribution.
- 4
Enable HTTPS
Serve it on your own domain behind a reverse proxy with a certificate.
- 5
Back it up
Schedule a database dump plus a copy of any uploaded files to an off-box location.
Practical tips
- Give Ombi its own database user with rights only on its own schema.
- Reverse-proxy Ombi and terminate TLS at the proxy so certificates are managed in one place.
- Take a VPS snapshot before major upgrades so you can roll back cleanly.
- Keep Ombi patched — most self-hosting incidents are unpatched software.
Frequently asked questions
- How much RAM does Ombi need?
- Plan on 1–2 GB for typical use; add headroom if you expect many concurrent users.
- What stack does Ombi run on?
- .NET + SQLite/MySQL.
- Can I run other things on the same VPS?
- Yes — size the plan so Ombi plus your other workloads fit in RAM with room to spare.
Looking for something else? Popular alternatives include Jellyseerr, Overseerr, Petio — browse all app guides.
About Ombi
Ombi is open-source software released under the GPL-2.0 licence. HostingSwift does not maintain, sell or support Ombi itself — you install and run it on your own VPS. These are the official links to the project:
- Website: ombi.io
- Source code: github.com/Ombi-app/Ombi
Read the project's own documentation before deploying. We credit upstream projects because we genuinely run and recommend them — see our full open-source directory.