atlas Open atlas
LAT 40.7128° N · LON 74.0060° W

Chart the systems your team ships.

atlas is a reference platform for engineering teams who write runbooks, architecture notes, and incident logs. Every page has a coordinate. Every change leaves a bearing. Nothing drifts.

Edition
v4 / Spring 2026
Bearing
N 04° 12'
Depth
2,148 fathoms
Status
In service
CHART I · WAYPOINTS

Every service has a coordinate.

Pin services, queues, and dependencies as waypoints on the chart. Each one carries an owner, a depth reading, and the exact bearing that points to its runbook. New engineers find their footing in an afternoon.

  • 01Owner, on-call, and escalation in one pin
  • 02Cross-link to the upstream and downstream waypoints
  • 03Depth marks degrade-gracefully when the system can
Plot a waypoint →
Fleet / Waypoints 12 in service
40.71°N
74.00°W
Checkout gateway
payments · tier 0 · depth 12f
Active
37.77°N
122.41°W
Vector index
search · tier 1 · depth 6f
Watch
51.50°N
0.12°W
Webhook fanout
platform · tier 2 · depth 4f
Drift
Coordinates / Find 4 results · 12ms
Runbook Checkout gateway: retry ladder CHK-014
Postmortem 2026-02-11 · retry storm PM-077
ADR Adopt token budget per merchant ADR-042
Note Why the checkout queue cost-caps N-211
CHART II · CROSS-REFERENCES

Press cmd K. Land on the right page.

Search reads the chart, not just the title. Type a half-remembered phrase from a postmortem you wrote two years ago, and atlas surfaces the runbook, the ADR, and the incident that drew the line between them. Every result carries its coordinate.

  • 01Backlinks from runbooks to incidents to ADRs
  • 02Coordinate breadcrumbs on every result
  • 03Hot-key access from any page, any time
Try the index →
CHART III · THE LOG

Keep a ship's log of what changed.

Every edit, every incident, every bearing-change is recorded against the page it touched. Open the log on any waypoint and read the last six months of decisions in a single column. No search archeology, no Slack scrolls.

  • 01Diff view between any two bearings
  • 02Incidents thread directly into the runbook they fixed
  • 03Export the log for postmortem review in one click
Open the log →
Log / Checkout gateway last 30 days
04 / 11
14:22 UTC
Incident: retry storm on EU shard
m. okafor · PM-077 · resolved 14:48
04 / 09
09:14 UTC
Bearing: lower retry budget to 3
k. tanaka · CHK-014 · +12 −7
04 / 02
17:51 UTC
Note: token bucket cost-cap merged
l. ferreira · ADR-042 · new doc
03 / 27
08:03 UTC
Waypoint moved: tier 1 → tier 0
e. wright · CHK-014 · depth +6f
FROM THE LOG
“A runbook should read like a chart, not a memoir. atlas is the first tool that gets that. We onboard new engineers in a week now, not a quarter.”
Mara Okafor · Principal Engineer, North Star Logistics
FARE

Two berths. No surprises.

Crew
Crew
$12/ engineer / month

For teams up to thirty. Everything you need to chart a single product surface.

  • Unlimited charts and waypoints
  • Cross-reference search with cmd K
  • The log, kept forever
  • GitHub and Linear bridges
Take the helm
LAT 40.7128° N · LON 74.0060° W

Ship with a chart.

Stop relying on tribal memory and Slack threads from 2023. Give every system a coordinate, every decision a bearing, every page a place on the chart.

Free for the first ten engineers · No credit card · Sail in under five minutes