# Product

## Register

product

## Users

MeshLLM serves local AI hobbyists, small and mid-sized technical teams, company IT teams, and larger cluster operators. They use it when they need to combine heterogeneous hardware into a single, legible mesh for AI inference across home labs, offices, and organizational environments.

The primary user is an operator using the app to check node health, route models, allocate VRAM, tune configuration, and understand how inference work moves through the mesh. They value speed, precision, recoverability, and technical transparency more than promotional storytelling.

## Product Purpose

MeshLLM makes distributed local AI infrastructure feel controllable. It turns a set of peers, models, GPUs, routes, and configuration files into one coherent operations surface where users can see capacity, place workloads, inspect behavior, and act with confidence.

Success means the mesh feels understandable at a glance, detailed under inspection, and safe to operate even when the underlying hardware is varied. The product should read as a private AI operations console, not a consumer chat app and not a marketing dashboard.

## Brand Personality

Technical, sharp, fast.

The tone should communicate power and control without theatrics. Users should feel high agency, operational clarity, and confidence that the system is capable. The interface can be intense and information-dense, but it must stay calm, precise, and composed.

## Anti-references

- Generic SaaS dashboards with oversized whitespace, interchangeable cards, and soft “growth platform” styling.
- Gaming-neon cyberpunk, holographic sci-fi, and loud AI magic visuals.
- Consumer chat products with oversized rounded bubbles, giant composers, and assistant-first personality.
- Dull enterprise software that hides capability behind gray sameness and weak hierarchy.
- Decorative gradients, glassmorphism, multicolor dashboards, and theatrical motion used to imply intelligence.
- Dark-mode-only design where light mode feels like an afterthought.

## Design Principles

1. Make distributed infrastructure feel legible and controllable, not abstract or intimidating.
2. Express technical depth through precision, hierarchy, and useful density rather than visual clutter.
3. Keep the product minimal and deliberate, but never bland; every element should signal capability.
4. Design for real heterogeneous deployments, from personal machines to larger operational environments.
5. Treat light and dark modes as equally intentional operating conditions.

## Accessibility & Inclusion

Target WCAG 2.2 AA for contrast, keyboard navigation, focus visibility, and screen-reader semantics. Preserve reduced-motion compatibility for mesh visualizations, command surfaces, and configuration controls.

Do not communicate state through color alone. Pair status color with labels, icons, text, or position. Keep dense technical information readable through typographic contrast, clear hit targets, and explicit focus states rather than relying on hover-only affordances.
