Infinite Haiku

Observability that stays in your network.

Metrics, logs and traces on one timeline, stored in your own cluster and read by your browser directly. Your telemetry never passes through our servers.

Write to us See our servers live →
OpenTelemetry in · Kubernetes · read-only MCP for your agents
Our own Poet, live

drag to zoom · double-click back

Reading our own Poet…

Your data stays home.

The datastore runs in your Kubernetes cluster or on your Linux machines. We sign you in and introduce your browser to it; the data goes straight to you over an encrypted channel. No egress bill to ship telemetry out, and nothing at our end to leak.

Walk into the timeline.

Every series of a service at once, drawn on your GPU. Zoom in and the detail follows; open a request and see its log lines and the change behind it. Missing data is shown as missing, never as zero.

Your agents investigate.

A read-only door (MCP) lets the coding agent you already use search, follow a request and read the same numbers as your charts. No vendor AI, no per-investigation fee.

How it works

  1. 1A Poet in your cluster. Our datastore runs where your services run and takes their OpenTelemetry. Read-only, one namespace.
  2. 2You sign in at infinitehaiku.com. Our web service checks who you are and introduces your browser to your Poet. That is all it sees.
  3. 3Your browser talks to your Poet directly. An encrypted peer-to-peer channel (WebRTC). The numbers never pass through our servers.
Your browser signs in at infinitehaiku.com, which introduces it to the Poet in your network; the data then goes directly between the Poet and your browser. Your network Your services OpenTelemetry Poet your datastore Your browser dashboards, AGS infinitehaiku.com sign-in, introduction your telemetry, encrypted, direct never through our servers
Infinite Haiku in one minute · plays from YouTube (youtube-nocookie.com)

Proof, not promises

Measured: 500,000 tasks from 200 workers over five hours, drawn at 1.1 ms of CPU per frame.

This site's own requests, live: the same public view you can give your customers.

This site's own requests, live · open it full size

Who is behind it

An independent team. You talk to the people who build it.

No sales layer between your questions and the answers.

Built since April 2024. Bootstrapped: no venture capital, no board, no hyperscaler lock-in. About us

  • Alerts in your network. Evaluated inside your own Poets.
  • Public status pages. Share a live dashboard without sharing access.
  • Kernel faults on the timeline. Memory errors, silent out-of-memory kills and disk errors, per node.
  • Flat CHF 5 per user account and month. Nothing per gigabyte, host or event.
  • Don't trust us: watch it yourself. Your Poet shows every connection and its bytes, peer to peer or to us. See how

Join the free pilot.

Expert help on your systems. Leave anytime: delete the Poet, one command. Once we open to the public: two months free, then a flat CHF 5 per user account and month. How the pilot works · Security

Write to us

Blog

What Infinite Haiku does, with measured numbers.

Start here

  • We rebuilt the Poet so your data never leaves your network poet webrtc

    The new Poet keeps your telemetry in standard formats inside your infrastructure, answers with exact numbers, and talks to your browser directly; our servers only introduce the two.

  • The request, the log line and the change, on one page logs traces incidents agents

    Logs & Traces puts the failing requests, their log lines and the change behind them on one page, and the same live views go into incident reports written by people or AI agents.

  • When the machine lies muse reliability

    Silent memory errors, quiet out-of-memory kills and disk faults now appear on Infinite Haiku's timeline per node and per core, found the hard way on our own build server.

All posts

  • Charts you can enter, alerts that stay in your network ags kabuki alerts incidents

    Infinite Haiku now has live AGS charts you can enter, chart styles you choose, Logs & Traces on live data, alerts evaluated in your Poets, incidents as living documents, and Explore, each checked in a browser against the agreed design.

  • Two and a half years of AGS, and the three days we rebuilt its engine ags performance agents

    AGS draws 500,000 task intervals from 200 workers over five hours on your GPU. Two and a half years of hand-built design made that possible; AI agents let us rebuild its engine for scale in three days.

  • Honest graphs ags graphs

    A monitoring graph makes claims about your systems; four rules keep Infinite Haiku's claims true, from 400% CPU to why missing data is never drawn as zero.

How we got here

  • Your data takes the short way webrtc poet origins

    Why your telemetry travels straight from your Poet to your browser over WebRTC, never through our servers, and how real Kubernetes metrics first made that trip in February 2025.

  • A datastore that lives with your data poet origins

    Poet was designed from day one to run in your infrastructure, next to the systems it watches, so your telemetry is not shipped to our cloud and billed twice.

  • Teaching metrics to take shape ags origins

    Why Infinite Haiku draws your whole system as one shape you can zoom into like a map, and how that renderer, AGS, grew from one badly centred colour into a WebGPU tool in spring 2024.