Comment by packet_mover

Yes - I do plan to sell Corviont, and it is worth explaining the licensing bit.

It is built on open-source components and OSM-derived data, so the obligations are mostly (a) keeping third-party software licensing/attribution intact, and (b) OSM/ODbL compliance - clear attribution, and if you distribute derived OSM databases, meeting the ODbL share-alike requirements for those database artifacts.

I am handling this via attribution in the UI/docs and a licensing reference bundled with the dataset that points to a public licensing/attribution repo containing the third-party license texts and details: http://github.com/corviont/licensing

What I am selling is the packaging + ops side: ready-to-run region packs and (eventually) a signed updater for fleets.