Infinite Haiku
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.
OpenTelemetry in · Kubernetes · read-only MCP for your agents
Reading our own Poet…
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.
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.
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.
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.
Who is behind 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
Read more
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
One line in a terminal installs two programs on the machine: the Poet, our datastore, which keeps the machine’s data on the machine, and the Muse, our collector, which reads the machine and feeds the Poet. Both start on their own and restart if they stop. Your browser reads the Poet over a direct, encrypted WebRTC connection: your telemetry never passes through our servers; we only handle sign-in.
web-1.curl -fsSL https://infinitehaiku.com/install.sh | sh -s -- --org <your organisation id> --cluster web-1
web-1 turns Connected a few seconds after
the download; the machine, its disks, interfaces and busiest processes
follow.The token is never on a command line or in your shell’s history. For
automation without a terminal, --token-file FILE reads it from a file
instead (the installer copies it; remove the file after).
The installer downloads the release from infinitehaiku.com and refuses to
install unless the checksums carry our release signature and each archive
matches them. It checks against our release key, which is written in the
script. Its fingerprint is SHA256:tM/OPJFdCbcQYqLcRfCwpVKhG11sb8R+xPM3KbL+lY0,
the same key that signs our agent door. To read
the script before running it:
curl -fsSL https://infinitehaiku.com/install.sh -o install.sh
less install.sh
sh install.sh --org <your organisation id> --cluster web-1
On a Mac (Apple silicon, macOS 11 or later), two LaunchAgents of your user, no administrator rights:
| Where | What it is |
|---|---|
~/Library/Application Support/InfiniteHaiku/ | The Poet and the macOS Muse, your data (at most 10 GB) and the token, readable only by you |
~/Library/LaunchAgents/com.infinitehaiku.*.plist | Start both at login and restart them if they stop |
~/Library/Logs/InfiniteHaiku/ | poet.log and muse.log |
Our programs are not notarised by Apple. Downloaded by the installer, they run as they are.
On Linux (x86_64 or arm64, systemd 247 or newer: Ubuntu 22.04, Debian
11, Fedora 34, RHEL 9 or newer), two system services, installed with
sudo. Each runs sandboxed under its own transient user, not root. They
are system services because the Linux Muse reads the whole host (every
service and process, the kernel’s faults) and a server’s Poet runs from
boot, with nobody logged in.
| Where | What it is |
|---|---|
/opt/infinitehaiku/bin/ | The Poet and the Linux Muse |
/etc/infinitehaiku/ | The settings and the token, readable by root only |
/etc/systemd/system/infinitehaiku-poet.service, infinitehaiku-muse.service | The two services |
/var/lib/private/infinitehaiku-poet/ | Your data (at most 10 GB); logs in the journal |
On NixOS, use our NixOS module instead.
The Muse sends to the Poet over loopback only, and the Poet listens on no other address. Installing again replaces the programs and keeps the data.
curl -fsSL https://infinitehaiku.com/install.sh | sh -s -- status
It shows both services, whether the Poet’s intake answers, the Poet’s last sign-in lines and the Muse’s last samples.
curl -fsSL https://infinitehaiku.com/install.sh | sh -s -- update
It installs the newest release (update --version <version> for another)
with everything as installed: organisation, cluster name, Shibuya, ports,
limits and the stored token, so it asks nothing. The data and the
machine’s own secrets stay. On Linux it asks for sudo, as install does.
Kabuki marks a Poet that runs an older version on Updates and on the Poet’s own page, with this command. An older Poet is updated; Kabuki does not keep older versions of itself to open it.
To change the organisation, the name or the token, run the install line again instead: it replaces the programs and settings and keeps the data.
curl -fsSL https://infinitehaiku.com/install.sh | sh -s -- uninstall
It stops both services and removes everything the install made, the data
included. Then revoke the token (poet web-1) in Access › Tokens.
Your data was only on this machine, so that is all it takes to leave. During the pilot there is nothing to cancel (leaving).
curl and
ssh-keygen (on Linux, the openssh-client package).No account yet? Write to us: during the pilot we set up your organisation with you.