Authority
No mandatory NoBS session service
The independent self-host target authorizes business and session activity through the customer-operated control plane.
I need private infrastructure
Keep the control plane inside the boundary you choose.
NoBS Remote is being designed for organizations that cannot accept a mandatory shared-cloud authority path. Dedicated-private and independently self-hosted operation are first-class directions, but neither is customer-ready today.
Private deployment plannedThe intended fit
Control must be architectural, not ceremonial.
These are design and evidence requirements, not current service guarantees.
Content
Endpoint-owned private and content keys
The control plane and future relay are not intended to receive endpoint private keys or plaintext session content.
Operations
Responsibility made explicit
Updates, backups, restore, monitoring, relay, diagnostics, incidents, support, and recovery must have named owners for each deployment.
Intended workflow
Private infrastructure without a weaker endpoint boundary.
- Customer or dedicated authority resolves the exact organization, role, device, and request.
- The intended local user sees and controls attended-consent authority.
- Future endpoint-to-endpoint protection binds the exact session, roles, directions, and keys.
- Relay, if used, forwards without plaintext authority.
- Stop, revoke, expiry, process loss, and incident policy terminate authority consistently.
Not an air-gap claim
No private package exists yet.
Development Docker Compose does not establish a supported, offline, air-gapped, high-availability, independently audited, or customer-operable product. NoBS Remote will not use “self-hosted” to imply those properties before they are tested.
Deployment fit
Three choices, two private operating models.
NoBS-hosted
Useful where a managed shared service meets the organization’s policy. It is not positioned as the only full-capability path.
PlannedNoBS-operated dedicated private
A separately defined environment for organizations that need a dedicated boundary but want NoBS to operate it.
Conditional engagementIndependent self-hosted
A customer-operated Linux Docker/PostgreSQL control plane intended to function without mandatory NoBS session authorization.
PlannedSecurity and assurance
Your threat model still decides.
No design label removes the need for customer review of endpoint trust, identity, cryptography, update authority, relay, logging, recovery, insider risk, provider dependencies, and operations. Exact evidence will accompany each supported profile.
Commercial direction
Private economics stated separately.
Dedicated operations and independent self-hosting have different costs and responsibilities from hosted service. Licensing, support, update, and optional service terms will be explicit before payment.
Read pricing principlesFounding Pilot fit
Bring the actual boundary and threat model.
Tell us what must remain internal, which dependencies are allowed, who operates the service, and what evidence your organization requires.
Can NoBS Remote run fully offline today?
No. No supported customer deployment, remote-control path, offline package, update process, or air-gap evidence exists today.
Will self-hosting require a NoBS cloud account to authorize sessions?
The independent self-host target explicitly avoids a mandatory NoBS session-authorization dependency. Final installation, licensing, update, and support mechanics are not yet published.
Does “dedicated private” mean single tenant, single server, or a specific region?
No fixed technical or contractual meaning is claimed yet. Isolation, topology, region, operations, recovery, and support will be defined and evidenced for each offered profile.