Skip to main content
Regulaxy

For IT operations

The hard part isn't the install.
It's the three weeks before it.

The install itself takes twenty minutes. What takes three weeks is finding out who owns that system this year, agreeing a time that suits them, sending the invite, reminding them two days out, and then writing down what was done. That is the part Regulaxy takes over.

Tuesday, at your desk

Thirty systems, and not one of them is yours to decide about.

The inventory knows what exists. It does not know who to ask, when you are allowed, or what is already booked that night.

  • Who owns this system?

    The first question of every window, and the answer is in a table somebody last updated two years ago. Two phone calls before you start.

  • The mail nobody answered

    You asked for approval. A week later you reminded them. Two weeks later you called. The window moved a month.

  • The invite that never reached a calendar

    A plain mail is not an invite. It is read, closed and forgotten. On the night of the window nobody is online.

  • The window that collided

    At 3am it emerges that another team is working on the database yours depends on. You both booked the same night.

  • The write-up done the next morning

    Somebody writes a summary from memory. Half the detail is already approximate.

What changes

One wizard, and what used to be a mail thread becomes a record.

  • The owner is fetched for you

    Type a host name and the product pulls the system owner from the inventory and their mail and phone from AD. There is no first question.

  • Two calendar invites, not a mail

    One to the owner and the contacts, one back to you — so you can accept it onto your own calendar too. An edit updates both; a cancellation withdraws both.

  • An SMS before the window

    A set number of hours ahead, per update type. To the owner's phone, automatically.

  • Collisions flagged while you book

    The product knows which systems are linked because it reads that from the infrastructure. The warning appears as you pick the time, and does not block you — it just stops you meeting it at 3am instead.

  • A checklist instead of a write-up

    A form built in advance, answered while you work, and mailed to everyone involved when the last required question is answered.

What you personally receive

An approved window with a name on it

Date, time, host list, the owner who approved, the contacts, and a signed checklist. Once a week, that is the difference between an evening of work and an evening of phone calls.

We'll run the wizard on your hosts.

Forty minutes. On demo data, or on an inventory export of yours.