Nexion Labs markNEXION LABS
Run it like infrastructure
In build · Design-partner access

Enterprise Operations

Take the same workflows to production with governance, audit and separate environments.

A control plane that turns authored workflows into governed production assets. It covers identity, promotion across environments, secrets kept in your own vault, pooled execution and tamper-evident audit, all designed for regulated industry. It extends the open-source core rather than forking it, so what runs on a laptop is what runs in production.

Promotion · regional-sales
dev
v14
Deployed
qa
v13
Verified
prod
v12
Awaiting approval
Plan · qa → prod2 approvals required
  • + connection dataverse → prod-crm (mapped)
  • + secret crm-client → Key Vault
  • ~ parameter region_filter changed
Audit chain
a41f
9c02
e7b3
51d8
0fa6
Unlimited
Environments, each with its own setup
Hash-chained
Audit, verifiable end to end
Azure-first
Key Vault, Entra ID, AKS, Blob
Zero
Secrets stored in the platform
The problem

A notebook on a laptop isn't a production service

Production means knowing who can run what, where secrets live, how a change moves from dev to prod, what happens when it fails, and being able to prove all of it to an auditor.

How it works
  1. 01

    Publish

    Authored workflows become immutable, content-addressed versions in a registry, compiled and validated on real workers.

  2. 02

    Promote

    Move from source to destination environments with plan/diff, connection mapping, approvals, verification and one-click rollback.

  3. 03

    Operate

    Warm worker pools execute runs, with live cell-by-cell monitoring, drift detection, notifications and a hash-chained audit trail.

Capabilities

What you get

Identity & access

Local accounts plus SSO via Microsoft Entra ID, Google and generic OIDC, with SAML and LDAP planned. Roles are scoped per environment and per workflow.

Environments & promotion

Dev, QA, test, prod, or as many as you need. Each has its own setup, and changes reach it only through a governed pipeline.

Secrets stay in your vault

Azure Key Vault first, then HashiCorp Vault, AWS and GCP. Credentials are never stored in the platform.

Isolated execution

Pooled, warm workers partitioned by tenant and environment. Workers are never shared across environments.

Tamper-evident audit

A per-tenant, hash-chained, insert-only audit log, plus Prometheus/Grafana metrics and Teams/email notifications.

Deploy where you operate

Docker Compose today, Azure AKS as the first production target, then OpenShift, generic Kubernetes and air-gapped sites.

Where this fits in the suite

Runs the Data OS engine as-is. It extends the core, it doesn't modify it.

In build · Design-partner access

Run it like infrastructure, with us.