P9 statusPrivate evaluation program // Technical intake open

Release notes Documentation Subscriber access

P9 // Network Simulation System

Control the conditions.

Shape latency, loss, jitter, bandwidth and packet behavior. Replay the same conditions. Compare outcomes with evidence before deployment.

Controlled experiment specimenIllustrative condition values

Scenario: 09 // Edge instability

Baseline: Run A // Nominal

Condition: +80 ms · ±12 ms jitter · 2% loss

Replay: Channel armed

Evidence: Awaiting controlled run

Run A // BaselineRun B // Controlled

Explore the system Review Evaluation Intake

Condition replayOutcome comparisonControlled emulation

Perceive. Adapt. Evolve.

01 // Controlled experiment

Repeat the condition. Preserve the evidence.

P9 turns an unstable network variable into a controlled experiment: define the condition, repeat it through a profile, compare the outcome and retain the operational evidence.

Condition definedSet the impairment boundary.
Baseline observedObserve nominal behavior.
Profile appliedActivate reusable policy.
Condition replayedRepeat the same condition.
Outcomes comparedInspect outcome differences.
Evidence preservedRetain traceable evidence.

Run A // Baseline

Nominal condition

System state is observed before a network profile is applied.

Run B // Controlled

Profile active

The same explicit condition can be replayed and compared without claiming a fabricated benchmark result.

02 // Platform systems

One command continuum. Four operational systems.

P9 connects packet conditioning, repeatable profiles, operator context and control integrity in one Windows-native network simulation system.

Condition engine

Shape packet behavior

Build controlled conditions for the network variables that reveal fragile system behavior before deployment.

LatencyJitterLossThrottleReorderingDuplication

Replay and compare

Repeat conditions with evidence

Capture reusable profiles, replay explicit conditions, compare baseline and controlled outcomes, and preserve versioned recall.

ProfilesRepeatabilityBaselineComparisonEvidenceRecall

Operator intelligence

See system state in context

Unify vitals, events, process activity and operator actions with concise contextual PARADIGM guidance.

VitalsEventsProcessesActionsContextGuidance

Control integrity

Keep advanced control observable

Safety gates, watchdog behavior, recovery paths and traceable decisions preserve evidence as the platform evolves.

Safety gatesWatchdogsRecoveryTraceabilityAudit evidence

03 // Product interface

Operational control belongs in an authentic surface.

Authentic P9 interface walkthroughs are delivered through release documentation and technical evaluation. This public surface identifies verified control domains while the application remains evaluation-gated.

Evaluation-gated control topology

Illustrative public surface

Profile: Edge instability

State: Staged

Evidence: Awaiting replay

Safety gate: Armed

Review the operational interface with technical context.

Authentic application walkthroughs are presented during evaluation so condition controls, profiles and evidence can be understood without substituting a product screenshot.

04 // Signature preset concept

Don't FallCliff control

A stability-focused preset concept intended to hold performance near a tuned operating boundary while respecting defined latency, loss and recovery limits.

Illustrative boundary topology // not performance evidence

Operating boundary

Tuned stability region

Establish the intended behavior before applying a controlled disturbance.

Observed conditions

Latency and loss state

Relate current network evidence to the active preset intent.

Safety limits

Bounded policy

Keep control behavior inside explicit gates and watchdog constraints.

Recovery evidence

Traceable outcome

Preserve the result and surface a recovery path when required.

05 // Architecture

Intent becomes observable action.

The operator, policy engine, packet path and evidence layer remain connected throughout the control cycle.

Intent

Capture the operator objective and explicit condition boundary.

Compilation

Resolve the selected profile into a bounded execution policy.

Execution

Apply network behavior through the qualified control path.

Observation

Collect host, process, network and operator state in context.

Evidence

Compare the outcome, retain the trace and surface recovery.

06 // Engineering milestones

Signing milestones, stated precisely.

Qualified user-mode release evidence, driver-signing status and theoretical research are separated plainly from released capability.

WorkstreamEngineering stateRelease gate

Azure-signed user modeClean-host qualifiedEvidence available

Packet Warp driverEngineering completeMicrosoft production signing pending

Null Point HyperPathArchitecture researchTheoretical

Engineering complete — Microsoft production signing pending.

Packet Warp Driver

An owned Windows packet-control path intended to reduce external runtime dependencies while preserving lifecycle safety, recovery and traffic parity. Microsoft has not endorsed or production-signed Packet Warp.

Architecture research // Theoretical

Null Point HyperPath

A research direction exploring compiled immutable policies, per-core workers, adaptive batching and lower-overhead packet decisions.

07 // Launch plans

One system. Four ways to operate.

Start as an individual, scale into a team or deploy across an enterprise fleet. Annual plans include twelve months for the price of ten.

Individual

Personal

For creators, learners, enthusiasts and individual developers.

$390/ year

$32.50 effective monthly
12 months for the price of 10

1 person and 2 active devices
Local impairment and scenario control

Independent professional // Recommended

Professional

For QA engineers, consultants, researchers and developers.

$990/ year

$82.50 effective monthly
12 months for the price of 10

1 person and 5 active devices
Local automation API and report exports

Team / Studio

Team

For product teams, test labs and independent studios.

$4,990/ year

$415.83 effective monthly
12 months for the price of 10

5 people and 15 active devices
Shared profiles and hosted automation API

Organization

Enterprise

For departments, larger fleets and security-conscious organizations.

$24,990/ year from

$2,082.50 effective monthly from
12 months for the price of 10

25 people and 100 active devices
Fleet controls, SSO and audit access
Deployment and support options by agreement

Launch-candidate pricing before applicable tax. Annual plans save 16.7%. Access, billing, downloads and service commitments activate only after applicable release, identity, security and agreement gates are complete.

08 // Technical evaluation

Evaluate P9 with technical context.

Paradigm is preparing P9 for broader availability. Current discussions focus on Windows deployment needs, controlled network-testing workflows, technical fit and release readiness.

01Define the operating need
02Review qualification evidence
03Plan the evaluation path

Review Evaluation Intake Review documentation