Deployment and security
Choose how to run OMN to suit your IT: SaaS, hosting or on-premises. User responsibilities and day-to-day operations matter as much as the deployment model.
Three ways to deploy OMN
SaaS: use OMN as a provided software service. OMN Accelerator is the preconfigured SaaS entry point, suitable when you want to start within a predefined framework.
Hosting: OMN documentation describes purchasing licences and running the software with a hosting provider such as apollon. Software licences and hosting services can therefore be considered separately.
On-premises: OMN can run in an environment you operate. Involve your IT team early to align infrastructure, maintenance and cooperation with apollon support.
User licences based on actual use
PIM and DAM base licences use named users. According to the licensing model, Power Users and Light Users have the same functional scope, but Light Users are limited to four hours per week. Portal Users have read-only access.
This distinguishes regular data maintenance, occasional contributions and read-only use. A user licence does not replace an access-control design: define separately which content and actions each person needs. Add-ons such as Flatplan are licensed separately per tenant installation.
What to establish before deciding
Agree with your IT team where data may be stored, who owns updates, monitoring and incident resolution, which backup and recovery objectives are required, and how users are provisioned and access revoked.
Obtain specific confirmation of hosting location, sign-in methods, backup scope and support hours for the proposed solution. These services depend on the deployment model and agreement; they are not a blanket promise for every OMN installation.