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
← Docs

What is Infinite Haiku

Infinite Haiku shows what your systems are doing: metrics, logs, traces and the changes behind them, on one timeline.

What it observes

  • Your services, through OpenTelemetry (OTLP/HTTP): send what your applications already emit (today to a Poet on a Linux machine).
  • Your infrastructure, through small collectors we call Muses: a Kubernetes cluster, a Linux host and its kernel faults.
  • How things relate: which pod runs on which node, which request called which service. The views keep that context when you move between them.

Your data stays with you

The datastore, the Poet, runs in your infrastructure: a Kubernetes cluster or a Linux machine. Your telemetry is written there and stays there.

When you open a view, our web service signs you in and introduces your browser to your Poets. From then on the data travels directly between your Poet and your browser over an encrypted WebRTC channel. It never passes through our servers, and you do not pay egress to ship it to us.

Several Poets can replicate each other, so a view stays available when one of them is down.

The charts

The charts are drawn by our own GPU engine (WebGPU in the browser). It draws every series of a service at once as bands you can enter: zoom in and the resolution follows, select a band and the others step back, with the details beside it. The Poet computes every number; the browser only draws them, so a chart, the API and an AI agent read the same answer.

Agents included

AI agents investigate through a read-only door (MCP) that runs on your machine and talks to your Poets the same direct way. It can search, follow a request, and record what it found in an incident.

Next

Install a Poet where your data should live, on Kubernetes or a Linux machine, and the Muses or OpenTelemetry senders that feed it. See Public dashboards for sharing a view with people who do not sign in, and the blog for how it is built.