NodeFox
NodeFox for enterprise

Put a defined workflow into production.

Connect AI, applications, code and human decisions in executable graphs that your teams can inspect, operate and extend. Establish a valuable first workflow, then reuse the platform across processes with clear ownership and deployment responsibilities.

Agree before implementation

A production decision needs more than a working demo.

Start with one recurring process and the people accountable for it. Agree what success means before extending automation into operational systems.
A bounded workflow
Name the trigger, systems, input variants, permitted actions and cases that remain with people.
Evidence of value
Compare hands-on time, rework and elapsed time against a baseline. Include implementation, software, provider and support costs.
An operating owner
Agree who maintains access, reviews changes, handles failed cases and decides whether to add the next workflow.
Ownership

The owner changes the rules. Operators work the cases.

The process owner keeps one visible place for checks, routing and thresholds. The people handling cases get an app: a form, a result and the decisions that are theirs to make.

Operations / Claims intake
RORevenue Opsbuilds
Publishv3v3^v4
Apps / Claims Intake
v3v4
Ticket*
claim-4821.eml
Queue
Claims triage
RunSASalesrunsRunning on v4
Responsibilities

Who does what in an engagement.

NodeFox

Builds the first workflow with you

Within the agreed implementation scope, against your rules and cases.

Connects the systems in scope

Through their APIs or exports, listed in writing before work starts.

Documents the behavior

Normal, exception and error paths, and where people decide.

Provides the platform and agreed support

Under the terms of your agreement.

Your team

Names a process owner

Who decides what a correct outcome is and owns the rules.

Provides access

A technical contact for credentials, exports and, for headless, a host machine.

Reviews the exceptions

The people who already make these decisions keep making them.

Agrees the baseline

Today’s numbers, so the implementation is measured against something real.
Deployment

Choose where the workflow runs.

Review and build in the browser. Export compatible workflows to a supported headless machine you control. Confirm each connection and the operator response path before unattended use.

Deployment options
Browser
Headless Pro & Enterprise
Runs on
The browser session of the person running it
Your Linux or macOS machine, as a background service
Starts from
A person, an app form or a batch
Command line, schedule, watched folder or webhook
People decide
In the NodeFox app, when a run awaits input
From the operator’s terminal or an attached agent
Suited to
Building, reviewing and attended work
Unattended volume on a schedule or trigger
Run records

Inspect the work, not just the answer.

Inspect a recorded run in the app without repeating its actions. Headless runs keep their record on the machine that ran them, and Enterprise can stream run records, encrypted, to your organization.

Expansion

The next workflow can reuse the foundation.

Integrations, checks, approval patterns and whole sub-workflows are reusable. Order exceptions lead to invoice reconciliation; client onboarding leads to account changes. Assess each new workflow on its own value and integration effort, reusing the parts that fit.

From pilot to production

A deliberate path, with a decision at each step.

  1. 01

    Map one workflow

    A conversation on what arrives, what gets checked, where exceptions appear and who signs off.

  2. 02

    Scope and baseline

    Agree the inputs, systems, review points and the current numbers we will measure against.

  3. 03

    Paid pilot

    The workflow runs on your real or anonymised cases, with a written scorecard at the end.

  4. 04

    Production and the next one

    Agree operating ownership, recurring platform and support scope. Measure use and value, then evaluate the next workflow.

Commercial paths

Agree the right scope for adoption.

Validate an uncertain implementation through a paid pilot. When feasibility and value are established, scope production access, responsibilities and support.

Deploy an operational workflow

Start with a workflow conversation. Agree the systems, expected value and responsibilities before choosing the implementation path.

Paid pilot

Use a bounded scope and representative cases to validate feasibility and value.

Direct production

When fit is established, agree implementation, recurring access and operating ownership.

Will this replace our current systems?

No. Your ERP, CRM and case systems stay the systems of record. NodeFox does the work between them and writes approved results back.

Can it run unattended in production?

Supported headless workflows run on your own Linux or macOS machines, from a schedule, folder watch or webhook. Confirm node compatibility and how human decisions will be handled before deployment. Headless execution is included with Pro and Enterprise.

Who owns the workflow after the pilot?

Your process owner maintains the rules; the workflow is visible and editable rather than locked in code only we can change. Licence terms are set in the agreement.

Do you support security reviews and questionnaires?

Yes. We share the security overview, DPA and technical brief, and answer questionnaires during scoping. We don’t hold SOC 2 or offer SSO today.

Start with one workflow, an owner and a number to beat.

Bring a recurring workflow or deployment plan. We’ll discuss systems, controls, ownership and whether to scope a pilot or proceed directly to implementation.