localhosted / app

A calmer way to operate a self-hosted stack

The first localhosted MVP objects are now explicit: services, checks, activity, and recommended actions. The dashboard exists to help a small team understand risk quickly and decide what to do next.

MVP product objects

The first product language is now explicit

localhosted is not a generic infra abstraction layer. The current MVP revolves around four objects: services, checks, activity, and recommended actions.

Services

What is part of the stack and what shape it is in.

Checks

The smallest useful health signals for confidence.

Activity

Recent events that explain what changed and why it matters.

Actions

The next useful moves that keep the stack reliable.

Services

Three services define the current stack snapshot

These service cards are now driven from a shared mock data layer so the product can evolve without rewriting every screen first.

Recovery

Backups

At risk

The last successful backup is older than the recommended window.

View service details

Monitoring

Uptime checks

Needs setup

No monitor is connected yet for service-level alerts.

View service details

Recommended actions

What should happen next

Actions should feel concrete enough that a team could use them to guide the next product move or operational step.

Review backup timing

Open

Make recovery confidence visible before the next deployment push.

Connect one health check

Open

Start with a simple uptime signal instead of a full observability stack.

Capture the next deploy path

Open

Keep the next rollout obvious for a small team instead of burying it in ad hoc notes.

Recent activity

Recent signals

The app only needs a lightweight activity stream for now, but it should already help users understand what changed.

2h ago

TLS certificate renewed successfully

Public ingress stayed healthy after the renewal cycle.

Yesterday

Backup job skipped expected window

Recovery posture needs confirmation before the next deploy.

Planned

Add first service-level monitor

The next useful milestone is basic uptime coverage for the stack.