Skip to content
Scalpels home

Scalpels is officially launching on October 31, 2026. Special early adopter pricing is available now.

Hone

Laravel MIT licensed

Your application's telemetry — slow requests, slow queries, job durations, exceptions — collected and queried on hardware you already pay for. No stream leaving your environment, no per-event pricing, with retention periods you control.

Deploy Hone for free Or run it yourself, free Read the Docs
Replaces
Hosted APM subscriptions
Runs on
Your Laravel Cloud account
Needs
Compute · Database · Queue · Scheduler

What it captures

Rolled into daily aggregates, queryable across deploys

  • Slow requests

    Endpoint and duration, rolled into queryable aggregates.

  • Slow queries

    The statement, where it was called, how often.

  • Queued jobs

    Durations, failures, and queue backlog over time.

  • Exceptions

    With the request context that produced them.

  • Outgoing HTTP

    Which third party is making your app slow.

  • Cache activity

    Hit rates and the keys that never hit.

  • Ask it directly

    MCP

    Hone exposes a Model Context Protocol server, so your agent can answer "which query got slower after Tuesday's deploy?" against your own telemetry — without a vendor sitting between the question and the data.

  • Speaks Nightwatch

    Your apps send standard Nightwatch telemetry to your Hone deployment. If you already instrument with Nightwatch, the only thing that changes is the destination — and who owns what arrives there.

Hone vs. the incumbents

We rebuilt one row of their feature matrix

Nightwatch, Sentry and Datadog are good products, and Hone is not trying to replace them. It does one slice of what they do — performance history you can query, and an MCP server over it — and deliberately does not do the rest. The question is not which product is better. It is which slice you are actually using.

Hone feature comparison
Feature Hone Self-hosted, MIT Nightwatch Laravel, hosted Sentry Hosted Datadog Hosted
Request and query performance history the row we rebuilt Does this well:Yours, retention you set Does this well:Included Partly, or with a caveat:Add-on Does this well:Included
MCP server over your own data the row we rebuilt Does this well:Built in Does this well:Built in Not built:Not offered Not built:Not offered
Exceptions with request context Does this well:Included Does this well:Included Does this well:Their core strength Does this well:Included
Alerting, paging, on-call routing we did not build this Not built:Not built Does this well:Included Does this well:Included Does this well:Extensive
Curated dashboards and charting we did not build this Partly, or with a caveat:Enough to answer a question Does this well:Polished Does this well:Polished Does this well:Industry standard
Infra metrics, logs, RUM, tracing we did not build this Not built:Not built Not built:Not offered Partly, or with a caveat:Partly Does this well:All of it
Non-Laravel apps Not built:Laravel only Not built:Laravel only Does this well:Most stacks Does this well:Everything
Where your telemetry lives Does this well:Your Postgres Works, but on their terms:Their cluster Works, but on their terms:Their cluster Works, but on their terms:Their cluster
Cost of sending more data Does this well:Disk Works, but on their terms:Per usage Works, but on their terms:Per event Works, but on their terms:Per host, per seat
Who is on call for the tool itself Partly, or with a caveat:You are Does this well:They are Does this well:They are Does this well:They are
  • Does this well
  • Partly, or with a caveat
  • Not built
  • Works, but on their terms

The honest test

Open your current bill and ask what you actually touched last month. If these are all true, you are paying for a suite to use one row of it.

  • You query it through an agent or the API, not the dashboard.
  • You never turned the notifications on.
  • Everything you monitor is a Laravel app.

Then you lose very little by moving. The same slice runs on infrastructure you already pay for, with retention periods you set.

Keep paying them if

These are the parts we chose not to build, and we are not going to pretend otherwise.

  • Alerts wake someone up, and that matters.
  • Your estate is polyglot and you need one pane of glass.
  • Someone reads those dashboards every morning.
  • You want infra, logs and RUM in the same place.

Small, sharp tools are a deliberate scope, not an unfinished roadmap. Hone will not grow into an observability platform.

Be honest about it

You don't need us to run Hone

The repository is public and MIT licensed. These are the steps, and you are welcome to spend the afternoon doing them by hand.

  1. 1

    Fork the Hone repository into your own GitHub organisation.

  2. 2

    Deploy the fork to Laravel Cloud with its own compute, Postgres and Redis.

  3. 3

    Point your application's telemetry at your deployment.

Or let Scalpels do it, free. It forks the app, provisions exactly what it needs on your Laravel Cloud account, and deploys it. The app and the infrastructure are yours either way — the only question is who spends the afternoon.

Deploy Hone for free

Guides for Hone

Want some help?

After you buy, we will pay for an hour with one of these experts to help you get everything up and running.

  • Artisan Build

    USA

    We run Scalpels, as well as a suite of other tools for developers and development teams.

    Agency Ask for help
    Ask Artisan Build for help

Hone pairs with the rest of the suite

Reel links each session replay to the requests behind it, so a slow trace here comes with a recording of the person who sat through it.

Reel Matte Sink