Trust & Readiness

Security and Tenant Readiness

A transparent readiness page for operators evaluating how KC is preparing the software before broader external-operator use.

Request Early Access Operator Resources

Also useful:Resources Pricing FAQ

Quick Answers

A clear answer before the deeper guide

These short answers help operators understand the page, connect it to Rivet, and keep important boundaries clear.

What is this security readiness page for?

A conservative trust page explaining authenticated dashboard access, company context, roles, protected routes, public-dashboard separation, software-interest admin boundaries, and ongoing readiness work.

How does this connect to Rivet?

This guide connects the operator topic back to Rivet's washer and dryer rental workflow: customers, inventory, delivery, payments, service, reporting, and guided early access.

Does this replace professional advice?

No. These pages are practical operating resources, but legal, tax, insurance, lending, installation, and repair decisions should be reviewed with qualified local professionals.

Readiness Posture

External access is being prepared deliberately

Practical education for washer and dryer rental operators, grounded in operating workflow rather than generic startup copy.

We are preparing the software for broader external-operator use and are deliberately reviewing tenant isolation, authentication, permissions, integrations, and operational safeguards before self-service onboarding.

This page only describes claims supported by the current architecture audit. It does not publish secrets, credentials, internal hostnames, or sensitive implementation details, and it does not claim security certifications or absolute guarantees.

Authenticated dashboard access

Public software pages are separate from dashboard workflows. The dashboard path requires an authenticated session before a user can reach internal operating views.

Unauthenticated dashboard requests are redirected to sign in. That supports the basic boundary between public marketing pages and protected operational tools.

Company and tenant context

The codebase includes company context for operating records and an active-company concept for authenticated users. The current public pages should describe that foundation conservatively because external-operator isolation must continue to be tested before self-service onboarding.

Company-scoped operating records are part of the architecture.
Authenticated users resolve into a company context.
External-operator onboarding remains guided and readiness-gated.
Public requests do not create a company, account, or tenant automatically.

Owner, admin, and member concepts

The application includes owner, admin, and member role concepts. Software-interest review is limited to owner/admin membership in the configured owner company, and broader role behavior should continue to be reviewed before external rollout.

Owner/admin/member role concepts exist.
Software-interest admin routes require owner/admin authorization.
Fine-grained external permission promises remain a readiness item.

Protected routes and public workflow separation

The public software pages route interested operators to a software-interest flow, not to the consumer rental contact form, public account signup, customer setup, payment pages, or the internal dashboard.

That separation matters because a software prospect should not trigger consumer rental automation or receive accidental operational access.

Readiness work still in progress

Before broader external use, KC is continuing to review tenant isolation, provider configuration, access boundaries, support processes, onboarding and offboarding, backup and incident expectations, and legal documents.

That is why early access is manually reviewed. The goal is to move carefully enough that the public story makes the readiness gaps clearer, not hidden.

Important Boundary

Transparent claims only

This page is a readiness overview, not a security certification, audit report, or guarantee. Operators should expect continued review before external onboarding and should not treat early access as public self-service availability.

Trust Path