Overview / Request a demo
Request a demo
Which transaction would you want followed first?
A monitoring tool shown against a vendor's own tidy example looks impressive and settles nothing. Name the business operation that actually costs you sleep — the order, the claim, the payment run — and the session gets built around that one instead.
Where does this request go once you send it?
- Into contact@optier.com, and into no database, no sales tool and no marketing platform of ours. The external form-to-email service that carries it there is named and described on the privacy page.
- In front of an engineer who works on OpTier, and the answer you receive is written by that person.
- Back to you with a straight answer if the approach looks wrong for your situation — that gets said in the reply, rather than a session being arranged regardless.
- Nowhere near a mailing list, since this company runs none to add you to.
What actually happens in the session?
An hour or so, worked against a prepared example rather than against anything you have running. One transaction gets walked from its first hop to its last; the trace is read out loud, including the parts of the journey it cannot see; a baseline is fitted to it; and then the example is broken deliberately so you can watch what the alerting says and judge whether that wording would have helped you at three in the morning.
Nothing gets installed anywhere and no access to your estate is requested at any stage. If reading a written answer suits you better than sitting through a demonstration, say so — a description sent to contact@optier.com comes back answered in writing, which is a legitimate way to evaluate this and not a lesser one.
What is worth putting in the message?
Four facts shape the hour more than any other detail you might send: the name the business uses for the transaction, roughly how many systems it crosses, whether any of those systems belong to another organisation, and the single question you currently cannot answer about it. Anything beyond those four is welcome colour rather than a requirement.
What will you never be asked for?
- Access to your systems. Not at this stage, not at any later stage of the conversation — this is software you would run yourself, not a service that reaches into your estate.
- Production data, log extracts or captured traces. A drawing on a whiteboard conveys what we need and costs you no review cycle.
- An architecture document. A sketch of the hops with the owning team written beside each one is more useful and takes about ten minutes.
- A decision on the day. Where the honest conclusion is “instrument two boundaries yourselves first and see whether the picture improves”, that is what gets said.
Every page on this site was written by the people building the product. If a statement here is wrong, or a limitation is missing from the list of things the software does not do, write and it gets corrected.