Is this a sales call?
It is a working session about your situation. Where we are not the right people we say so, and say who might be.
Book a briefing · Reign Ops
Hand over the part of the work that never finishes.
Bring us the toolchain and the open source estate beneath it, and we will tell you what we would take on first and what we would leave alone. That second half is the useful part of the answer.
- A plain answer on fit, including when we are not the right people.
- What we would look at first: your estate.
- A working session on your situation, not a product demo.
Delivered as a single-tenant dedicated instance, in infrastructure iTmethods operates or in your own cloud account on AWS or Azure. Both are available today. Air-gapped and sovereign deployment are supported.
- Two decades operating regulated & SDLC platforms
- SOC 2 Type II compliance
- Dedicated and single-tenant
- FINOS member
After you send it
Three steps, and the first is a person.
A person reads it
Not a rule that files it under a topic. A question about how a platform is operated is answered by the people who operate it.
We reply within one business day
To propose a time, or to say we are not the right people and who might be. You can decline.
A 30-minute working session
The platforms you run and what is forcing the question. Nothing is booked, bought or committed until you decide.
What to bring
The estate you already run, and what keeps slipping.
Four shapes this conversation usually takes. Three of them are a situation; the fourth is a date.
01Version currency keeps losing
Upgrades are understood, agreed and never quite the most urgent thing in the week.
This is the ordinary case and it is what Reign Ops exists for. Version currency becomes our work rather than a ticket waiting for a quiet week.
AskWhat is the oldest version you are still running in production?
02The pager is the problem
Somebody on your team holds the pager for a toolchain that is not the product you sell.
The pager goes to us instead, to a named engineer with a current runbook.
AskWho would get their evenings back?
03The open source estate underneath
The tools your engineers use sit on an estate that nobody owns end to end.
Scanners report findings with context into the work; they do not block, and you decide the order.
AskWhich finding has been open longest, and why?
04A date is driving it
An end-of-life deadline you did not choose, on a platform you cannot simply stop using.
This is the sharpest version of the conversation because the scope is set by somebody else and the deadline is real. Bring the date and the platform. The Atlassian Data Center path →
AskWhat happens on the day if nothing moves?
Readiness
What we would want to know on the first call.
Less a checklist than the four things that make a scoping conversation useful rather than exploratory. None of them needs preparing in advance; if you know two of the four, write anyway.
1
Which platforms, and which versions
The tools your engineers use every day and roughly where each one sits. Approximate is fine. Nobody has this exactly right and pretending otherwise wastes the call.
2
Who holds the pager today
Whether that is a named team, one person, or nobody in particular. The answer changes what we would take on first.
3
How change gets approved
We run to your change control, so the shape of it is the shape of the service. An upgrade is scheduled through your process, at a time you agree.
4
What is actually forcing the question
A deadline, a departure, an audit finding, or simply that it has been deferred twice. This is the one that decides whether now is the right time.
What stays yours either way. Your repositories, your code, your data and your decisions about what ships. Adoption is additive: the pipeline you already run keeps its wiring.
What you get back
What we would take on, and what we would leave.
A scoped answer rather than a proposal that assumes the answer is everything.
At the end
What you would have
Written down, before anything moves
A scope with a boundary on it. What we would operate, what stays with your team, and the order we would do it in.
The service levels and the change path. Held to your change control, with named engineers rather than an on-call rotation and a shared inbox.
An honest view of what we would not touch. Some of an estate is better left where it is, and saying which part is most of the value of the first conversation.
Stated, not hidden
What we will not give you
The limits, in the same voice as the offer
A published operating metric. There is no uptime figure, no service-level number and no operating metric published anywhere on this site. Two decades of doing the work is the evidence, and we would rather say that than print a number nobody signed off.
A shared or multi-tenant option. Single tenancy is the only model on offer, in either deployment, and there is no SaaS tier behind it.
A price on this page. Commercial terms are agreed in writing with you.
Two engagements are written up and cleared for use by the customer, anonymized. Read them →
Next step
Tell us what you run.
The platforms, roughly which versions, and what is forcing the question. We will come back with what we would take on first and what we would leave alone.
Before you write
Questions people have first.
What should I bring?
The platforms you run, roughly which versions, and what is forcing the question. Approximate is fine.
Who will I speak to?
The people who operate and build Reign, not a booking queue.