One honest platform

Remote support that can grow without changing its principles.

NoBS Remote is being built for one trusted device, a client fleet, an enterprise operation, and private infrastructure. The customer experience is not ready yet; the security and authority foundation is real and still being proven layer by layer.

Verified foundation Building now

The intended workflow

Clear before, during, and after support.

This is product direction, not a claim that remote sessions work today.

01 / Request

Make the help request understandable

The person receiving help should know who is asking, what is being requested, and when the request expires.

Building now

02 / Support

Keep local control visible

Attended consent, a visible session state, immediate local Stop, and bounded authority remain central to the intended experience.

Planned product

03 / Accountability

Leave useful, bounded history

Organizations should be able to understand who acted, which resource was involved, and how authority ended—without logging session content or secrets.

Foundation in progress

Verified foundation

What exists in the development foundation

  • Persisted tenant, device, support-request, consent, and audit foundations.
  • One-time, hash-only enrollment tokens and locally generated device identity keys.
  • Signed, replay-protected device heartbeats.
  • Bounded attended-consent authority with explicit revoke and Stop semantics.
  • A Windows service and per-user SessionHost trust boundary verified in development.
Current boundary

Remote access is not available yet.

There is no customer-ready screen viewing, mouse or keyboard control, clipboard, file transfer, production relay, hosted service, self-host package, billing, or licensing product today.

A successful control-plane or consent test is not described as a connection. NoBS Remote will not use a polished interface to disguise missing capability.

Follow the evidence

See exactly where the build stands.

The build page separates achieved foundations, active work, and future product milestones.