NexusA complete integration, reporting, and automation platform — running in your tenant
Nexus combines a multi-system adapter layer, a Universal Query Language, pipeline orchestration, reporting, and a sandboxed Python runtime in one Azure-native deployment.
One integration layer for disconnected business systems
Build reports, dashboards, automations, transformations, and pipelines across systems that were never designed to talk to each other — without moving data out of your environment.
AI pipelines via MCP
Connect any MCP-capable AI agent and have it build pipelines, queries, and automations against your live systems — governed and logged in your tenant.
Sites
Have AI build fully integrated custom software on top of your data. It runs inside Nexus — no external hosting, no separate stack to operate.
Multi-system integration
Connect ERPs, databases, and SaaS behind a single, governed integration layer in your tenant.
Universal Query Language
One request shape across every connected system, with pushdown declared per adapter and every run recorded.
Pipelines & automation
Orchestrate transformations and scheduled data movement with monitoring and retries.
AI-assisted reporting
Generate auditable UQL from natural language — answers for analysts, governance for IT.
Azure-native, customer-owned
Nexus is provisioned as a managed application into your subscription. The application tier, database, storage, and Key Vault all live in your resource group. Stingray ships updates through the managed application contract without ever touching your data plane.
- Runs in your subscription and region
- Customer-owned database and storage
- Updates via managed application contract
- No vendor data plane
Reference architecture
All components are provisioned into your resource group and owned by you. Stingray manages application updates through the managed-application contract only.
| Component | Role |
|---|---|
| Azure Container Apps | Application, query engine and scheduler |
| PostgreSQL | Metadata, workspace tables and run history |
| Azure Key Vault | Connector secrets, signing and encryption keys |
| Storage account | State, exports and git-backed authoring history |
| Microsoft Entra ID | Authentication, SSO and conditional access |
| Private endpoints | Network isolation under your own policy |
AI builds your pipelines through MCP
Nexus runs a Model Context Protocol (MCP) server inside your tenant, so any MCP-capable AI agent can read your connected schema and author pipelines, UQL queries, transformations, and automations against live systems. Every action is governed by RBAC and recorded in your audit log.
- Native MCP server for AI agents
- Agents author pipelines and UQL
- Every action governed by RBAC
- Generated logic is reviewable and auditable
Custom software, fully integrated, zero external hosting
Sites lets AI build internal applications directly on top of your connected data. The apps run inside Nexus in your Azure tenant — there is no separate stack to host, secure, or operate, and data never leaves the environment it already lives in.
- AI-generated internal apps
- Runs inside Nexus — no external hosting
- Reads and writes live connected data
- Inherits Entra ID auth and RBAC
One query model across every system
UQL is one request shape — bridge, collection, select, where, group_by, order_by — that every adapter compiles into its own native operations: SuiteQL, a SQL dialect, REST calls or a file scan. What the source can filter, it filters; what it cannot, the engine applies.
One read targets one bridge. Combining two systems is done deliberately, by staging both into the built-in workspace inside a pipeline, rather than by inventing a distributed join across systems that were never designed for one.
- One request shape across every system
- Pushdown declared per adapter, never assumed
- Parameterized, reusable, version-controlled
- Fully auditable execution
{
"bridge": "NETSUITE.production",
"collection": "transaction",
"select": ["entity", "trandate", "foreignamount"],
"where": {
"type": { "$eq": "CustInvc" },
"trandate": { "$gte": "2026-07-01" }
},
"order_by": [{ "field": "trandate", "direction": "desc" }],
"limit": 500
}Orchestrate movement and transformation
Define pipelines that extract, transform, and load across systems on a schedule or trigger. Built-in monitoring, retries, and lineage give engineering teams operational confidence.
- Scheduled and event triggers
- Retries and failure handling
- Run history and lineage
- Incremental loads
A growing connector library
Adapters normalize each source system into the UQL model. The library spans ERPs, relational databases, SaaS platforms, and file sources, and expands continuously.
- ERP, database, SaaS, and file sources
- Consistent normalized schema
- Secrets stored in your Key Vault
- Continuously expanding
Reports and dashboards on live data
Build operational and analytical reports directly on connected systems. No separate warehouse is required, though Nexus can land data into one you own.
Natural-language reporting compiles to auditable UQL that runs entirely in your tenant. Analysts get answers; engineering keeps governance, lineage, and review.
- Operational + analytical reporting
- Dashboards on live sources
- Export and scheduled delivery
- Row-level access controls
{
"bridge": "MSSQL.production",
"collection": "dbo.invoices",
"select": ["customer_id", "balance"],
"where": { "status": { "$eq": "OPEN" } },
"group_by": ["customer_id"],
"aggregations": [{ "field": "balance", "fn": "sum" }]
}Custom logic, safely isolated
Run custom transformations in a sandboxed Python runtime that executes within your environment with constrained resources and no outbound access beyond approved connectors.
- Isolated execution sandbox
- Resource-constrained runtime
- Reusable transform functions
- Runs inside your tenant
Your governance, applied directly
Because Nexus lives in your tenant, your existing network isolation, private endpoints, and Azure Policy apply to it. Encryption and secrets remain under customer control.
- Customer-controlled encryption
- Private endpoints and network isolation
- Azure Policy compliance
- Tenant-resident audit logs
Microsoft Entra ID and RBAC
Authentication is handled through Microsoft Entra ID. Role-based access control governs every adapter, query, pipeline, and report, with full audit trails.
- Entra ID single sign-on
- Granular RBAC roles
- Conditional access support
- Complete audit logging
Provision from the Marketplace
Deploy from the Azure Marketplace as a managed application. Initial configuration and identity setup take minutes, and the resources are yours from the first deployment.
- Marketplace managed application
- Guided initial configuration
- Identity setup with Entra ID
- Customer-owned from day one
Connect the systems you run today
Adapters available today, with new systems added regularly. Need one we don't list yet? Request it for your stack.
NetSuite
SuiteQL and REST — surface ERP data alongside every other system.
QuickBooks Online
Governed access to QuickBooks accounting data.
SQL Server
Native pushdown against Microsoft SQL Server.
MySQL
Query MySQL databases through the UQL model.
PostgreSQL
Connect PostgreSQL and the internal workspace.
Monday.com
Bring project and operational data into governed reports.
Frequently asked questions
Where does Nexus actually run?
That is the choice you make when you buy it. Self-hosted, Nexus is an Azure Marketplace managed application: the compute, database, storage and Key Vault are provisioned into a resource group in your own subscription and owned by you. Stingray-hosted, the same build runs on shared infrastructure that we operate in our Azure subscription, with a dedicated database and secrets per customer.
Is there a free trial?
Yes — the Stingray-hosted plan is free for your first month, taken through the Microsoft Marketplace with your Microsoft account. It is the full product, not a restricted tier: every connector, pipeline, report, Site and the MCP server. After the month it is $150/month, and you can cancel at any point. Self-hosted deployments are scoped as a private offer instead of a trial.
What is the difference between the hosted and self-hosted plans?
The product is the same build with the same features. Self-hosted gives you dedicated resources inside your own tenant, your own governance perimeter, and scoped implementation support — it is sold as a private offer. Hosted is free for the first month and $150 a month after that, self-serve on the Microsoft Marketplace, on infrastructure we run and share between customers, which means lower throughput and standard support rather than implementation hours.
Does any of our business data reach Stingray?
On the self-hosted plan, no — data is read, transformed and stored entirely within your tenant, and Stingray has no data plane there. On the hosted plan you are choosing to have us operate the infrastructure, so your workspace and cached data live in Stingray's Azure subscription, isolated per customer. Pick self-hosted if data custody is a requirement.
Who controls encryption and secrets?
Self-hosted, you do: encryption keys and connector secrets live in your own Azure Key Vault, reached through managed identity, and Stingray has no access to them. Hosted, secrets live in the Key Vault we operate, isolated per tenant. In both cases secret values are never returned through the API or written to logs.
How is Nexus different from Boomi, Workato, or MuleSoft?
Those platforms route and often store your data on vendor-controlled infrastructure. Self-hosted Nexus deploys into your tenant, so there is no vendor-controlled customer database and data residency follows your existing Azure policy.
Which systems can it connect to?
NetSuite, Monday.com, SQL Server, MySQL, PostgreSQL, QuickBooks Online, Stripe, REST APIs, files, and JDBC-reachable databases such as Oracle, Salesforce and Snowflake. Every adapter's authentication, capabilities and pushdown operators are published in the adapter reference.
How is Nexus different from Microsoft Fabric or Power BI?
Fabric and Power BI are warehouse and BI tools — you typically copy data into them to model and visualize it. Nexus is a governed access and automation layer over your live systems: it queries NetSuite, SQL Server, QuickBooks and others in place, without standing up a warehouse. They are complementary — Nexus can feed governed, reconciled data into Fabric or Power BI.
How is Nexus different from dbt or building custom Azure pipelines?
dbt transforms data already landed in a warehouse, and custom pipelines are infrastructure you build and operate yourself. Nexus provides the cross-system connectors, governed RBAC, audit logging, and Python automation out of the box — so teams reconcile and report across systems without hand-building and maintaining that plumbing.
Is Nexus a fit for individuals or small projects?
No. Nexus is enterprise infrastructure for teams whose data is spread across multiple business systems and who need governed access and auditable automation. For personal projects or single-source analytics, lighter tools are a better fit.
Deploy Nexus into your Azure tenant
The infrastructure, database, and Key Vault are yours from the first deployment.