Understandable
One clear request
The person receiving help should see who is asking, what kind of help is requested, and when the request expires.
I help family
Calm support for the people who call you first.
NoBS Remote is being designed so a trusted helper can solve a problem without turning consent, safety, or a handful of machines into enterprise complexity.
Product experience plannedThe intended fit
Simple enough to explain over the phone.
These are design requirements, not available features.
Visible
Local control stays obvious
Consent, active support state, scam warnings, and Stop should use plain language instead of implementation terms.
Proportionate
A few machines stay affordable
Personal and family use should have clear licensing without forcing occasional help into an enterprise-sized annual commitment.
Intended workflow
Ask, understand, approve, stop.
- The helper sends a bounded support request.
- The person at the computer sees the helper and an anti-scam warning.
- Approval grants only time-limited, revocable authority.
- Visible local state remains while support is active.
- Stop ends authority immediately and the session leaves useful history.
Security foundation
Consent work exists. Remote control does not.
The development foundation has real bounded-consent and Windows session-binding evidence. There is no customer-ready invitation, Viewer, screen, input, or reconnect path today.
Deployment fit
Start easy without closing future choices.
NoBS-hosted
The intended straightforward choice for personal and family support once the hosted product is ready.
PlannedDedicated private
Available as a future organizational engagement, but usually more operational boundary than a family helper needs.
ConditionalIndependent self-hosted
A first-class future option for people who already operate Linux Docker and PostgreSQL infrastructure and want full control-plane ownership.
PlannedAvailability
Not ready for a real support call.
Do not rely on NoBS Remote to help a family member today. Screen viewing and control are not implemented, and no public download exists.
See the verified build statusPricing direction
Fair at small scale.
Clear personal licensing, month-to-month availability, cancel-anytime treatment, and no annual trap are commitments. Exact prices are not published.
Read pricing principlesFounding Pilot fit
Are you the family tech-support person?
Tell us what makes remote help confusing, unsafe, or too expensive today. Applying starts a design conversation, not product access.
Will the person receiving help need an account?
The final invitation and identity flow is not complete. The requirement is that attended help remain understandable and not depend on hidden authority.
Will unattended family access be available?
It is not available and is deferred by default. Any future unattended mode requires separate device-owner policy, recovery, visible state, Stop, and compromise-response evidence.
Can I join the pilot with only a few machines?
Yes. Small, occasional use is an equal audience, and selection is based on learning value rather than fleet size.