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

Security

Infinite Haiku is built so that your telemetry does not reach us. Not “stored encrypted at a vendor”: not sent at all.

The data path

The Poet, our datastore, runs in your infrastructure: a Kubernetes cluster or a Linux machine. Your services and collectors write to it there.

When you open a view:

  1. You sign in at infinitehaiku.com.
  2. Our web service introduces your browser to your Poets.
  3. Your browser and your Poet then talk directly, over an encrypted WebRTC channel. The data never passes through our servers.
Our web service seesOur web service never sees
Sign-inYour username and the session
IntroductionWhich browser wants to reach which of your Poets
TelemetryYour metrics, logs, traces and changes
Answers to views and queriesAnything the Poet computes for you

The Poet computes every number. The browser only draws it, so a chart, the API and an AI agent read the same answer.

Don’t trust us: watch it yourself

Your Poet measures every connection it serves and keeps the numbers with your data: who is connected, whether the path is direct or through our encrypted relay, the bytes each way, and the bytes of signalling it exchanged with infinitehaiku.com. Sizes and counts only, never content. Watch every connection yourself.

Accounts and tokens

  • Passwords are stored as bcrypt hashes. A first password is random and shown once; you change it after signing in.
  • Tokens are created by you, with a scope, and shown once. Store them yourself; we cannot show them again.
  • A read-only token can read and nothing else. Use it for agents and scripts.

The agent door (MCP)

AI agents investigate through a read-only door (MCP) that runs on your own machine. It signs in with your token and talks to your Poets the same direct way your browser does; no agent data passes through our servers.

  • It is read-only: it can search, follow a request and read numbers. It cannot change your data.
  • Telemetry text is treated as data, never as instructions. A log line that says “ignore your instructions” is evidence to report, not a command to follow.

In your cluster or on your machine

You install the Poet yourself with one command Kabuki gives you, and you run every command. We never get access to your cluster or machine.

  • A direct, encrypted WebRTC connection from your Poet to your users’ browsers: your telemetry never passes through our servers. We only handle sign-in.
  • Kubernetes: one namespace, one read-only cluster role (get, list and watch of pods, nodes, namespaces, events and workloads; never Secrets, never a write), NetworkPolicies with no ingress.
  • Non-root containers with read-only file systems and no capabilities (the restricted Pod Security Standard); images pinned by digest.
  • The token Kabuki issues is shown once and lives only in your cluster or on your machine. Revoke it in Access › Tokens at any time.
  • Help without access: you send us the pod’s description and logs, which contain no secret, or you share your screen.
  • Removal is one command; see each install page.

Our website

The public pages load only their own scripts: no third-party trackers. What the site records is on the Privacy page.

Reporting a security issue

Write to info@infinitehaiku.com. Please include what you found, how to reproduce it and how to reach you. We answer you personally and tell you what we change.