Hone

A telemetry server you run

Hone is a server you run for your own Laravel application telemetry. It receives Nightwatch data from your apps and stores it in infrastructure you control, so performance data, exception context, cache activity, and queue behavior stay inside your environment.

The project is built for teams that want the operational visibility of application telemetry without sending that stream to a third-party SaaS. You fork it, deploy it, and keep the compute, Postgres database, and Redis instance under your own account.

Built for Laravel Cloud

Hone fits the Built for Cloud model: a Laravel app that is useful as open-source software, practical to fork, and meant to be deployed as your own service. Laravel Cloud supplies the runtime, database, cache, and deployment path; Hone supplies the telemetry server.

That keeps the setup understandable. Your application sends Nightwatch telemetry to your Hone deployment, Hone writes the data to your database, and your team queries the results across deploys and incidents.

What Hone captures

Hone captures slow requests, slow database queries, queued-job durations, outgoing HTTP calls, exceptions, cache activity, and more. It rolls that stream into daily aggregates so you can compare behavior over time instead of only reading isolated events.

Ask it directly (MCP)

Hone also exposes a Model Context Protocol server. That gives an AI agent a structured way to ask questions about your telemetry, such as which query is slowest or whether latency changed after the last deploy, while still querying the Hone server you operate.