The terms for using OpsMinder.

1. Who you are agreeing with

OpsMinder is a service of Tocabi Software B.V., Arnhem, the Netherlands, Chamber of Commerce number 78396026 ("we"). By creating an account or joining the waitlist you agree to these terms on behalf of yourself and, if you set up a team, on behalf of the organisation the team belongs to ("you").

2. What OpsMinder is

OpsMinder keeps lists: runbooks and their runs, releases and freezes per environment, and a registry of IP addresses and SSH public keys. It sends reminders to the channels you connect and answers your pipeline, CLI, Terraform or API calls about freezes and the registry.

It is not a security product. It does not hold credentials, does not sit between people and your systems, and does not deploy anything itself. Your tools decide what to do with its answers.

3. Your account

You need to be 18 or older and give us a working email address. You are responsible for what happens under your login and for keeping it to yourself. Tell us at privacy@opsminder.sh if you think someone else has it.

The team owner decides who is in the team and in which seat. We follow the owner's instructions about the team's data.

4. Seats and payment

The Solo plan is one seat and free, without a credit card, for as long as it is one seat.

The Team plan is two seats or more at €1 per seat per month, billed yearly in advance: €12 per seat per year, excluding VAT. A seat is one login, or one person who owns a runbook, an IP address or an SSH key. You pay for the number of seats, not for who is in them, and you can swap people in and out of seats at any time.

Adding a seat during the year is charged for the remaining months. Removing a seat is credited on the next invoice. If you go back to one seat, the account moves to Solo at the next renewal.

Payment is handled by Mollie. The subscription renews each year unless you cancel before the renewal date. Because the price is €1 a seat, we do not offer monthly billing or refunds for part of a year, other than the credits described above. We may change prices with 60 days' notice by email; the new price applies from your next renewal.

5. What you may not do

Use OpsMinder to break the law, to store data you have no right to store, to attack or overload the service, to resell it, or to get around a seat count. Register only IP addresses and keys that belong to your team. If we see this happening we will contact you first, unless the harm is immediate, in which case we may suspend the account and explain afterwards.

6. Availability and what we promise

We run OpsMinder with care and aim to keep it available, but we do not offer an uptime guarantee at this price. Planned maintenance is announced in advance where we can.

OpsMinder is designed so that if it is down, your systems are not. A missed reminder, a freeze check that cannot be answered, or a registry your pipeline cannot reach are the failure modes you should plan for, and your tooling decides how to handle them. We are not responsible for deploys that went out, chores that were missed, or firewall rules that were kept or removed as a result of using or not being able to use OpsMinder.

7. Your data

Your data stays yours. We use it only to run the service, as described in the privacy policy. You can export everything as CSV or JSON at any time. After cancellation it remains readable and exportable for six months, then it is deleted.

8. Integrations

Connecting Slack, Teams, GitHub, GitLab or any other service is your choice and subject to those services' terms. You can disconnect them at any time. If a service changes in a way that breaks an integration, we will try to fix it but cannot promise when.

9. Ending the agreement

You can cancel at any time from the account settings. The service continues until the end of the paid period. We can end the agreement with 60 days' notice, or immediately if you break section 5 or do not pay. In both cases section 7 applies to your data.

If we ever stop offering OpsMinder, we give at least 90 days' notice and keep exports available for that period.

10. Liability

We are liable for direct damage caused by our failure to meet these terms, up to the amount you paid us in the twelve months before the event. We are not liable for indirect damage such as lost revenue, lost data you had not exported, or costs of a deploy or outage. This does not limit liability that cannot be limited under Dutch law, such as for intent or gross negligence.

11. Changes to these terms

If we change these terms in a way that matters, we email account owners at least 30 days before the change takes effect. If you do not agree, you can cancel before that date. The date at the top shows the current version.

12. Law

Dutch law applies. Disputes go to the court of Gelderland, location Arnhem, after we have first tried to resolve them by talking.