Deploy
Deploy AssetZA the Way Your Organization Requires
Choose multi-tenant SaaS, dedicated SaaS, private cloud, on-premises, or hybrid — the same platform, deployed to fit your IT and compliance requirements.
Overview
What deployment covers in the platform
Five models. One product surface — choose the hosting path your organisation requires.
Five clear models
Multi-tenant SaaS, dedicated SaaS, private cloud, on-premises, and hybrid.
Same platform underneath
Capabilities stay aligned across models — deployment changes hosting, not the product story.
Fit IT and compliance
Pick the model that matches policy, residency needs, and operating preference.
Deployment models
Challenges
What deployment flexibility solves
One-size hosting fails policy
IT needs on-prem or private cloud, but the product only ships as public SaaS.
Cloud vs on-prem forks
Different deployment paths mean different features, releases, and support models.
Residency answers are vague
Buyers ask where data lives — and get a sales deck instead of a clear model choice.
Hybrid is hand-waved
Some workloads must stay local while others can run in SaaS — with no shared platform story.
Capabilities
What deployment flexibility delivers
Need residency and hosting detail? Continue to Deployment & data residency.
How it works
Five models, one platform
- SaaS
- Dedicated
- Private
- On-prem
- Hybrid
Outcomes
What teams gain from flexible deployment
Policy-fit hosting
Choose SaaS, private cloud, or on-prem without abandoning the platform.
No feature fork story
The same AssetZA surface stays consistent across deployment models.
Clear next step for compliance
Choose the model here; open Trust Center for residency and security posture.
Who it's for
Built for the teams that own the hosting decision
Three roles. Five models.
IT & security
Match deployment to policy, network, and control requirements.
Procurement & economic buyers
Compare models without buying a different product for each constraint.
Compliance reviewers
Separate model choice from residency proof — then follow Trust Center for detail.
Continue exploring
Related capabilities
Frequently asked questions
Can asset management software be deployed on-premises?
Yes. AssetZA deploys on-premises as well as multi-tenant SaaS, dedicated SaaS, private cloud, and hybrid — same platform, different hosting paths.
What is the difference between SaaS and private cloud deployment?
SaaS (multi-tenant or dedicated) is operated as a cloud service. Private cloud runs in a private cloud footprint under stricter boundary or residency requirements — still the same AssetZA platform.
Do features change by deployment model?
Hosting and operating model change. The platform capabilities and configuration approach stay aligned so teams are not forced into a forked product.
How is this different from Trust Center data residency?
This page covers which deployment models exist and how to choose. Trust Center Deployment & Data Residency covers where data is hosted, regions, and compliance posture.
Can we run a hybrid model?
Yes. Hybrid lets some workloads stay local while others run in SaaS or cloud — when policy requires a split footprint.