Your project-specific resources remain owner-only in every model. Paying the centralized project never buys access or control: it only adds a convenient domain or amortizes the cost of shared supporting services.
There is no requirement to rely on the centralized project forever. The subdomain and shared infrastructure are replaceable conveniences, not permanent dependencies. If you choose to leave—or if Elsdon is ever discontinued—you can switch to your own domain and an automatically created registry in your Azure account, then continue in the fully self-hosted mode.
The open-source core provides the exit path. The mechanisms remain inspectable and runnable in your own environment, so moving away from centralized services does not mean abandoning the underlying project or rebuilding it from scratch.
All three paths land in a similar baseline price range. Full self-hosting commonly requires an Azure Container Registry at roughly $5 per month. The amortized model applies that same monthly spend to shared infrastructure and includes a convenient subdomain.
The paid options also help sustain the project. Think of that support as a tip attached to useful convenience: the one-time option provides a subdomain, while the monthly option pools infrastructure that each self-hosted customer would otherwise need separately. Any margin comes from that sharing efficiency—not from marking up Azure usage or taking control of customer resources.
The middle option purchases account-wide naming convenience for a nominal one-time fee. The amortized option is a recurring account-wide plan: its monthly fee is charged whether or not you actively use every included shared service.
Azure run costs apply to every option. Projects produced by the harness generally cost close to zero while idle. Persistent storage and other allocated resources are charged separately at Azure's market rate—on a per-second basis for most resources.