Roadmap
Plain English tests for user flows are the start. Scroll through to see what we're building toward.
Available now
The CLI is available in early access today. It reads .haiku files and drives your app on iOS simulators, Android emulators, web browsers, and macOS.
Write your flow in plain English, run it from the terminal, wire it into any CI pipeline. No selectors. No framework to configure.
Available now
The same belief that drives UI testing applies to backend code. A Python module, a Rust crate, an API endpoint: if you can describe what it should do, you should be able to test it.
.py.haiku files run with pytest. .rs.haiku files run with cargo test. Both available today. .go.haiku, .ts.haiku, and .java.haiku are experimental and improving fast. Each one slots into your existing test runner. Nothing to replace.
In development
A native macOS app for writing, recording, and running tests in one place. Use your app normally and Haiku captures every action as a readable, editable .haiku file.
No terminal required. Review the generated flow, run it immediately, share it with anyone on your team.
Coming next
Managed infrastructure for running tests remotely. CI/CD integrations for GitHub Actions, CircleCI, and others built in.
Tests run on every push without owning the machines. Results show up in your pipeline like any other check.
Coming next
The same execution engine on your own runners or servers. Full CI/CD support.
No data leaves your network. Drop it into the infrastructure you already run.
Haiku is in early access. Be first in line as each piece ships, and tell us what matters most to you.