A SITE BUILDER FOR SRES

The outage you fixed in 38 minutes belongs on your site.

Nines turns your incident write-ups, uptime figures, tooling and certifications into a one-page site that shows how you handle production. It runs in your browser with no sign-up, and nothing you type leaves it.

No sign-up · Autosaves in your browser · Exports one HTML file

SEV1 14 Mar 2026 ✓ Resolved · 38 min

Checkout outage during regional failover

  1. 14:02 Failover begins. Traffic moves to the secondary region.
  2. 14:06 Detected · 4 min. A synthetic checkout probe alerts.
  3. 14:40 Resolved · 38 min. Traffic routed back, stuck queue drained.

Follow-ups

  • Add replica lag to failover pre-flight checks
  • Rehearse regional failover every quarter
  • Alert on session errors per region

Why Nines

Portfolio builders ask for screenshots of things you made. Your best work is a pager that stayed quiet, a deploy pipeline that went from weekly to daily, and an error budget that held. Nines has a place for all of it.

Built for blameless write-ups, DORA figures, tooling matrices and expiring certifications.

HOW IT WORKS

Three steps, no sign-up.

  1. 01

    Write it down.

    Guided forms for your profile, incident stories, reliability wins, tools and certifications. Clear messages catch a bad link or an impossible uptime as you type.

  2. 02

    Arrange and preview.

    Move sections up or down, hide what you're not ready to share, and switch between three themes. The preview beside the forms is the exact file you'll download.

  3. 03

    Export.

    Download one self-contained HTML file to host anywhere, a JSON backup to move your work, and a print-ready résumé built from the same data.

WHAT GOES ON THE PAGE

Shaped around how reliability work is described.

Incident stories, written blameless.

Every story follows a real postmortem: impact, detection, response, root cause and follow-ups, plus time to detect and time to resolve. If a word like "fault" or "human error" slips in, Nines points it out. It never stops you saving.

The deploy failed because of a careless config change.

Blameless check: "careless" in Root cause. Describe what the system allowed, not who slipped.

Figures that mean something.

Add uptime, deploy frequency, MTTR and change failure rate, or a metric of your own. Give a previous value and the change is worked out for you. Uptime is translated into the downtime it allows, so readers see what 99.95% means.

Uptime
99.95%
was 99.5% · ≈ 4h 23m downtime / year
Deploy frequency
14 / week
+600% · was 2 / week
Mean time to recovery
18 min
−85% · was 2h
Change failure rate
4%
−73% · was 15%

Your stack, at a glance.

Tools grouped by category in a sensible order (cloud, infrastructure as code, CI/CD, containers, observability, incident response, languages) and marked Expert, Proficient or Familiar. Duplicates are caught for you.

Category Expert Proficient Familiar
Cloud AWS — Google Cloud
Containers Kubernetes Docker —
Observability Prometheus Grafana —

Credentials that keep themselves honest.

Add issue and expiry dates, a credential ID and a verification link. Nines marks each one valid, expiring soon or expired, and keeps expired ones off your public site and résumé automatically.

  • AWS Certified Solutions Architect – Professional Valid
  • HashiCorp Certified: Terraform Associate Expiring soon · 42 days
  • Certified Kubernetes Administrator Expired · hidden from site

THREE THEMES

Pick a look. Change your mind any time.

Switch themes in the builder and the preview changes at once. Every theme uses system fonts and no scripts, so the exported file loads instantly and makes no requests.

TRY IT HERE

This is the real builder.

It's running right here in the page. Press Load example to fill it with Alex Rivera's site, then change a theme or edit an incident and watch the preview follow.

Your work autosaves to this browser's local storage.

Open it full screen →

WHAT YOU TAKE AWAY

Three files. Zero servers.

Nothing you type leaves your browser. There are no accounts, no analytics and no servers. Your data lives in local storage until you export it.

Write the postmortem you're proud of.

Open the builder, load the example, and have your own site by the end of your next on-call handover.

Open the builder

Free · Runs in your browser · No sign-up