Skip to content
View LindqvistMartin's full-sized avatar

Block or report LindqvistMartin

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
LindqvistMartin/README.md

.NET / C#, React + TypeScript, PostgreSQL. Some Go.

Building self-hosted alternatives to SaaS-only ops tooling. The three are built to chain: pulsewatch to detect, sluice to route webhooks, flare to run the incident.

  • pulsewatch — reliability dashboard: probes, SLOs, error budgets, public status pages (live demo)
  • sluice — webhook fan-out daemon in front of the incident tools (Go, early)
  • flare — incident management: append-only timeline, auto-drafted postmortems, MTTR/MTTA (live demo)

In .NET OSS, I had a LinkedHashSet→OrderedHashSet sweep merged into Apache Lucene.NET (#1313).

Pinned Loading

  1. pulsewatch pulsewatch Public

    Self-hosted reliability dashboard. Probes, SLOs, public status pages - without the SaaS bill. .NET 10, React 19, SignalR, Postgres.

    C#

  2. flare flare Public

    Self-hosted incident management. From alert to postmortem - without the SaaS bill. .NET 10, React 19, SignalR, Postgres.

    C#