NodeFox
The NodeFox platform

Enterprise workflows.
Executable by design.

NodeFox is software for automating multi-step business processes. Build workflows that coordinate AI, existing systems, code, documents and human decisions—then run them through one structured execution engine.

The graph is the workflow. Its connections define the information and conditions each step needs to run.

Product-derived illustration · sample process
From process to software

Define it once. Run it for each case.

Turn the steps people coordinate by hand into a reusable workflow. Keep the systems of record in place; connect the work between them.

Model the process

Choose the information, checks, decisions and actions. The visual graph defines the workflow that will run.

Design time: define and connect. Run time: execute and inspect.

Invoice reconciliation

An invoice arrives. The quantities don’t match.

NodeFox reads the document, retrieves the order and receipt, and checks the numbers. The exception reaches AP with the evidence already assembled.

Invoiced

240

Received

228

Difference

12

A person decides how to resolve the shortfall before the configured downstream action.

Illustrative quantities, not customer results.

Illustrative from invoice to approved record product demonstration
Designed workflow demonstration · sample records and simulated integrations.
Transcript and demonstration details

Illustrative execution, not a customer deployment. Narration is AI-generated. Actions and outputs depend on workflow configuration.

  1. 0–8s · The invoice and receipt disagree.

    The invoice and the warehouse receipt disagree. Before anything moves to accounts payable, someone has to reconcile them.

    INV-2048 · Northstar Supply · PO-7301 · 240 units at $18 · Invoice total · $4,320 · Received · 228 units

  2. 8–17s · Turn the handoffs into a workflow.

    In NodeFox, that work becomes an executable graph. AI reads the invoice while a Reader retrieves the purchasing records.

    INV-2048 · Northstar Supply · PO-7301 · 240 units at $18 · Invoice total · $4,320 · Received · 228 units

  3. 17–25s · Wait for the facts. Apply the rule.

    Both inputs feed an exact check. Twelve units are missing, so two hundred and sixteen dollars needs review.

    Invoice quantity exceeds receipt · 228 × $18 = $4,104 supported · Route remaining $216 to review

  4. 25–32s · A decision with the evidence attached.

    The reviewer gets the discrepancy and its evidence together. The next action waits for that decision.

    AP reviewer sees invoice + receipt · Approve $4,104 for AP preparation · Hold $216 pending receipt

  5. 32–41s · Approval releases the next action.

    Approval releases the configured Writer. It prepares the supported amount for accounts payable, and keeps the balance on hold.

    AP-2048 · review completed · Supported amount: $4,104 · Held amount: $216 · Payment release: separate authorization

  6. 41–49s · An approved result. A visible history.

    The result includes both amounts, the source records and the decision. Payment authorization stays separate.

    AP-2048 · review completed · Supported amount: $4,104 · Held amount: $216 · Payment release: separate authorization

  7. 49–59s · Less coordination. More completed work.

    Use the same approach for orders, onboarding and investigations. Less coordination by hand. A process you can inspect and reuse.

    AP-2048 · review completed · Supported amount: $4,104 · Held amount: $216 · Payment release: separate authorization

AI interprets

Extract the relevant information from the document.

Code checks

Compare quantities and identify the exact exception.

People decide

Review the evidence and choose the permitted next path.

Illustrative workflow film. Data access, credentials, business rules and approval responsibilities are configured for each implementation.

For builders and operators

One workflow. More than one way to use it.

Build in the visual graph or through the workflow DSL. Give an operational team an App with clear inputs, or run configured input sets through an Automation.

Give the team a clear place to start.

An input form passes named values into the configured network. People can run a process without editing its graph.

Sample input: Clause 8.2 · 30-day renewal notice · 60-day internal minimum

Learn how Apps and Automations work →
Product-derived NodeFox app view with synthetic contract-review data

Product-derived UI illustration · sample inputs and states · no live execution

Author visually or with code

The DSL creates and edits workspace assets. AI assistance can propose graph changes; inspect and test the generated workflow before use.

See authoring & composition

Connect existing capabilities

Configure models, files, API requests, custom code and compatible MCP tools. Connections depend on the selected service, credentials and execution environment.

Explore connection methods

Choose an operating environment

Run browser workflows with the Rust/WASM engine. Native headless operation requires a compatible host, configured access and a reviewed workflow. Apps and Automations depend on plan access.

Understand runtime boundaries
Where the work adds up

Automate recurring coordination.

The strongest starting point is a process with repeat volume, clear inputs and a costly handoff or exception. Measure the work before and after implementation.
01

Order & invoice exceptions

Documents and system records disagree.

Retrieve the evidence, apply exact checks and route discrepancies to the responsible person.

Measure: Manual touches · exception resolution time

02

Customer & supplier onboarding

Missing information holds up the next team.

Organize submissions, check completeness and coordinate the next configured handoff.

Measure: Time to readiness · rework

03

Document-intensive reviews

Repeated reviews consume specialist attention.

Use AI to organize clauses or evidence, apply review criteria and surface issues for human judgment.

Measure: Review effort · unresolved exceptions

04

Service & operational investigations

An answer is scattered across systems.

Assemble case context, evaluate conditions and prepare an action with its supporting evidence.

Measure: Case cycle time · throughput

Make the business case around one process.

Estimate handling effort, exception volume and cost per transaction. Recovered capacity is an opportunity to evaluate, not a promised cash saving.

Explore workflow economics
Structure that earns its place

The process stays explicit as the work gets complex.

AI handles interpretation. Code and rules handle exact checks. Dependencies coordinate the steps, and people retain the decisions assigned to them.
Explore the technology

An executable definition

The graph defines computation and control flow. You can examine the path to a result instead of inferring it from an agent’s conversation.

An inspectable run

Inspect step outputs and execution state. Recorded-run playback shows captured evidence without reissuing the original external actions.

Components you can reuse

Network nodes invoke other networks through mapped inputs and outputs. Keep repeated logic in reusable components instead of duplicating entire processes.

Scope one recurring workflowValidate systems and decision pathsMeasure outcomes before expanding

Bring a process worth improving.

Walk through the inputs, systems, exceptions and people involved. Determine whether a scoped NodeFox implementation makes operational and economic sense.