A separate installation for your organisation.
If your Microsoft 365 monitoring requirements include control over the server or a separate application installation, Vigil Alerts offers two deployment choices.
Self-host on your own infrastructure
Deploy Vigil Alerts on a server your team controls. Choose the infrastructure and manage application access, server maintenance, backups and updates through your operating procedures.
This can suit an MSP with its own hosting environment, or an internal IT team that wants to operate the monitoring application itself. Your team remains responsible for configuring and securing that environment.
Dedicated hosting without running the server yourself
With dedicated hosted Vigil Alerts, your organisation gets a virtual server and application instance reserved for its installation. Your monitoring environment is not placed inside a single application instance shared with other Vigil Alerts purchasing organisations.
We agree the hosting region, capacity, maintenance, backups and support arrangements before deployment. Dedicated virtual hosting does not mean the underlying physical hardware is exclusive to you.
How that differs from shared SaaS
In a multi-tenant SaaS architecture, a shared application can serve several organisations, with controls separating their data and access. Shared SaaS can be securely designed; using it does not mean customers can see one another’s information.
Vigil Alerts’ dedicated hosted offer uses a separate virtual server and application installation per purchasing organisation. The reason to choose it is a clearer deployment boundary and an agreed hosting arrangement, rather than an absolute claim that data crossover or security incidents are impossible.
A purchasing organisation is not the same as a Microsoft 365 tenant
An MSP may monitor several Microsoft 365 customer tenants within its own Vigil Alerts installation. Those tenants are intentionally managed together by the MSP’s authorised engineers. A separate hosted installation for the MSP does not automatically put every end customer on a different server.
If an end customer requires an independent server, application or specific access boundary, request that separately so the deployment and price can reflect it.
Ask where the boundaries sit
When comparing Microsoft 365 monitoring services, ask which application, database, backup, administration and physical infrastructure components are separate or shared. Server separation is one part of the answer; provider access and supporting services also need to be understood.
Self-hosting still requires connections to Microsoft 365 and any external services you configure. It is not an offline deployment or an automatic guarantee of data residency or compliance.
Background reading: IBM’s explanation of single-tenant and multi-tenant cloud architectures.