About

Observe. Alert. Respond.

SkyLogs started as an internal tool for a team drowning in alerts. It's now an open-source incident response platform anyone can self-host.

Why the bird

A sentinel, not a dashboard.

The prinia on our mark is a small, alert bird that calls the moment something moves. That's the job: notice early, tell the right person, stay out of the way.

SkyLogs logo — a prinia bird above the skylogs wordmark

Principles

What we optimise for

Your data stays yours

Incident data describes your infrastructure. It should live where you decide — no telemetry, no forced cloud.

API before UI

Every action in the interface is an endpoint first, so SkyLogs fits into automation instead of blocking it.

Built for responders

Designed around the person being paged at 3am, not around a procurement checklist.

Open by default

Source, roadmap and discussion happen in public. Contributions are the point, not an afterthought.

History

How we got here

  1. 2024

    Internal tool for routing Prometheus alerts to the right on-call team.

  2. 2025

    Escalation chains, schedules and multi-channel notification delivery.

  3. 2026

    Public open-source release and the first managed workspaces.

Contribute or self-host.

Read the docs, run it on your own infrastructure, and open an issue when something doesn't fit your workflow.