Deployment in Microsoft Azure

Each customer has a dedicated RealmHelm deployment in Microsoft Azure. Use NetPrecedent hosting or deploy in your own Azure subscription.

Hosting options

Hosted by NetPrecedent

We deploy and operate RealmHelm in our Azure subscription, including platform updates, monitoring and backups.

Your Azure subscription

Deploy RealmHelm through a private Azure Marketplace offer. Your team manages the Azure resources, with support from NetPrecedent as needed.

Responsibilities

ResponsibilityHosted by NetPrecedentYour Azure subscription
Azure subscriptionNetPrecedentYou
Data locationNetPrecedent's Azure subscriptionYour subscription, in the region you choose
DeploymentNetPrecedentYou, through the Marketplace offer, with our help
Update managementNetPrecedentYour administrator, or automatic updates
Platform monitoringNetPrecedentYour team, with alerts to your recipients
Database backupsAzure automated backups, managed by NetPrecedentAzure automated backups in your subscription, with the retention you set
Support accessThe access needed to operate the platformRead only. Additional access is time limited and approved by your staff
Site agentsYou provide a VM or physical machine per site, and we help installYou provide a VM or physical machine per site, and we help install
Device credentialsYou enter themYou enter them

Deployment architecture

Site agents connect to local equipment and make outbound HTTPS connections to the appliance.

RealmHelm architecture At each site, a site agent reaches the local switches, firewalls, servers, cameras and radios, and connects outbound over HTTPS to your dedicated RealmHelm in Azure. Your people use RealmHelm from a web browser and from rhctl, RealmHelm's command-line tool. At each site Site agent Switches Firewalls Servers Cameras, radios Outbound HTTPS No VPN, no inbound ports Your dedicated RealmHelm in Azure RealmHelm application Database Key vault Storage Monitoring Your people Web browser Command line (rhctl) RealmHelm architecture At each site, a site agent reaches the local switches, firewalls, servers, cameras and radios, and connects outbound over HTTPS to your dedicated RealmHelm in Azure. Your people use RealmHelm from a web browser and from rhctl, RealmHelm's command-line tool. At each site Site agent Switches Firewalls Servers Cameras, radios Outbound HTTPS No VPN, no inbound ports Your dedicated RealmHelm in Azure RealmHelm application Database Key vault Storage Monitoring Your people Web browser Command line (rhctl)

Security

Change approval
A person must approve the exact device changes in the browser.
Credential storage
Device credentials are kept in Azure Key Vault and stay hidden once saved. Passwords and keys in backed-up configurations are masked.
Change history
Each change records who wrote, approved and ran it, and the output from each device.

See RealmHelm in use