nQube designs it. agentOS commits it. An agent is something else.

Three names get mixed together. They are three different things, and each has its own page. Demos use synthetic data. Buy on Pricing.

Design and runtime

nQube is where a workflow is designed, and it comes with Platform. agentOS commits that workflow only after a gate, and only inside a capability you declared.

nqube.nventr
run start · 3 documents in

nQube

The canvas where a workflow is designed — blocks, data, gates — before agentOS is allowed to run it.

Walkthrough →
runtime · agentOS
erp.postadmin.bypass
INV-20841waiting
Manifest lists erp.post. admin.bypass is not callable.

agentOS

The runtime. The model proposes. A gate decides. Only agentOS commits — and only inside a manifest you declared.

Walkthrough →

Agents

Agent IO is where you define the agent: voice, what it may read and propose, and how the launcher looks. nventr Agent is that definition on a page you already have — a script, an iframe, or the API. A coordinator block can run several Agent IO roles. It still cannot commit.

agent-io.nventr
support-intake
Answer from projects and pipelines. Creates wait for a person.
read · projectread · pipelinepropose · pipelinepropose · workload
script · iframe · API

Agent IO

Where an agent is defined — voice, access, look — and where a coordinator pulls several of those roles onto one objective. One of them, on a page, is nventr Agent.

Walkthrough →
embed · nventr agent
nventr Agent · support-intake
Set up a pipeline for vendor invoices.
I can propose it. I can’t create it until you confirm.
Propose · pipeline · invoice-intakeConfirm

nventr Agent

One conversation on a page you already have. Script, iframe, or API. It proposes. A person confirms.

Walkthrough →

Capabilities

What the runtime did, where data comes in, who gets told, and deploys, health and logs.

athena.nventr
done82%gated11%error7%

Athena

Live numbers for the work the platform ran — runs, gates, errors — and a path from a chart down to one event.

Walkthrough →
listen.nventr
postgresorders_prod⇄ syncing
s3archive-2026✓ synced
apisalesforce✓ synced
filesclaims batch✓ synced
12 datasets · 4 live connections

Listen

Datasets and live connections, registered once, used by reference everywhere else.

Walkthrough →
reachout.nventr
slack #opsalert · error rate 2.1%✓ delivered
email finance@invoice INV-20841 posted✓ delivered
webhook erppayload · 214 rows✓ delivered

Reachout

When a workflow decides, the right person or system hears about it.

Walkthrough →
devops.nventr
api-gatewaylive
agent-runtimelive
pipeline-workerslive
99.98% · 30d

DevOps

Releases, environments, health and logs for the apps and workloads you run — up is not the same as working.

Walkthrough →

App Kit

A separate product. Dev Console builds and deploys an app, and it requires App Kit — it is not included at $15. The instance under that console is the URL, the database, and the layer repo.

instance /dev
Plangate the $10k hold
Diffwaiting
Previewwaiting
Deploywaiting
Requires App Kit

Dev Console

Requires App Kit. The build-and-deploy console on that instance. The agent works your layer. You preview the change and ship it from /dev.

Walkthrough →
How the instance works →

A workflow on Platform

Invoice intake is a gated pipeline into systems you already use. An app people log into is App Kit, not a module.

idp.nventr
vendorAcme Industrial
invoice #INV-20841
amount$12,480.00
dueOct 14, 2026
Solution

IDP — Intelligent Document Processing

Pretrained neural-network workflows for high-accuracy document extraction at scale: invoices, claims, contracts. Extraction agents propose, gates hold anything above policy thresholds, and only the runtime posts to your systems of record.

What’s new

Start on the systems you already use

Start is $15/mo · 1 builder · 3,000 workflow runs. The free canvas has no production runs. Standing up the first pipeline with us is a separate delivery.