Nodes and Internal build with Anthropic
Which product responsibilities does buying eliminate?
An internal team can start with a managed agent runtime rather than a bare model API. Evaluate Nodes on the company-specific product, implementation work, and ongoing operating responsibilities the agreed scope can take off that team's backlog.
Where Internal build with Anthropic fits.
Consider an internal build when the workflow is strategically distinctive, your team wants direct control of its implementation, and you can staff product ownership and ongoing operations. Existing internal integration and data capabilities belong on the asset side of the comparison.
Why evaluate Nodes alongside it.
Buying Nodes should reduce a specified set of implementation and operating responsibilities. Ask us to name those deliverables and demonstrate them. Company intelligence, usable review screens, source permissions, recovery, and outcome evaluation still need an owner in either option. Our broader adaptive runtime is product direction; it cannot be counted as delivered engineering savings.
What the current product materials establish
These are vendor descriptions, not performance ratings. Fit recommendations above are our assessment of those materials.
- Claude Managed Agents is in beta. It provides a managed harness with tools, long-running and stateful sessions, and scheduled execution. Environments can use an Anthropic-managed or self-hosted sandbox. Claude Managed Agents overview.
- Self-hosted sandboxes move tool execution to customer infrastructure; tool inputs and outputs still flow to Anthropic's control plane. Review the complete model, memory, and tool boundary for the intended use. Claude Managed Agents self-hosted sandboxes.
Production evidence and product direction have different jobs.
Inspect the existing application.
Public production evidence is limited to insurance talent at one Fortune 500 carrier. It includes $1.58M in Q1 2025 net savings validated by the customer's CFO. That figure is not an independent audit or a benchmark against this alternative.
Read the evidence registerRead the separate research methodology
Test the broader responsibility.
Dynamic capability creation, the general autonomous runtime, and automatic outcome learning are product direction. A concept diagram or insurance result does not establish that this full system is deployed. Agree on what is available, what needs configuration, and what must be demonstrated.
Review the platform and statusTake an unfamiliar problem through the result.
Illustrative evaluation: reconcile an unfamiliar operational document, then investigate a related workflow exception using the same permitted company context. One task may need only one tool.
Inventory what you already have
Credit existing connectors, schemas, agent tools, controls, and internal expertise. Identify the missing product responsibilities.
Run the same unseen cases
Compare correct outputs, missing evidence, permission boundaries, human edits, and verified effects on the same test set.
Exercise the operating burden
Change a source schema, interrupt a run, and update the model. Record the testing, repair, and customer intervention needed.
Test durable usefulness
Inspect the later case with and without a prior applicable lesson. Confirm that evidence remains traceable and unrelated work does not regress.
Use an authorized test environment. Record engineering hours, customer interventions, completion quality, and the applicability of retained learning. Compare with a prior or no-memory baseline where appropriate. Approval permits work; it does not prove the result.
Put the operating and exit terms in writing.
- Compare license and implementation fees with staffed product ownership, infrastructure, model use, evaluations, and continuing maintenance. Do not treat internal salaries as free.
- Separate the cost of the first working task from the cost of a supported product with review, support, recovery, and outcome-history surfaces.
- Identify customer-owned code and intelligence, vendor intellectual property, third-party licenses, and usable exports for each option.
Nodes scopes the agreed business process. Additional agents, steps, or refinements inside that scope do not automatically add a charge; material expansion is agreed first. Include implementation, infrastructure, support, and retained customer effort in the evaluation. Review pricing scope.
Deployment can use Nodes Cloud, a single-tenant customer VPC, or customer-managed on-premises infrastructure. Verify the actual model and connector paths. Customer ownership of separable intelligence does not mean indefinite free use of Nodes' licensed runtime. Agree on formats, provenance, retention, and transition support. Inspect the security and ownership questions.
Start with a product walkthrough.
Bring the responsibility, current systems, and the result you want to improve. No dataset is required for the first conversation. Historical Decision Replay remains a separate validation offer with its own data requirements and written terms.