Platform first · Delivery model

Decide where the platform runs before choosing the first app.

Cloud and on-premises use the same NMS Prime stack. Decide who owns infrastructure, Linux, backups, DNS, and TLS—then which app track goes live first.

Compare delivery models Compare cloud and on-prem Watch introduction
Decide first Run · reach · secure One platform decision creates the foundation for network activation, CRM / BSS, and digital sales.
  1. 01 Choose the delivery model Pick managed cloud, self-hosted cloud, or on-premises based on control and operating capability. Done when: the infrastructure owner and operating owner are named
  2. 02 Choose the host For self-hosted cloud, pick AWS, Hostinger, or another supported VPS; for on-premises, name the hardware or VM. Done when: the provider, region, and account owner are agreed
  3. 03 Plan access Agree hostnames, DNS, TLS renewal, first admin access, and any trusted proxy. Done when: URLs, certificates, and access owners are documented
  4. 04 Choose Wave One apps Pick the smallest app stack that completes one operational outcome. Done when: the first track, app owners, and acceptance criteria are signed off

Delivery model

Same platform. Three operating models.

All three use Rocky Linux 9 or RHEL 9 and the same RPMs. What changes is who owns and operates the infrastructure.

Fastest handoff

NMS managed cloud

NMS Prime provisions the environment and sends the HTTPS URL and credentials. The managed default is an EU region in Frankfurt.

  • TimeTypically ready in under 15 minutes
  • YesNMS team provisions and operates the VM
  • YesLow Linux knowledge required
Choose for a fast start with one accountable team. Technical guide
Cloud under your account

Self-hosted cloud

You provision a supported VM at AWS, Hostinger, or another VPS. Installation uses the same packages as on-premises.

  • YesYou own the provider account and billing
  • PartialYou operate the VM, capacity, and network
  • YesAWS and Hostinger have dedicated guides
Choose for cloud elasticity with infrastructure control. Technical guide
Full local control

On-premises

Run NMS Prime on your own server or virtualisation, close to the access network.

  • TimeUnder 30 minutes on a fresh VM
  • YesData stays at the location you choose
  • NoHA and backups are yours unless agreed by SLA
Choose when local control and plant proximity matter most. Technical guide

What to prepare

Five platform decisions unblock every app workshop.

These customer deliverables come before module configuration.

01

Delivery model

  • Managed cloud, self-hosted cloud, or on-premises
  • Who provisions and operates the VM
  • Hybrid only where the operating split is explicit
02

Hosting

  • Provider and production region
  • Cloud account and billing owner
  • Capacity, backup, and restore responsibility
03

Domain & TLS

  • Admin, shop, portal, and API hostnames
  • DNS change owner
  • Certificate issue and renewal owner
04

Project ownership

  • Technical and commercial contacts
  • Finance and legal contacts where needed
  • Named owner for each onboarding workshop
05

Wave One Scopes

  • Licensed app list
  • One outcome-led starting track
  • Platform and app acceptance blockers

Installation, condensed

Cloud and on-premises share one technical baseline.

These are the decisions that matter before provisioning.

Cloud vs on-premises at a glance

Topic Cloud On-premises
Who operates the VM PartialNMS Prime (managed) or you (self-hosted) YesYou
Ready to start TimeUnder 15 minutes when managed TimeUnder 30 minutes on a fresh VM
Linux knowledge YesLow if managed, medium if self-hosted PartialMedium
High availability YesProvider baseline (e.g. AWS) NoYour architecture and operations
CPU, RAM, and disk YesScale with the provider NoPlan and provision locally
Data location YesEU Frankfurt by default; other regions on request YesThe site you choose
Automatic backup YesIncluded in the managed path NoIncluded with SLA only
Software stack YesRocky Linux 9 / RHEL 9 and the same RPMs YesIdentical stack and packages

Functionality is the same in both models. Hybrid (cloud BSS, on-prem OSS) is possible when the operating split is explicit.

Fresh supported OS

Use a fresh Rocky Linux 9 host for Community, or Rocky Linux 9 / RHEL 9 for Prime Enterprise. Do not pre-install the database or web stack.

One RPM delivery path

Cloud and on-premises install from repo9.nmsprime.com. Managed cloud is prepared by the NMS Prime team.

Edition changes access

The OSS core needs no license. Prime apps require a license file, repository access, and a curated package list.

Size for the workload

Guidance starts at 4 cores, 4 GB RAM, and 32 GB disk; production is typically 16+ cores, 16–32 GB RAM, and 200–400 GB SSD/NVMe.

Two documented self-hosted cloud paths

AWS EC2

Rocky Linux 9, gp3 storage, security groups, Elastic IP, and Frankfurt as the documented default region.

Technical guide Hostinger VPS

A straightforward VPS path for customer-hosted deployments; also used for automated RPM installation tests.

Technical guide

Product media

See the platform, then the first screen.

A short walkthrough of the installed apps after login, plus local views of a redundant setup and the operational home screen.

Platform walkthroughTorsten Schmidt walks through the installed NMS Prime apps after login—billing, CRM, provisioning, monitoring, and more.
Two NMS Prime instances side by side, illustrating a redundant platform
Redundant platformTwo instances side by side. Illustration from the Start here page.
Prime Dashboard home view with coloured status tiles above a system summary
Operational home screenStatus tiles after login. Archive capture from 2021.

Apps in this journey

Choose apps by outcome, not from one flat catalogue.

Start with the smallest stack that produces a testable result. Shared apps such as Product and Billing can appear in more than one track.

Track A · Network activation

Get the first modem online

Prove one complete device path from service definition through activation and NOC visibility.

Open journey
OS ProvisioningGateways, pools, QoS, configuration, and activation. Prime ProductThe sellable service profile for the pilot. Prime BillingCommercial contract and cost-centre minimum. Prime MonitoringOperational visibility after activation.

Track B · CRM / BSS

Organize your Telco

Build one chain for catalogue, addresses, customers, invoices, documents, and care.

Open journey
Prime ProductCatalogue, technology, speed, and tariff rules. Prime PropertyAddress, building, coverage, and rollout truth. Prime BillingInvoices, payments, credits, and settlement. Prime CRMCustomers, contacts, contracts, and relationships. Prime Document ManagementTemplates and generated customer documents. Prime Customer Self-Service PortalInvoices, services, and account journeys for customers. Prime TicketOwned work across care, NOC, and field teams.

Digital sales

Drive ISP sales

Turn an address into an eligible offer, a clean order, and an activation-ready contract.

Open journey
Prime PropertyService footprint and address source of truth. Prime ProductEligible offers, prices, speeds, and options. PRIME Service AvailabilityThe answer to what can be sold at an address. Prime Order PortalThe customer-facing order journey. Prime SalesLead qualification and opportunity conversion. Prime CRMThe resulting customer and service contract.

Customer self-care

A control center customers actually use

Open invoices, account changes, and upgrades onto the same contract your care team already sees.

Open journey
Prime Customer Self-Service PortalThe customer-facing portal for invoices, account, and upgrades. Prime BillingInvoice, CDR, and payment records shown in the portal. Prime CRMCustomer, contract, and service context behind the login. Prime TicketSupport requests that leave the portal as owned work.

Care, tickets and field

One ticket from first call to the van

Care records the problem, Detect locates it, Ticket owns it, and Workforce routes the visit.

Open journey
Prime TicketType, owner, priority, due date, and history. Prime DetectPlant impairments and affected devices. Prime WorkforceTechnicians, tickets, and directions on the map. Prime Customer Care AppGuided agent workspace on the same customer record.

Collections and dunning

Chase overdue money on a schedule

Match payments, age open items, run reminder letters, and apply agreed service consequences.

Open journey
Prime BillingInvoices, due dates, and the SEPA lifecycle. Prime OverdueMatching, remaining amounts, and block indicators. Prime DunningBatch reminder-letter runs. Prime Document ManagementLetter templates and generated PDF packages.

Source material

Prime Platform onboarding

Canonical delivery-model, hosting, DNS, TLS, and Wave One app decisions.

Installation

Cloud/on-prem comparison and the shared Rocky/RHEL 9 RPM installation path.

Hardware Requirements

Supported OS, sizing, storage layout, networking, and virtualisation guidance.

Related journey

Get the first modem online

Start with a real network activation acceptance test.

Organize your Telco

Start with the customer, product, address, billing, and care stack.

Drive ISP sales

Start with address eligibility and digital ordering.

Make the platform decisions in one delivery workshop.

Bring your infrastructure owner, preferred delivery model, provider options, domain plan, and first operational outcome.

Book a strategy call