Fast attended help
Quick Support without silent persistence
A future portable or minimal-install path must make the technician, request, consent, and cleanup clear to the client.
I support clients
A serious support toolkit without enterprise-sized contract pressure.
NoBS Remote is being designed for technicians whose reputation depends on solving problems cleanly, keeping each client boundary clear, and paying for a commercial tool that fits the actual operation.
Product experience plannedThe intended fit
Professional behavior without administrative drag.
These are design requirements, not available features.
Client trust
Know whose machine you are touching
Device and request identity, active-session state, immediate Stop, and bounded history should reduce ambiguity on both sides.
Commercial clarity
License the work you actually do
Independent commercial support should have understandable units and month-to-month availability without an annual trap.
Intended workflow
Move from request to resolution with less ambiguity.
- Create or receive a client-scoped support request.
- Let the client verify the technician and approve attended help.
- Use a role-scoped Viewer for the supported screen and control capabilities.
- Keep Stop, revoke, connection state, and failure states visible.
- End cleanly with bounded session history and no unintended persistence.
Current boundary
The technician applications do not exist yet.
Windows Viewer and Quick Support are not implemented. Screen, input, clipboard, files, chat, reconnect, and signed commercial packaging remain required future work.
Deployment fit
Choose simplicity or take control of the service boundary.
NoBS-hosted
The intended fast-start path for technicians who want NoBS to operate the service.
PlannedDedicated private
A future NoBS-operated environment for engagements whose isolation or client obligations justify a separate boundary.
ConditionalIndependent self-hosted
A future customer-operated path for technicians prepared to own Linux Docker/PostgreSQL operations, updates, backups, and recovery.
PlannedSecurity and consent
Client consent is not a speed bump.
The attended path is intended to bind one verified local support window to time-limited authority. Stop, revoke, process loss, session loss, and expiry must end authority instead of merely changing a badge.
Pricing direction
Commercial use stated plainly.
Technician pricing will state the charging unit, included use, overage or fair-use behavior, cancellation, and support level before payment. No price is published today.
Read pricing principlesFounding Pilot fit
Bring the awkward edge cases.
We want to understand your support volume, client handoff, emergency access, billing, packaging, and failure-recovery reality.
Can I replace my current technician tool now?
No. NoBS Remote does not yet provide a Viewer, Quick Support package, screen viewing, or control.
Will commercial use be allowed on a small plan?
Clear personal and commercial licensing is a product commitment. The exact technician plan and price are not yet published.
Can I test self-hosting in the Founding Pilot?
Potentially, after customer-operated install, update, backup, restore, diagnostics, and independent authority pass their gates. The development Compose setup is not the pilot product.