Which decision needs attention?
Bring one business question and its accountable owner. See how Nodes takes the company knowledge your people built and uses it to investigate, compare responses and carry out approved work.
First decision brief
Review the scope and termsScope one question with its owner. Review what Nodes found, missing evidence, possible next steps and estimated costs of acting or waiting before deciding what to implement.
Security review
Open the security pathAsk for SOC 2 Type II materials, deployment architecture, data-flow details, or a questionnaire response.
Press and partnerships
Send an inquiryUse this path for analyst briefings, integrations, events, and channel discussions.
Start with one question.
Our team replies from a nodes.inc address to arrange the conversation. We show a relevant example and discuss the owner, available evidence and starting measure. You can explore Nodes before preparing data or connecting systems.
Nodes is enterprise AI software that runs on a company-owned context graph. That graph holds what your people learned doing the work, so you can change models and agents without losing your decision history and outcomes. The walkthrough shows how records, prior decisions, human judgment and relevant external developments inform a recommendation you can question.
- A renewal risk that needs a response.
- A handoff causing repeat requests.
- A partner change that may affect your process.
The boundary is clear before data moves.
Your security and data owners agree the deployment model, access, and approval controls before systems are connected.
Questions about the first step.
A walkthrough helps you understand the product and choose where to begin.
01What should I send in the first request?+
Your name, work email, and company. Your role or business area and a sentence about the work are optional. Do not send production data through this form.
02Do we need a dataset to see Nodes?+
No. The product walkthrough and first-use-case discussion require no dataset or connected systems. Data access is agreed separately if you choose to proceed.
03Can we test Nodes on our own history?+
Yes. Decision Replay is a separate read-only evaluation with data-sufficiency requirements and a written evidence bar. Read the eligibility, data requirements, and commercial terms. A walkthrough does not start or commit you to a Replay.
04What does the first decision brief cover?+
Setup typically takes 1-2 weeks. Within 72 hours of complete agreed data access, receive findings, evidence gaps, options, estimated action and inaction costs, and recommended next steps. Implementation is separately scoped and scheduled. Review the paid decision brief and its terms.
05Where does data live after deployment?+
Nodes Cloud uses a Nodes-managed boundary. A single-tenant customer VPC or customer-managed on-premises deployment uses your approved private boundary. These private configurations can enforce zero customer production-data egress. Review the platform architecture and security posture.
06Who approves the actions?+
Before work starts, agree what each person and assigned agent may access, recommend and change. Your named reviewers control consequential decisions and required approvals. Current permissions govern work; prior approval is context.
Start with the question your team owns.
See how company knowledge informs a recommendation, how people challenge it and what an owner controls. Then discuss a scoped first decision brief.