Stop being the one who remembers.

Most small teams have one person who knows when the key was last rotated and whose IP that is. OpsMinder takes that job with runbooks, deploy logs and an IP and SSH key registry, and tells the team when something is due.

OpsMinder#ops · Mon 09:00
Rotating the prod-db key is due Thursday. Last done 86 days ago. Assigned to j.berg.
JB
j.berg#ops · Wed 15:12
done ✓
You didn't have to ask.
The problem

Small ops chores pile up quietly.

A cloud console listing 23 inbound firewall rules by source IP and creation date, some years old

The allowlist keeps growing

Someone's home IP from two laptops ago. A contractor who finished last spring. Removing a rule you can't place feels risky, so it stays.

A Slack alerts channel at three in the morning: payments-worker is down with an expired API key, and two people asking who owns it

The key that expired on a Saturday

It was issued a year ago by someone who meant to set a reminder. Finding out who could rotate it took an hour.

What OpsMinder does

Keeps the list current, and reminds the team when something is due.

Three jobs. Each has an owner, a date and a record, and each can send a message to Slack, Teams, a webhook or email.

A runbook timeline: two runs done, the next due Thursday

Runbook tracking

Key rotations, backup drills, server updates and other recurring chores. Each has an owner and an interval. The owner gets a reminder a week before it's due, and the team sees when it was last done.

A deploy log with releases and one rejected during a freeze

Deploy logs

Your pipeline sends the repo and commit hash on each release. OpsMinder pulls the commits from GitHub or GitLab and keeps a change log per environment. Start a freeze and releases are rejected until it lifts.

A registry of IP addresses with an owner next to each, one marked as left

IP address registry

Each IP and key has an owner and a reason. When someone leaves or changes machines, their entries are listed, so you know which firewall rules to remove.

Reminders go where the team already is. Pick a channel per job, or per person.
SlackTeamsWebhooksEmail
Pricing

One euro per seat a month.

Everything is included on both plans. Billed yearly.

A team of 4 pays €48 a year.
A team of 12 pays €144.
SOLO
Free

One seat. Free for as long as it's just you.

Get started
TEAM
€1 per seat a month

Two seats or more. Swap developers in and out of seats whenever you like.

Get started
Runbook tracking
Deploy logs and freezes
IP address and SSH key registry
Slack, Teams, webhook and email reminders
Getting started

The first ten minutes.

01
Import what you have

Paste your current IP list or upload the spreadsheet. Add the people on the team.

02
Connect a channel

Slack, Teams, a webhook or email. One channel for the team is enough to begin.

03
Add your first runbook

Pick the chore you most often forget, set an interval and an owner. The first reminder is scheduled.

Where it fits

A list and a reminder. Nothing in your critical path.

OpsMinder is not a security product and does not sit between people and systems. It keeps the record and sends the message.

01
It holds names, dates and addresses.
Not the keys themselves. Your password manager and cloud console stay where they are.
02
Your data stays exportable.
Runbooks, deploy logs and the registry download as CSV or JSON at any time. Leaving takes one click.
03
If OpsMinder is down, your systems are not.
You miss a reminder, at most. That is the intended failure mode.

Start with the chore you forget most.

Free for one developer. €1 per seat a month after that.