Services

Choose the lane that matches the main readiness problem.

Backup & Recovery Readiness is the active preview lane. Three more preview pages make the direction clearer: homelab and small-server review, documentation cleanup, and website or service deployment readiness.

Start a KITPro conversation Review the active lane

01Active now

Backup & Recovery Readiness is the first active preview service lane.

02Also visible

Homelab, documentation, and deployment previews show the likely next review directions.

03Still conservative

No forms or automated intake. /start remains the manual next step.

Compare lanes

Which lane fits?

Scan the four current preview lanes by problem type before opening a full service page. Keep /start as the manual next step if the fit is still unclear.

Backup & Recovery Readiness Audit

Best fit: Backups, restore notes, and recovery readiness are the main concern.

KITPro reviews: Backup coverage, copy separation, restore assumptions, access dependencies, and readiness gaps.

What it is not: Not the right lane for emergency recovery or a broad review of the whole server environment.

Open preview lane

Homelab / Small Server Readiness Review

Best fit: The overall small-server or homelab setup needs review.

KITPro reviews: System layout, admin habits, access paths, update routines, and practical weak points across the setup.

What it is not: Not the right lane when backup and restore confidence are the only real issue.

Open preview lane

Documentation / Runbook Cleanup

Best fit: Systems work, but notes, runbooks, or operational steps are messy.

KITPro reviews: Scattered notes, recovery steps, handoff context, stale instructions, and missing runbook structure.

What it is not: Not the right lane for direct deploy work or a full technical review of the host environment.

Open preview lane

Website / Service Deployment Readiness

Best fit: A site, app, DNS, proxy, deploy path, or runtime flow needs readiness review.

KITPro reviews: Hosting context, routing assumptions, deploy notes, restart behavior, rollback thinking, and ownership gaps.

What it is not: Not the right lane when the main concern is data recovery or general documentation cleanup alone.

Open preview lane

Start a KITPro conversation

Current lineup

Public preview lanes

These four lanes are the current public-facing direction. One is active now; three are visible so the service lineup feels understandable before anything broader is offered.

Review whether important systems have useful backup coverage, separated copies, restore notes, and a realistic recovery path.

Review backup readiness preview

Review homelab and small-server setups for system layout, access habits, update posture, recovery assumptions, and day-to-day readiness gaps.

View service preview

Review scattered notes, runbooks, recovery steps, and handoff context so the systems you depend on are easier to understand and support.

View service preview

Review websites and internet-facing services for deployment basics, routing assumptions, ownership notes, rollback readiness, and practical weak points.

View service preview

Coming later

Additional lanes are staying quiet for now.

These directions fit KITPro, but they remain card-only and conservative until the earlier preview lanes have stronger evidence and clearer public language.

Self-Hosted App / Docker Stack Review

A possible future lane for reviewing compose stacks, app boundaries, persistence assumptions, backup coverage, and service layout before they become fragile.

Basic Monitoring / Uptime Readiness

A possible future lane for checking service visibility, basic alert assumptions, uptime weak points, and what should be noticed before downtime becomes a surprise.

Linux / Open Source Migration Planning

A possible future lane for reviewing pragmatic moves toward Linux, open source, or self-hosted tooling without rushing production changes.

Monthly Advisory / Retainer

A possible ongoing advisory lane for periodic review, planning, and technical follow-up after the preview lanes are proven. Scope remains under review.

Manual path

How the manual process starts

The start path is intentionally simple so KITPro can understand the request before suggesting a next step.

Start with context

Use /start to share what setup matters, what process already exists, and which review lane seems closest to the problem.

Josh reviews fit

The first reply stays manual and practical. If the request fits, Josh can ask a few follow-up questions.

Keep scope clear

Each lane is a review and recommendation path. Any deeper work is a separate later decision.

What the public preview is not offering

Emergency recovery during an active outage

Not part of the current preview path.

Managed IT operations

Not part of the current preview path.

Guaranteed restoration outcomes

Not part of the current preview path.

Instant self-serve request flow

Not part of the current preview path.

Next step

Start manually when you want Josh to review fit.

The start page explains what to include in the first email and keeps the process manual while KITPro validates the current service direction.

Start a KITPro conversation Review Backup & Recovery Readiness