HOMER 7 on Ubuntu 24.04 LTS

Why the cloudimg image

A self assembled install of this stack is a day of careful work: two databases and a role, schema migrations, a capture server configuration, the web application wired to both databases, a signing secret and a TLS front door. cloudimg ships all of it done, so the first sign in lands on a working platform. The ingest port is the part most deployments get wrong, because the capture protocol carries no authentication the server enforces: an open port is an unauthenticated way to write into your call database. So it ships listening but closed, and the paired guide walks through opening it to your own signalling hosts and nothing else, with a note on the mutual TLS alternative. Five separate secrets, both built in logins, the database password, the session signing secret and the TLS key, are generated on the first boot of every instance, so there is no known credential in the image and no two instances share one. Captures live on a dedicated volume with retention already configured, the image itself contains the schema and nothing else, no call data of any kind, and every instance proves its own capture path on first boot by sending a synthetic call into its own listener and reading it back through the API. The base is fully patched with unattended security updates enabled, paired with a step by step deploy guide and backed by 24/7 cloudimg support.