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

Watch every connection yourself

Don’t trust us: watch it yourself. Your Poet measures every connection it serves and keeps the numbers with your other telemetry.

Your browser or AI agent and your Poet talk peer to peer; infinitehaiku.com carries only signalling; a TURN relay passes the same encrypted packets when no direct path exists

  • Your data goes peer to peer. Every chart, query and answer travels between your browser or agent and your Poet, encrypted. Your Poet counts the bytes and messages each way, per connection.
  • infinitehaiku.com only introduces the two. Sign-in, then the offer, the answer and network candidates; your Poet adds a load report every 10 s. Your Poet counts it per message type; so does our web service.
  • The relay is a fallback. Only when no direct path exists, the same encrypted packets pass through turn.infinitehaiku.com, which cannot read them. Your Poet marks such a connection “relay”.

Sizes and counts only. No content is recorded, ever.

See it in your organisation

Open Dashboards, choose one of your Poets, then Connections:

  • Now: who is connected, how many go through the relay, the bytes per second peer to peer and the bytes per second to infinitehaiku.com.
  • Traffic: bytes per connection, in and out, by path, and the signalling by message type.
  • Who: one row for each user and each agent token, with their sessions and bytes. Users of another organisation never appear by name.

Your AI agent reads the same numbers through the agent door: ask it “who is connected to my Poet, and how much went to infinitehaiku.com?”

Live: our own Poet

Our own Poet, right now: its data channel bytes by path, and what went through infinitehaiku.com.

Our Poet: bytes peer to peer, by path, live · open it full size
Our Poet: signalling via infinitehaiku.com, live · open it full size

How we protect the rest is on the Security page; what our website records is on the Privacy page.