Continuity and Trust
Every serious enterprise buyer asks this question. It is the right question. This page is the answer, in plain language. Procurement and risk committees can read it start to finish in ten minutes.
REDLINE inference runs on dedicated infrastructure under No Human Nearby's exclusive control. If the vendor is impaired, the Sovereignty Preservation Clause activates a dual-jurisdiction software escrow and the Failsafe Activation Continuity Plan keeps your in-flight reviews accessible while you take over operations. Continuity is mechanical, not a verbal promise.
In a traditional SaaS arrangement, the product lives in a multi-tenant cloud the customer never controls. When the vendor sunsets, the product vanishes, usually with the customer's data and zero recovery path.
REDLINE inverts that exposure with three structural layers:
Formerly called the Acquisition Poison Pill, the Sovereignty Preservation Clause is the contract language that prevents an acquiring tech giant from quietly migrating your privileged data onto their multi-tenant cloud. The covenant fires on any of the following:
When any trigger fires, both escrow legs release the deposit to active paying customers, and the architecture is contractually frozen against re-platforming onto a multi-tenant pool.
Single-jurisdiction escrow has a single point of failure: a US-only agent can be enjoined, frozen, or compromised in a way that prevents release. The Dual Escrow Covenant closes that gap by default in every REDLINE enterprise contract. Two agents, geographically and corporately distinct, each hold an identical quarterly deposit. The second agent activates if the primary is unable to perform.
Specific trained model weights and proprietary prompt libraries. These are the competitive how of the product and remain No Human Nearby intellectual property. The deposited training pipelines give you everything needed to produce your own trained models on your own data if you ever need to operate independently.
A royalty-free internal-use license to the deposited source code for the full duration of your continued operation of REDLINE. Self-hosted operation, internal patching, and continued use on customer-provisioned infrastructure are all permitted. No redistribution rights, no resale rights, no commercial re-licensing.
No Human Nearby. Both agent fees (typically $1,500 to $3,000 per year for the primary, $2,000 to $4,000 per year for the second jurisdiction) are absorbed as operating expense. Cost is not passed through to customers. Default for new contracts; existing contracts amend at next renewal at no additional charge.
The hardest enterprise question is not "what happens if the vendor sunsets" but "what happens during the transition window between trigger and customer self-host." The Failsafe Activation Continuity Plan documents that window with mechanical precision.
The primary escrow agent confirms the trigger condition (heartbeat failure, bankruptcy filing, founder incapacitation, written sunset notice, or Sovereignty Preservation Clause activation). The clock starts.
Customer access to in-flight reviews remains available in read-only mode. No new submissions, but every flagged risk, partner annotation, and audit log already produced stays accessible. The mid-audit status auto-generator captures the exact frozen state of every active deal room and packages it as an exportable bundle.
Both escrow agents release deposits to active paying customers via secure delivery. The primary release fulfills US-jurisdiction obligations; the secondary release covers any jurisdiction where the primary is constrained.
Customers stand up the deposited stack on their own infrastructure (cloud, colo, or on-prem) using the included terraform / ansible procedures. Documented runtime is 8 to 14 calendar days for a competent platform team with access to the architecture diagrams. The deposit includes a working reference deployment that runs end to end on a single Apple Silicon developer machine for validation purposes.
Customer-operated REDLINE is fully independent of NHN. The customer holds the source, the build pipeline, the training recipes, and the cryptographic keys to their own deposit. NHN's continued existence is no longer a dependency.
This is the analog of a dead man's switch on a train. The conductor stepping away does not derail the train; the brakes engage automatically and the system stabilizes for handover.
If you ever choose to migrate off REDLINE for your own reasons, you take your data with you. Full contract analysis outputs export as structured JSON and human-readable PDF. All flagged clauses, risk scores, and redline recommendations are exportable. All metadata. Full audit trail.
No proprietary binary formats. No vendor-specific encoding that would require No Human Nearby tools to read the data back. Data schemas are publicly documented.
For customer-initiated migrations, No Human Nearby provides a one-time export package at no additional charge: complete data export, schema reference document, and a 30-day support window for integration questions.
What happens to my active data if No Human Nearby goes out of business tomorrow?
The Failsafe Activation Continuity Plan executes. Read-only access to in-flight reviews continues for the first 24 hours. Within 10 business days, both escrow agents release source, build pipelines, and cryptographic keys to active paying customers. Within 60 days, your platform team is operating REDLINE on infrastructure you provision yourself. The dependency on NHN is severable by design.
Can I audit the escrow deposits to verify they are complete and current?
Yes. Both standard software escrow contracts include customer audit rights. No Human Nearby accepts customer audit provisions for both legs of the dual escrow as part of the master contract. Annual audit cadence is the default; ad hoc audits are available on customer request.
Why a second escrow agent in a different jurisdiction?
Procurement teams in three of three v6 review transcripts surfaced single-point Iron Mountain US-jurisdiction risk as the weakest link in the continuity guarantee. The second leg (typically a Swiss IP trust or Channel Islands trust company) activates if the primary agent is impaired by a corporate event, systemic breach, or US-jurisdiction legal freeze that prevents valid release. Two legs, identical deposit, identical cadence.
What if I want to stop using REDLINE for my own reasons, not vendor-driven?
You export your data in open formats, migrate wherever you prefer, and the contract terminates cleanly. No data held hostage. No early-termination penalties designed to lock you in.
Are the AI models open or proprietary?
The base models are widely available open-weight models. Training pipelines and fine-tuning recipes are part of the escrow deposit, so you can produce your own trained models on your own data if the vendor relationship ever ends. The specific trained model weights and prompt libraries that ship with REDLINE remain No Human Nearby intellectual property and are not in the deposit.
Is there a named successor if the founder is incapacitated?
No Human Nearby's continuity model does not depend on a single named successor. The dual escrow release mechanism hands customers full operational control (source code, build scripts, training pipelines, deployment runbooks, cryptographic keys) on a published timeline if the vendor is unable to continue. For intellectual property succession, applicable inheritance law applies. Mechanical escrow plus the Sovereignty Preservation Clause is more durable than a single named human, who could themselves become unavailable at any time.
For customer-specific escrow language, contract addenda, or procurement review packages covering this framework:
Email: [email protected]
A pre-signature draft of the continuity clauses is available on request.