Keep the data, weights, and decision history inside your boundary
CISOs are accountable for data movement, model access, auditability, and exit risk. Nodes runs single-tenant inside the customer VPC, with zero customer production-data egress and customer-owned weights. It starts with one bounded decision program. Every recommendation carries a signed Decision Trace, and a named human approves, edits, or declines before Nodes acts.
The deployment boundary is explicit
Nodes runs inside a customer-controlled AWS, Azure, or GCP environment. Fine-tuning, inference, deployed customer-specific weights, Decision Traces, and approved actions stay inside that boundary. No hosted foundation-model API sits in the production data path. Customer production data and deployed model artifacts remain inside the approved environment.
The customer keeps its data, deployed customer-specific weights, decision history, and the assets defined in the agreement. If the executed agreement permits shared improvement, a PII-stripped weight artifact may leave only after two PII checks and explicit customer approval. Optional aggregate operational telemetry contains no customer data and can be disabled. Neither path carries customer production data. Exact export formats, transition support, and release mechanics belong in the contract. Ownership and exit rights are reviewable before production.
Integration has a stop condition
Nodes uses templated connectors for systems enterprises already run. An internal glossary defines the canonical schema. The mapping layer matches discovered fields to that glossary with confidence bands, and a human verifies anything uncertain. A renamed or drifted field stops flowing instead of being guessed at.
That mechanism gives the platform team four concrete review points:
- the connector permissions and data paths
- the proposed field mapping and its confidence
- the human acceptance record for uncertain mappings
- the behavior when a schema changes or a source becomes unavailable
Every recommendation carries its evidence
A signed Decision Trace records what happened, where, why, which model and policy versions were used, what input a human gave, and what action followed. A named human approves, edits, or declines before execution. Designated regulated workflows can require a second signer.
The trace gives security, model-risk, legal, and internal-audit teams one queryable record. It does not claim that architecture alone creates legal compliance.
One deployment, with clear limits
At one Fortune 500 insurance carrier, six AI hiring vendors had been rejected over 18 months on architecture. Nodes completed legal approval in 17 days.
The same deployment moved from contract to production in 34 days. These are results from one deployment, live since January 2025. They are evidence of the mechanism, not a timeline promise for another environment.
Frequently asked questions
Why buy this if the data team has already joined the systems?
A joined dataset solves retrieval. Nodes adds continuous reasoning across systems, a proposed workflow with ROI attached, a human approval gate, execution across approved systems, and a signed trace of the decision. The build-versus-buy question is whether your team wants to own and maintain that full loop.
Does fast integration mean controls were skipped?
Ask to inspect the mechanism. Templated connectors, confidence-banded mapping, human verification of uncertain fields, scoped permissions, and a stop on schema drift explain the speed. The 17-day and 34-day results remain one-deployment evidence.
What happens if the relationship ends?
The customer retains its customer-specific model weights and decision assets as defined in the agreement. The Nodes software license, agent operation, connector maintenance, monitoring, updates, and support end according to the contract.
Replay one decision inside the proposed boundary
Bring one repeated decision, the systems it crosses, the outcome you measure, and the security constraints that govern it. Nodes will map the data path, evidence requirements, human gate, and stop conditions before a production scope is proposed.