Hone

Self-hosted, MCP-only LLM-facing telemetry for Laravel.

Hone is a thin telemetry layer for Laravel apps. It captures laravel/nightwatch instrumentation, stores a pruned slice in a Postgres database you control, and exposes it to a coding agent (Claude Code, CI, etc.) over MCP to answer one question well:

"What should we improve this week?"

It is deliberately not a Nightwatch competitor. No UI. No deep request traces. No long-term history. No alerting. Just agent-queryable telemetry with no per-event cost.

Why Hone exists

Nightwatch's event-metered pricing doesn't fit a large class of apps where request volume doesn't track revenue. To control cost, those apps throttle sampling so hard the data stops being useful.

Hone is a free, self-hosted floor: agent-queryable telemetry with no per-event cost, for the apps the metered model was never going to fit. Storage is your only cost.

Positioning. Nightwatch is the full-featured product — deep request diving, history, alerting, collaboration, and the excellent UI the Laravel team built. Hone answers one narrow question for one consumer (a coding agent). Outgrow it → Nightwatch is the upgrade.

Hone is built on laravel/nightwatch (MIT, by Taylor Otwell). It rebinds Nightwatch's ingest transport so an app's own telemetry routes to the app owner's own server. Hone never contacts Nightwatch's cloud and never uses their service.

Support posture

Hone is written for how Artisan Build uses it. Bugs get fixed. Feature requests are a fork away. Client-specific features are not backfilled into the OSS release. If you need the full product, that's what Nightwatch is for.

Architecture

  Source app #1 ─┐  (hone-client: rebind transport → batch → HTTPS POST)
  Source app #2 ─┼──►  Hone app (one isolated env per client)
  Source app #N ─┘         │ ingest endpoint (HONE_TOKEN auth, tags source app, version-checks envelope)
                           ▼
                        Redis queue
                           ▼
                        Worker → Postgres  (raw, tagged by app + deploy + record_type)
                           ▼
                        Scheduled rollup (before prune) → aggregates
                           ▼
                        MCP server  ◄── coding agent (Claude Code / CI)

• One isolated environment per client on Laravel Cloud — its own compute, Postgres, and Redis, sized and billed per client. The Hone app is single-tenant; isolation is environmental.
• Unlimited source apps per environment. One client may feed many applications into one Hone environment — hence the app dimension and the app registry.
• Cross-boundary transport is HTTP, not shared Redis. Source apps are separate deployments; a TLS + token endpoint crosses environment isolation cleanly.

Repository layout

This is a monorepo. Three packages are developed here under packages/, each split read-only to its own repository and published to Packagist:

The Hone app (this repository's root) is a slim Laravel shell — token handout plus wiring hone-server. It pulls its packages from Packagist and stays thin so there's no Hone-specific business logic to dri

... View full README on GitHub