NoBS Remote

Build status · reviewed July 30, 2026

We show the work. We do not fake the finish.

NoBS Remote is in private testing across its identity, consent, lifecycle, and operating foundations.

Private testing

Stage / 01

Verified foundation

Persisted tenant/device state, protected enrollment, signed heartbeats, attended-consent authority, process/session binding, transition integrity, and bounded audit foundations.

Achieved foundation

Stage / 02

Private testing

Testing the authorization, lifecycle, security, connectivity, packaging, and operating foundations against the product's evidence gates.

In progress

Stage / 03

Founding Pilot

Selected operators help shape workflows and requirements. Testable product access begins only when an actual supported scenario is ready.

Next product stage

Stage / 04

Private Alpha

Hosted and independently self-hosted cohorts exercise real supported scenarios, updates, recovery, cancellation, and operations.

Planned

Stage / 05

Public Beta

Broader enrollment follows private-alpha exit, signed distribution, external review, documented limits, and operational readiness.

Planned

Stage / 06

Commercial Launch

A sellable, supportable release with evidenced applications, transport, deployment, billing, security, recovery, accessibility, and support.

Planned

Foundation evidence

Private testing has something real to exercise.

  • Development control-plane state persists in PostgreSQL.
  • Device enrollment and signed heartbeat protections are implemented foundations.
  • Attended consent is bounded, revocable, and tied to an exact epoch.
  • The Windows service/SessionHost process and user-session boundary has real protected-machine evidence.
  • Transition integrity and operating checks are part of the evidence program.
Private testing

Testing the product as a system.

Identity, authorization, consent, lifecycle, endpoint behavior, packaging, deployment, recovery, accessibility, and operations move through the same evidence-led program.

How public claims graduate

A roadmap assignment is not evidence. A capability moves from planned to shipped only when its owning work package, application path, failure cases, security boundary, and required real-environment evidence pass.

Scale language is limited to the last completed measured gate. A planning target is never converted into a concurrency or capacity claim.

When evidence changes a claim, the status page, product copy, metadata, and public graphics change together.

Interested in private testing?

Join the design conversation.

Founding Pilot applications are open across all five audiences.

Apply to the pilotProduct direction