About North Castle Ventures
North Castle Ventures sponsors, owns, and underwrites the conversion of underutilized subterranean real estate into sovereign compute nodes for regulated enterprises. We assemble the capital, the building physics, and the operating partners so that data boundaries are enforced by structure rather than by software policy.
Executive summary
Frontier AI has an appetite that commercial buildings were never designed to serve. High-density inference wants dense power, liquid heat rejection, acoustic isolation, and a defensible data boundary. The commercial stock that regulated firms actually occupy — well-located, architecturally significant, conventionally serviced — offers none of those things without deliberate intervention.
North Castle Ventures exists to close that gap on the real estate side of the ledger. We acquire and steward buildings where the intervention is economically rational, underwrite the conversion against a disciplined yield-on-cost model, and coordinate the partners who deliver and operate it. The result is a building that can host regulated AI workloads without asking its tenants to export their data to a shared environment.
We are the sponsor and owner of that infrastructure — not its software vendor, and not its installer. That separation is deliberate, and it is the basis of the tenant protections described below.
The problem we solve
Regulated institutions have not been slow to adopt AI because they misunderstand it. They have been slow because the delivery model conflicts with obligations they cannot renegotiate. Four constraints recur across quantitative finance, healthcare, legal, and M&A practices.
01
Once a prompt containing client identifiers, deal terms, or protected health information leaves the tenant boundary, the control question stops being technical and becomes evidentiary. A contractual assurance is not the same artifact as a demonstrable boundary, and examiners increasingly ask for the latter.
02
Round-tripping to a distant region is tolerable for drafting and intolerable for anything sitting inside a trading, diligence, or clinical decision loop. Round-trip distance sets a floor no amount of software optimization removes.
03
Pricing models that meter data leaving the environment quietly tax the firms whose corpora are largest and most proprietary — precisely the firms with the strongest reason to keep that corpus in place.
04
Multi-tenant inference means the hardware executing the workload is not in the tenant’s possession. For institutions whose obligations attach to custody, an access-control setting is not a substitute for title and physical control.
Each of these is an architectural constraint, so each requires an architectural remedy. Adjusting a data-handling policy does not shorten a fiber run, and no configuration setting places a GPU inside a tenant's custody. That work happens in the building.
The platform
Physical sovereignty, thermodynamic economics, and financeable underwriting are one system. Remove any of the three and the asset either fails compliance review, fails the energy model, or fails to clear its cost of capital.
Pillar 01
The boundary is built, not configured.
Suites are converted into acoustically and electrically isolated enclaves so that inference hardware can sit inside the tenant’s own premises. Tenants hold title to the silicon; the landlord provisions the shell and has no path to the compute or the data on it.
Pillar 02
Waste heat is an asset the building already needs.
Direct-to-chip liquid cooling rejects heat into building hydronics and driveway snow-melt loops rather than into the atmosphere, which converts a cooling liability into displaced heating load. Rooftop solar and battery storage buffer the demand profile.
Pillar 03
The conversion has to clear a hurdle, not a narrative.
Conversions are underwritten on dynamic yield-on-cost, with base rent set so the incremental capital clears a defined cash-on-cash hurdle. The model stands on tenant demand and displaced operating cost — it does not depend on speculative state grants. PropCo and OpCo responsibilities are separated at the lease.
Reference site
Node 01 occupies subterranean Level P1 beneath the Armonk Professional Center campus at 355 and 357 Main Street. Below-grade space is the natural home for this programme: it is thermally stable, structurally capable of carrying dense equipment loads, acoustically remote from tenant floors, and — in most office assets — dramatically undervalued relative to the rent it can support once converted.
The node serves as the reference implementation for the underwriting and engineering model described on this page, in a market whose tenant base skews toward regional financial and healthcare institutions. It is the site where the design targets above are being proven in place rather than argued in the abstract.
357 Main Street is fully leased. Suite availability and tours for the campus are handled by the property teams, not by North Castle Ventures.
Roles & boundaries
Sovereignty is a legal and operational structure before it is a technical one. Each party is deliberately isolated so that no single entity holds both the building and the data — which is what allows a tenant to retain custody of its own intellectual capital.
Sponsor & owner
Acquires and stewards the real estate, underwrites the conversion, assembles the capital, and coordinates the ecosystem. Provisions the shell — power envelope, network conduit, isolation — and holds no path to tenant compute or tenant data.
No data access
Property manager & delivery
A wholly owned subsidiary of North Castle Ventures, responsible for the buildings, power, fiber, and property infrastructure. It also owns the consultation-led path: assessing a candidate building or suite, documenting constraints before commitment, and performing conversion work across voltage, fiber, cooling, security, and hardware.
Assessment-led scope
Software operator
Operates Nate — Native Agentic Technical Engineer — and the sovereign operating environment, entirely at the software layer. Built by TruCast and North Castle Ventures. No access to inference data, un-redacted prompts, or outputs.
Software layer only
Technology partner
Technology partner to NativeAgentic, extending the operating layer toward a decentralized network of localized compute nodes so that enterprise tenants can deploy in their own suites rather than in a shared facility.
Network reach
The standard is developed in the open — read the AI-Native Office RFC
Engagement
Every path begins with an assessment rather than a commitment. Assessment and delivery are conducted by Sovereign Shells; a diagnostic informs a decision and does not guarantee regulatory, technical, lease, or operational suitability.
Commercial landlords
Establish whether below-grade or underutilized space in your asset can support a conversion that clears the yield-on-cost hurdle. Begins with a documented assessment of constraints, before any commitment.
Request a landlord assessmentEnterprise tenants
For quantitative finance, healthcare, legal, and M&A practices that need inference to run inside their own boundary, on hardware they hold title to. Starts with a tenant diagnostic of your suite and workload profile.
Start a tenant diagnosticCapital partners
For partners evaluating the asset class: the yield-on-cost model, the lease structure separating PropCo from OpCo, and the reference node economics that inform the wider pipeline.
Request the underwriting modelSTC-55 isolation, 100% heat-reclaim routing, and the 110–130°F fluid return are engineering design targets for Node 01. The 13.5% cash-on-cash hurdle and the $2.7M+ equity lift are underwriting assumptions from the sponsor's financial model. Figures are stated as modeled and scoped to Node 01 as of August 2026; they are not measurements of delivered performance and do not constitute verified results.
Acoustic performance, electrical capacity, cooling capacity, fiber state, and dedicated IP provisioning are confirmed per building and per suite through a documented assessment, and depend on carrier, network, security, site, and lease conditions. “Zero egress” describes an assessed technical configuration for a specific suite, not a default condition of any property. Verify current status before relying on any figure on this page.