1. Why we built this
Every engineering team ships a product that eventually pages someone at 3 AM. The next twenty minutes are the same every time: find the laptop, open the dashboard, open GitHub, open the runbook, re-load the context you had yesterday, pick an action from a short list of options you've run a hundred times before.
Viapoie collapses those twenty minutes into one phone call. The brief arrives in your preferred language, the actions are the ones your admin already approved, and the fix runs on your voice. The dashboard holds the full timeline and audit — but the engineer never needs to open it to resolve a routine incident.
We built Viapoie because the gap between “pager rings” and “fix dispatched” is where tired engineers burn out and simple incidents get worse. The voice is just the interface — the real product is the discipline it enforces: pre-approved runbooks, verbatim read-back of every action, and a tamper-evident record of what was said and what was done.
2. Who's behind it
Viapoie is operated by Harjobandeep Singh, an individual engineer based in India. The project started as a weekend-and-nights build in October 2026 after one too many 3 AM pages on a service that, in hindsight, needed the same rollback as the previous four pages that quarter.
We are not an incorporated company at this time. For all product, support, and partnership enquiries, email team@viapoie.com.
3. How we work
The product has one job: deliver the right incident brief to the right responder, listen for their decision, and carry it out safely. Every design choice flows from that.
- Admins declare what Viapoie is allowed to do. Only runbooks explicitly registered by a workspace admin can fire. The agent cannot invent an action, improvise a webhook, or escalate beyond the registered list.
- Responders authorize at run time by voice. The agent reads the action back verbatim before dispatching. “Confirming rollback of payments-api-prod-2. Say confirm to proceed, or cancel to stop.” Nothing executes without an explicit yes.
- Multilingual means the languages your engineers think fastest in. Nine languages at launch, with code-switching for English technical terms. “Payment-api” stays “payment-api” whether the surrounding sentence is in Hindi, Spanish, or Japanese.
- Audit is first-class. Every call, every spoken instruction, every webhook fire lands in the dashboard and in a tamper-evident log. Post-incident review stops being a scavenger hunt across chat channels.
4. What we believe
- Pre-approval beats real-time improvisation. The right action during a 3 AM incident is almost always one of six things. Declaring those six in advance and letting the responder pick by voice is safer than any AI that proposes novel fixes mid-call.
- Honest about what we don't solve. Viapoie does not verify who answers your registered phone number. That's your organization's responsibility — the same contract you already accept with PagerDuty or Opsgenie. We document this plainly instead of pretending voiceprints are a security primitive.
- Keep your existing paging alive. Viapoie is additive to the on-call tooling you already run. If we go down, your paging keeps working. If a specific call fails to connect, your escalation continues down whatever list your organization already maintains.
- Build in India, support globally. We're headquartered in India, launched with Indian engineering teams in mind, and designed the voice pipeline around code-switching from day one. The same product serves teams anywhere else without compromise.
5. Reach us
General, support, sales, partnerships: team@viapoie.com
We read every email and reply within one business day. Response times during an incident on our own infrastructure may be longer; the status of the Viapoie service itself is posted on this page as it changes.
Operator: Harjobandeep Singh, an individual based in India, operating under the name “Viapoie”.
Country: India
Legal pages: Privacy Policy · Terms of Service · Refund Policy