One address reaches the person who wrote the code.

Name: OperativeOps
Author: Aman Priyadarshi

CANONICAL — EVALUATION · LICENSING · SUPPORT · SECURITY · PRESS

contact@operativeops.com

SECURITY REPORTS — SAME ADDRESS, SUBJECT STARTING SECURITY: — READ FIRST · SEE /SECURITY

WHO ANSWERS

OperativeOps is built and maintained by one engineer — Aman Priyadarshi, working from Mumbai. Mail goes to him, not to a queue. No account manager, no call deflection, no support tier between you and the person who can actually fix it.

WHEN

First reply within 2 business days; security and evaluation mail first. Business hours are IST (UTC+5:30) — expect answers on European mornings.

CALLS

By arrangement over email — a scheduled call beats an unannounced one across four time zones. Video or phone, your choice of tool.

STRAIGHT ANSWERS

The questions you were going to ask anyway.

Answered here rather than discovered later, because a diligence reader always finds out.

“IS THIS A COMPANY?” OperativeOps is a product, not a corporation with an office to tour. Independently built, sold as a one-time perpetual licence, supported directly by its maintainer. For a buyer who has sat through enough vendor calls, that is the feature: nothing between you and the source.

“WHAT IF YOU GET HIT BY A BUS?” Your licence is perpetual and your deployment is yours — it keeps running with no vendor dependency, no phone-home, no licence server to go dark. Source access for continuity is part of the licence conversation; ask.

“WHAT HAPPENS TO MY EMAIL?” It sits in the mailbox and is answered. It is not entered into a CRM, not enriched, not subscribed to anything. Details in the privacy policy, part A.

NO CONTACT FORM — DELIBERATELY

A form implies a pipeline, a ticket number, and a team behind it. There is a mailbox and a person. Publishing the address plainly is more honest than a form that would post into the same mailbox anyway — or worse, into nothing.