Public cloud (SaaS)
Hosted on Microsoft Azure and managed by Veratas, with automatic updates and elastic scale.
Adverro runs on the System-on-Chip built into commercial displays, so there is no media player to buy, power or maintain behind each screen, which keeps the total cost of ownership down in every deployment model.
Choose public cloud (SaaS) hosted on Microsoft Azure and managed by Veratas, private cloud in your own Azure or AWS tenancy, hybrid with a local server on site, or on-premise in your own data centre. Every model runs the same platform, security controls and APIs, so what changes is who operates the infrastructure and where the data sits.
Every model runs the same platform, the same security controls and the same APIs. What changes is who operates the infrastructure and where the data sits.
| Public cloud (SaaS) | Private cloud | Hybrid | On-premise | |
|---|---|---|---|---|
| Infrastructure operated by | Veratas | Shared | Split | Your team |
| Available on | All plans | Scoped to your requirements | Scoped to your requirements | Scoped to your requirements |
| Data residency control | Region selectable | Full | Full | Full, your facility |
| Elastic scale | Automatic | High | High | Capacity planned |
| Updates and patching | Managed | Shared | Split | Your schedule |
| Disaster recovery | Managed | Configurable | Built in | Your design |
| Running cost | Subscription only | Subscription plus your cloud costs | Subscription plus a local server | Licence plus your servers and staff |
| Best suited to | Speed and low IT overhead | Dedicated resources | Mixed estates | Regulated and sovereign |
Hosted on Microsoft Azure and managed by Veratas, with automatic updates and elastic scale.
Dedicated resources inside your own Azure or AWS tenancy, combining isolation with cloud economics.
Central cloud management with a local server on site for continuity and local delivery speed. How hybrid and on-site deployments work.
A deployment inside your own data centre, on your servers and your storage. Windows-based on-premise deployments are available now and scoped with you.
All models include enterprise security, role-based access control, real-time monitoring, APIs and web view integration, and device management at scale.
Who actually does what.
The deployment model is a decision about operational responsibility, not about features. The platform, the security controls and the APIs are identical in all four. What changes is who gets paged when infrastructure fails, and whose change window applies.
| Public cloud (SaaS) | Private cloud | Hybrid | On-premise | |
|---|---|---|---|---|
| Infrastructure | Veratas | You | Split | You |
| Platform updates | Veratas | Veratas | Split | Your schedule |
| Panel application updates | Veratas | Veratas | Veratas | Veratas |
| Backup and retention | Veratas | You | Split | You |
| Monitoring | Veratas | Shared | Shared | You, or managed |
| Capacity planning | Automatic | You | You | You |
| First call on an outage | Veratas | Veratas | Depends on layer | Your team |
If a regulator or a security policy names the location, that answer chooses the model first: public cloud in a region you nominate, private cloud in your own tenancy, or on-premise in your own data centre.
In public cloud, Veratas does. In private cloud and on-premise, your team owns the servers underneath, which suits organisations that already run cloud tenancies or data centres.
Every model keeps playing from the display’s local cache. If sites also need to publish, pair new screens or deliver content locally without a link to the cloud, choose hybrid or on-premise.
Restricted or segmented networks, an existing identity provider or an audit regime you already run point to private cloud or on-premise. Without them, public cloud is usually the lowest total cost.
Every deployment model runs the same application, the same permission model and the same APIs. A screen provisioned against a private cloud instance is installed exactly as it would be against the cloud: the same package on the panel, the same installer route, the same grouping and scheduling. Nothing about the deployment model reaches the panel.
The way uptime is measured is also the same: from playback on every device, reported in the platform. Service levels and credits are defined in your agreement. Private cloud, hybrid and on-premise deployments are scoped to your requirements.
Which jurisdiction governs your data?
For a regulated organisation, the first question a security reviewer asks about any cloud platform is where the data lives and whose law applies to it. Adverro treats residency as a deployment choice: the same platform runs in a cloud region you select, in your own cloud tenancy, or entirely inside your own data centre.
Hosted on Microsoft Azure and managed by Veratas in the cloud region you nominate, so data stays within that geography.
Deployed into your own Azure or AWS account, so the data never leaves infrastructure you already control and audit.
Central management with local delivery, so content and telemetry stay inside the perimeter you define.
Running entirely on your own hardware, inside your own network perimeter.
Data location is a deployment choice, which is the question both GDPR and India’s Digital Personal Data Protection Act 2023 turn on. Backups are held daily in the Azure Central India region. Customer content is never used to train AI models, in any deployment model.
A local server, sized to the estate, that holds the content library and serves it to the screens on the local network. Where a display has no SoC capability, an Android or Windows player sits behind that screen. In a hybrid deployment the local server also carries pairing and provisioning, so a new screen can be added without a round trip to the cloud.
In hybrid, the platform, scheduling, approvals, reporting and alerting stay in the cloud, so a central team runs every site from one place while content is delivered locally. In on-premise, all of it runs inside your network, and nothing leaves it unless you choose to send it.
Veratas deploys and configures the platform and the local server, and installs the application on the screens. Your team owns the infrastructure, the network and the change windows. Managed operation, where Veratas monitors and operates the platform inside your environment, is available under an agreed service level.
Hybrid suits sites with limited or unreliable links to a central platform, or estates part way through a migration. On-premise suits organisations whose regulator or security policy requires the platform and its data to stay inside their own perimeter, and that already run data centres.
On-premise deployment: available now.
Adverro runs as a multi-tenant SaaS platform hosted on Microsoft Azure and managed by Veratas, and as private cloud and hybrid deployments. On-premise, meaning the platform, database and content store running on Windows-based infrastructure you own inside your own network, is available now. If the deployment model is decided by your regulator or your security policy, raise it at the demo and it is scoped with you.
The platform, database and content store run on infrastructure you own and operate, so nothing leaves your network unless you choose to send it.
Content is published through a portal reachable from your own network. Playback from local cache when the network drops is how every deployment works.
You own the infrastructure. Veratas provides the platform and the deployment, with managed operation under an agreed service level as an option.
Private cloud in your own tenancy is also available, with data residency in the region you select and the same platform as every other deployment.
Tell us your constraints and we will map them to a deployment model with you.
How hybrid and on-site deployments work