Step 1 of 2
Go to API keys
Open Settings, then API keys.
API keys
Keys for the checkout-api project
Search keys
Copy
Keys are shown once. Store them somewhere safe.
Stop explaining the same setup in Slack.
Haiku turns one walkthrough of a console or internal tool into a guide your team can follow, or instructions for AI tools.
API keys
Keys for the checkout-api project
Search keys
Copy
Keys are shown once. Store them somewhere safe.
Edit guideSave draftVersion history
Create an API key
Shipyard · Platform team
+ Create key
Step 2 of 2
Click Create key
Create a key, then copy it and store it safely.
API keys
Keys for the checkout-api project
Search keys
Copy
Keys are shown once. Store them somewhere safe.
+
Guide1 of 2PagesStep 1 of 2
Go to API keys
Open Settings, then API keys.
API keys
Keys for the checkout-api project
Search keys
Copy
Keys are shown once. Store them somewhere safe.
Step 2 of 2
Click Create key
Create a key, then copy it and store it safely.
API keys
Keys for the checkout-api project
Search keys
Copy
Keys are shown once. Store them somewhere safe.
The problem
Your processes live in a few heads
Release steps live in one engineer's head.
Rollbacks, keys, flags. When that engineer is away, the team guesses.
A new engineer's first week goes on setup.
Access and tools nobody wrote down. A senior engineer re-explains setup.
Your AI tools don't know your process.
They know code, not how your team ships. So someone checks every step.
How Haiku helps
Record once. Everyone follows.
One walkthrough becomes the guide.
Walk through a deploy or console change once. Haiku turns each click into a step with a screenshot and description.
- Browser and desktop capture
- Auto title and description
- Blur sensitive data
API keys
Keys for the checkout-api project
Search keys
NameKeyCreated
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
NameKeyCreated
local-devdemo-new-keyJust now
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
Keys are shown once. Store them somewhere safe.
Edit guideSave draftVersion history
Create an API key
Shipyard · Platform team
Step 1 of 2
Go to API keys
Open Settings, then API keys.
API keys
Keys for the checkout-api project
Search keys
NameKeyCreated
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
NameKeyCreated
local-devdemo-new-keyJust now
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
Keys are shown once. Store them somewhere safe.
Step 2 of 3
Click Create key
Create a key, then copy it and store it safely.
API keys
Keys for the checkout-api project
Search keys
NameKeyCreated
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
NameKeyCreated
local-devdemo-new-keyJust now
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
Keys are shown once. Store them somewhere safe.
+
Guide1 of 2PagesStep 1 of 2
Go to API keys
Open Settings, then API keys.
API keys
Keys for the checkout-api project
Search keys
NameKeyCreated
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
NameKeyCreated
local-devdemo-new-keyJust now
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
Keys are shown once. Store them somewhere safe.
Step 2 of 2
Click Create key
Create a key, then copy it and store it safely.
API keys
Keys for the checkout-api project
Search keys
NameKeyCreated
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
NameKeyCreated
local-devdemo-new-keyJust now
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
Keys are shown once. Store them somewhere safe.
Home+ Create haikuRecent haikus
Runbooks that match the real screen.
Every step shows the real console with the exact click marked. When a button moves, update that one step, not the whole doc.
- Arrows and highlights
- Edit with AI
- Version history
AnnotateEdit with AISave
API keys
Keys for the checkout-api project
Search keys
NameKeyCreated
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
NameKeyCreated
local-devdemo-new-keyJust now
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
Keys are shown once. Store them somewhere safe.
ArrowHighlightBlur
Edit guideSave draftVersion history
Create an API key
Shipyard · Platform team
Step 2 of 3
Click Create key to make a new API key
In Settings, open API keys and click Create key. Copy the key and store it safely.
API keys
Keys for the checkout-api project
Search keys
NameKeyCreated
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
NameKeyCreated
local-devdemo-new-keyJust now
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
Keys are shown once. Store them somewhere safe.
+
Hand the steps to your AI tools.
Export any guide as Markdown instructions for Claude, Cursor or another AI tool: the steps, the context, and what to check first.
- Export for AI agents
- Download Markdown
- Publish to Confluence or Notion
Edit guideSave draftVersion history
Create an API key
Shipyard · Platform team
Step 1 of 2
Go to API keys
Open Settings, then API keys.
API keys
Keys for the checkout-api project
Search keys
NameKeyCreated
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
NameKeyCreated
local-devdemo-new-keyJust now
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
Keys are shown once. Store them somewhere safe.
Step 2 of 2
Click Create key
Create a key, then copy it and store it safely.
API keys
Keys for the checkout-api project
Search keys
NameKeyCreated
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
NameKeyCreated
local-devdemo-new-keyJust now
ci-runner•••• •••• ••••Mar 12
staging•••• •••• ••••Feb 3
analytics•••• •••• ••••Jan 20
Keys are shown once. Store them somewhere safe.
+
OnboardingCreate an API key ↗
Set up a local-dev API key
Create an API key ↗ Use cases
For releases, new hires and AI tools
Deploys and rollbacks
Record release steps once, so anyone on call can deploy or roll back.
Developer onboarding
Turn access requests and tool setup into guides a new engineer follows on day one.
Cloud config changes
Record console or feature-flag changes step by step, with sensitive values blurred.
Context for AI tools
Give your AI coding tool your team's real process as a Markdown file it can follow.
Why Haiku
Why engineers choose Haiku.
Docs where engineers already look
Publish to Confluence or Notion, export Markdown, or link in a ticket.
Secrets kept out screenshots
Smart Blur hides emails, numbers and form fields while you record.
Built for screens that change
Edit one step or swap a screenshot. The link stays the same.
Ready for your security review
SOC 2 Type II and ISO 27001 certified.
FAQ
Questions, answered.
Yes. It records any web app in Chrome or Edge, including your cloud console and admin panels, and native apps on Mac and Windows.
Haiku is built for screen-and-click work. For command-line steps, add the commands to the step text.
A README describes the screen and goes stale when the UI changes. Haiku shows each screen, and you edit one step at a time.
Only guide creators install the Chrome or Edge extension or the desktop app. Anyone following a guide needs nothing.
Edit the affected steps or swap a screenshot. The link stays the same, so anyone who opens it gets the current steps.
Yes. The free plan includes up to 10 guides and needs no credit card.
Write the runbook. Stop being the runbook.
Start with the task you explain most often.