Private Edge

Private autonomous systems. Inside your boundary.

Edge keeps sensitive data, retrieval, credentials, and tool execution local on an NW Agentic-managed appliance. It connects outbound only, with no inbound ports and content-minimized evidence.

Talk with us See architecture
Who this is for

Operators with a hard data-residency boundary.

Regulated trades

Professional services, healthcare-adjacent, finance — anywhere a "the data left our network" finding ends a contract or a license.

Sensitive document workflows

Drafting and review against confidential client documents that cannot leave your premises in raw form.

Sovereignty-critical operations

Workflows where the privacy boundary is contractually or statutorily at the firm, not at a SaaS perimeter.

What's included

Appliance, platform, and operations — under one contract.

Secure on-prem appliance — NWA-provided hardware, NWA-managed remotely. No inbound ports exposed.
Local RAG retrieval — pgvector-backed semantic search runs on the appliance. Only chunks leave for cloud inference.
Outbound-only mTLS — appliance speaks to the NWA control plane over a tunneled mTLS connection. No inbound surface.
FileVault-equivalent disk encryption — enforced via MDM. Recovery keys escrowed with NWA.
Self-healing supervisor — five-stage automated recovery; eliminates 90%+ of onsite visits.
Same platform safety net — per-firm budget cap, per-job ceiling, audit log per step.
Tailored system design — same Forge-style design, build, and evaluation pass, then deployed to your appliance.
Direct engineering line — your workflow lead is one Zoom away.
Architecture

The privacy boundary is at the firm.

Documents stay on the appliance. RAG retrieval runs locally against your indexed data. Only the chunks that match a query are passed to a cloud LLM for reasoning. Full document content never crosses your network boundary.

The control plane sees workflow audit metadata — IDs, tokens, timestamps — for ops visibility. It does not see raw content.

Read the full architecture →

Operating model

What you operate. What we operate. What the appliance handles.

NWA does

  • Provide and ship the appliance
  • Workflow design, build, and evaluation
  • Remote management — updates, patches, recovery
  • Cloud control plane (NWA-managed)
  • Customer support — direct engineering line

You do

  • Provide power and outbound network access
  • Approve the workflow design
  • Index your documents into local RAG
  • Configure budget caps and review thresholds
  • Review and act on outputs

The appliance handles

  • Local RAG retrieval (pgvector)
  • Workflow execution with audit logging
  • Self-healing — five-stage recovery
  • Outbound-only mTLS to control plane
  • Disk encryption and key rotation
Priced for the system you operate
Private infrastructure, capabilities, evaluation, and ongoing operation are priced together.
Talk with us
FAQ

Common questions about Private Edge.

What is the on-prem appliance?

A secure compute appliance NWA provides and manages, installed at your premises. It runs the autonomous systems locally. Only outbound mTLS connections to the NWA control plane are made. No inbound ports are exposed.

What data leaves the premises?

Full documents do not. RAG retrieval runs locally against your data; only the chunks relevant to a query are sent to a cloud LLM.

Audit metadata flows to the control plane for ops visibility — workflow id, agent name, token counts, timestamps. Never raw content.

Who manages the appliance?

NWA does. Updates, patches, and recovery are remote — over outbound-only mTLS through the control plane. Onsite intervention is the last of five recovery stages and is rare by design — our target is to eliminate 90% of onsite visits.

How is Private Edge priced?

Price reflects system scope, private infrastructure, customer-scoped capabilities, evaluation, usage, and ongoing operation. We define the run-rate before you commit.

What if the cloud LLM is unreachable?

Workflows that depend on the cloud LLM pause and retry with backoff. The watchdog supervisor escalates through five recovery stages: container restart → daemon restart → OS reboot → optional power-cycle → critical alert to a human operator.

Can the same system move between Forge and Edge?

Yes. The compiled system definition is portable. Placement is bound in a reviewed deployment release, so capabilities can move without becoming a different product.

Map your private workflow in 30 minutes.

Free discovery call. We'll outline appliance specs, workflow design, and the data-residency boundary for your operations.

Talk with us