For services, dependencies and runbooks
Service notes that draw their own map.
Write one note per service and link what it depends on, in the text or in a property. The graph draws the dependency map from those links, each type of note becomes a table, and a board lays the system out by hand when a picture says it better.
Solo is free. An orb started here begins with Kubernetes, a Redis runbook and an incident template to build on.
# every capture lands at the top of today's daily note
Or try one
Today's timeline
- Nothing logged yet. Press Enter in the terminal and it lands here.
A live demo with five sample notes. The link matching is the same code the product runs.
Features
Built for the system you run
Every note is Markdown, and every link, property and type in it is something you can search, sort and draw.
Dependencies are links
Write
depends_on: ["[[Postgres]]"]in a service's properties, or mention a service in passing, and the graph draws the wire. Its backlinks list every note that depends on it.Every type is a table
Give notes a type such as Service or Runbook, and every note of that type becomes one table you can sort by its owner, its tier or any other property.
Boards for the big picture
Lay services, notes and cards out on an infinite board when an arrangement says more than the graph: a migration, a request's path, a war room.
Runbooks you fill in, not retype
A code block with placeholders like
<NAMESPACE>renders fill-in fields. Copy gives you the finished command, not the template.Read a runbook from the shell
orb_show redisprints the note exactly as written, by title, alias or path, so its commands can be read or piped in the terminal that will run them.Mentions waiting to be wired
Unlinked mentions lists the notes that name a service without linking it, each one click from a wire, so the map catches up with what you wrote.
Write down the first service
Create an orb and write a note for one service. Link what it depends on, and the map starts drawing itself.