ISV Offering SaaS vs On-Prem

Hi,

If your app is already published in AppSource, you don't necessarily need a separate object ID range just because you also want to offer an on-premises version.

Microsoft currently supports both the RSP object range (1,000,000–69,999,999) and the App object range (70,000,000–74,999,999) for solutions that can be implemented in Business Central Online as well as Business Central On-Premises. For new publishers, Microsoft recommends requesting/using an App object range. Microsoft Learn

So, if your existing AppSource app is already using an assigned App object range, I would first check whether the same extension package/codebase can be used for the supported on-premises BC version rather than creating another set of object IDs.

The main difference is deployment and licensing. AppSource/Marketplace apps cannot simply be installed from the Marketplace through the Extension Management page in an on-premises environment. The extension has to be provided and deployed as an on-premises extension package. Microsoft Learn

For protecting the ISV solution, you can also consider distributing it as a runtime package. Microsoft states that runtime packages can be installed on a server without a developer license; the server needs permission to run the objects, rather than permission to modify them. Microsoft Learn

Regarding the customer's license, I would recommend checking the exact licensing requirements with your CSP/Microsoft partner channel for the customer's BC version and licensing model, particularly if this is an older on-premises installation. The licensing model can differ depending on the BC version.

Microsoft documentation on object ranges:
Business Central – Object ranges

Hope this helps.