I will not act above my autonomy ceiling.
Each action type has a lane — safe-to-auto, suggested, or needs-nod. I stay in mine. If a remediation sits above the ceiling you've set for me, I propose it and wait for your nod.
Safe-to-autoAbout — the watchman’s lineage
A hundred-eyed watchman, modernized.
Argus is the agent on the watch. I open the incidents, surface the patterns, draft the postmortems, and ask for your nod when the call sits above my autonomy ceiling. The platform is built to bring back ITIL discipline without the legacy weight.
Argus — in my own words
I'm the watchman. I keep an eye on the systems you depend on, day and night, and I only interrupt you when something matters.
I'm not here to replace the supervisor on shift. I'm here to take the busywork off your hands so you can keep judgment where it belongs.
Every claim I make carries a confidence and sources. If I cannot show the receipts, I do not say it.
The name
In Greek myth, Argus Panoptes was a giant with a hundred eyes, set to watch over what mattered most. Some of those eyes always stayed open, while others rested. Nothing slipped past him.
We named the agent for him because that is exactly the job. An operations watchman is meant to be a steady, attentive presence across every system you depend on — without ever asking you to look in a hundred places yourself.
Why we are building this
Legacy ITSM platforms got the discipline right. Incidents, changes, problems, postmortems, on-call rotations, configuration items — ITIL named these for a reason, and the reason still holds. But the tools that carry that discipline aged badly. They became heavy, licence-locked, specialist-shaped, and slow to use on the days that matter most. Teams quietly drifted to spreadsheets and chat threads, and the discipline got lost along with the bloat.
Argus brings the discipline back without the weight. The agent opens the incident when something moves, classifies the severity, surfaces the past incidents that ring the same bell, and drafts the postmortem from the timeline. The supervisor stays in the decision loop; the agent stays in its lane.
What I will not do
I will not assert without showing the receipts.
Every read I make ships with a confidence score and the log lines, metrics, and past incidents I leaned on. Open the sources drawer on any claim and the trail is right there.
SuggestedI will not erase what I did.
Every action I take lands in the trail with a timestamp, a confidence, and a reversibility window. You can undo me; you can audit me; you can ask me why at any time.
Needs-nodHow Argus fits into Ekarche
Argus is a product of Ekarche, the home of software for the things people actually keep — memory, paperwork, operations. The name pairs Sanskrit eka (one) with Greek arche (origin) — the one origin from which everything begins. Argus is one of three products built around the same principle: software that ages well. Slow architecture, durable formats, no pivots that erase the work users trusted us to keep.
MemoriaYour household's memory, in one calm app.Production-readyDocusiftYour documents, in one clean layer.Production-ready
ArgusYour operations, in one watchful console.In trials
Where we are
Argus is in trials — POC complete, eight engineering milestones past it, and actively building toward design-partner readiness. If the philosophy resonates, join the waitlist. Early feedback shapes what ships first, and you will hear from us when it opens to your tier of access.
How to reach us
Write to hello@ekarche.com. We are based in Mathura, Uttar Pradesh, India.
Want to be a design partner?
I'll learn faster with you on the watch with me. Free production access, a direct line to the team, and the trail is yours from day one.
Join the waitlist