Why we ship Nexus as a managed application

The SaaS trust problem

Most integration platforms route your business data through infrastructure the vendor owns and operates. That means your most sensitive records — financials, customer data, operational history — transit and often persist on systems you cannot see, govern, or audit. For regulated enterprises, that is precisely the architecture their security teams are trying to eliminate.

Inverting the model

Nexus ships as an Azure Marketplace Managed Application. When you deploy it, every resource — the application container, the database, the storage account, and the Key Vault — is provisioned into a resource group inside your own subscription. Stingray publishes and updates the software through the managed application contract, but never holds your data plane. Your data never leaves your tenant.

What you actually own

Because the deployment lives in your subscription, your existing Azure Policy, network isolation, private endpoints, and cost controls apply to Nexus automatically. Encryption keys and connector secrets live in your Key Vault, under your control. Data residency follows your Azure region, not ours.

How updates work

New versions are delivered as signed images that your instance pulls on your schedule through an authenticated control-plane channel. You stay current without ever granting a third party access to your running data. Ownership and operational visibility stay with you from the first deployment.