Put cross-system processes into software you can operate.
Build workflows across APIs, code, models, files and people. NodeFox makes the data flow, conditions and execution visible, so your team can configure, test and maintain the process.
Illustrative interface with synthetic data; see the recorded product walkthrough on the demo page.
Make dependencies and action boundaries explicit.
NodeFox brings model tasks, exact code, system calls and human decisions into the same executable graph. Compare the approaches on data contracts, action boundaries, operator access and the work required to maintain a deployed process.
The graph is the program.
Typed data between steps.
Predictable execution.
Composable.
Is NodeFox the right approach for this process?
Keep a working automation when it solves the problem. These approaches overlap and can work together; compare the whole process and its operating requirements, not just the first successful task.
- Existing automation
- A defined trigger and supported actions may already solve the whole task.
- Check how it handles the dependencies, exceptions and review boundaries your process requires.
- AI agents
- Useful when the task needs flexible interpretation or tool selection.
- Decide which steps can be delegated and which actions need exact checks and explicit authorization.
- Custom code
- A good fit when a team wants direct control of a specialized integration or service.
- Account for the operator interface, run visibility, change ownership and ongoing maintenance.
- NodeFox
- Useful when one process combines model tasks, exact rules, multiple systems and human decisions.
- Express these in an executable graph, then validate connection access, failure paths and the deployment environment.
A process-level selection guide, not a feature comparison of particular vendors. Implementation capabilities vary.
Attended in the browser. Unattended headless.
The Rust runtime underpins both modes. Export workflows whose steps and connections are supported by the runner; browser MCP and OAuth steps do not transfer automatically. Headless execution is included with Pro and Enterprise.
# deploy the exported App or Automation $ nf deploy po-exceptions.nfx # weekdays at 9:00, in your timezone $ nf dispatch po-exceptions --schedule "0 9 * * 1-5" --tz America/Chicago # background service; restarts if it crashes $ nf service install # inspect, follow or answer runs $ nf runs
Where the decisions and the records live.
Gated side effects
Writes and sends fire only after the condition or sign-off wired in front of them.
Human decisions
A run pauses as “awaiting input” at the step you choose and continues on the answer.
Run records
Each run records what executed, what it produced and how it ended, including failures.
Your keys, your providers
Model requests go to the provider you configure with your keys; headless keys stay on the runner machine.
Through the access your systems already offer.
REST APIs, files and exports, watched folders, webhooks into the runner, JavaScript code steps, and MCP servers in the browser. Systems of record connect through their APIs, scoped per engagement.
- SSO / SAML
- SOC 2 or ISO certification
- Windows and Intel Mac runners
- MCP and OAuth steps in headless runs
- Prebuilt ERP, CRM or WMS connectors (we connect through their APIs)
Walk through the architecture with the people who built it.
Bring the workflow and the systems it touches. We’ll show where it would run and what it needs.