Viapoie is live — voice-first incident response for engineering teams →

Get paged. Answer the call. Fix it without opening your laptop.

Viapoie is the voice approval and execution layer for on-call. When production breaks, Iris calls, explains what happened, and runs the fix you already approved — on your yes.

Alerts in from the stack you already run
Vercel · native
Website checks · built-in
Grafana · webhook
Datadog · webhook
Your AI agent · webhook
[ Problem ]

Pages wake you up.
Dashboards waste your time.

01

Context-free alerts

The pager rings. All it tells you is that something broke. Not what, not where, not how bad — not yet.

02

Laptop out at 3 AM

Four tools open before you can even think about the fix: Datadog, GitHub, the runbook, the deploy history.

03

Six fixes, same shape

The actual action is almost always one of six: rollback, restart, scale, failover, flush cache, page the owner.

[ Solution ]

A voice-first incident commander on every page.

Viapoie listens to your monitors, composes the brief, calls the engineer on rotation, and executes the fix on their command.

The call opens with context.

No dial tone, no robotic alert text. Viapoie opens the call with a plain-English brief: which service, what signal, what changed, and the two or three actions that usually fix it.

  • →Opens with what broke, what the signal is, and what deployed just before
  • →Schedule-aware — respects each responder's call hours and time zone
  • →No answer? The next responder on the roster gets the call
servicepayment-api
signal500s · 1,842 in 5m
memory94% · up 38%
last deploya3f91e2 · 11m ago
ownerpayments-team

Talk back. Ask what you need.

Ask Iris to repeat the summary, spell out the failing check, or walk through exactly what the action will do before you commit. You triage by talking, not by opening a laptop.

  • →Two-way conversation, not a robocall
  • →Unclear answers never execute — Iris re-asks, then escalates
  • →Full transcript stored on the incident record
Monitor trippedassertion failed · 3×
Pulled latest deploya3f91e2 · 11m ago
Loaded runbookrollback · payments-web
Composed briefunder 400 ms
On-call reachedring 1 · roster of 3

Approve the fix. Spoken, logged, executed.

Say rollback, restart, scale up. Viapoie matches it to the runbook you registered, fires it, and writes a full audit trail. Nothing runs that you didn't register for that service.

  • →Pre-declared actions — only webhooks you've registered can fire
  • →Decline or stay silent and nothing runs — approval is explicit, never inferred
  • →Full audit log — who said what, when, and which action ran, with HTTP status
action · rollback.paymentsAwaiting voice confirm
vercel / payments-webpromote dpl_7c20d1b (previous)
health checkgreen in 41s
approved bypriya.k · registered responder
timelineinc-20461 · 9 events logged
[ How it works ]

From alert to resolved. Without opening a laptop.

01 · Fire

A monitor trips

A website check fails, a Vercel app breaks, or any tool you run POSTs an alert to your signed webhook endpoint.

02 · Compose

Context, not noise

Viapoie pulls what changed — including your latest production deploy — and the runbook for that service, and composes the brief.

03 · Call

Dial the roster

Iris calls your on-call. No answer? She dials the next responder on the roster until a human picks up.

04 · Execute

Run the fix

You say yes. Viapoie fires the registered runbook, polls the health check until it comes back green, and logs every step.

[ Multilingual ]

Respond in the language you think fastest in.

Pager at 3 AM is not the time to translate. Viapoie understands and speaks the major global engineering languages. And because the agent repeats every production action back to you verbatim, language flexibility never widens the blast radius.

  • →Understands and speaks the major global engineering languages — English, Spanish, Hindi, Portuguese, Japanese, French, German, Mandarin, Arabic
  • →Code-switch mid-sentence — mix English service names with your native prose
  • →Noise and accent-tolerant transcription on telephony-grade audio
  • →Every production action is read back verbatim before it runs — nothing executes on an ambiguous phrase
Confirm patternsame action · three languages
Englishen-US
Confirm: restart only payments-api-prod-2 in ap-south-1. Say confirm, or press 1.
Españoles-MX
Confirmar: reiniciar solo payments-api-prod-2 en ap-south-1. Diga confirmar, o presione 1.
日本語ja-JP
確認: ap-south-1 の payments-api-prod-2 のみを再起動します。confirm と言うか、1 を押してください。
[ Scoped execution ]

Iris only runs what you registered. That is the entire trust model.

Register a runbook — a Vercel project to roll back, or a webhook you own. On the call, Iris reads the action back and fires it only after your yes. No registered runbook, no execution — not even by voice.

  • →Scoped execution — only runbooks you registered can ever fire
  • →Alerts in from anything that can POST JSON — Grafana, Datadog, Alertmanager, or your own AI agent
  • →Native Vercel rollback — say yes and the previous production deployment goes live
  • →Unclear never executes — Iris re-asks once, then escalates. Silence runs nothing
  • →Every step on the timeline — who was dialed, what they approved, what ran, with HTTP status and latency
wake-iris.httplive
# Any monitor, script, or AI agent can wake Iris
POST /api/webhooks/alerts/<your-endpoint>
x-viapoie-signature: sha256=…

{
  "title": "Checkout 5xx rate above 2%",
  "severity": "critical",
  "summary": "502s spiked four minutes after the 02:14 deploy."
}

# → Iris calls your on-call with this context.
# → On "yes", the registered rollback fires.
# → The timeline gets the receipt.
[ Pricing ]

Start with one service. Expand when Viapoie earns your trust.

Priced per workspace and per protected service — never per responder. Adding engineers to your rotation should make incidents faster, not more expensive.

Sandbox
Free
Testing the voice experience
  • →1 protected service
  • →1 responder
  • →10 simulated incidents / month
  • →2 real incident calls (lifetime)
  • →Real webhook & Vercel runbooks
  • →Multilingual voice testing
Test an Incident
On-Call
$149/ month
Small engineering teams
  • →3 protected services
  • →5 responders
  • →100 incident calls / month
  • →Vercel rollback + webhook runbooks
  • →No-answer roster escalation
  • →Multilingual incident calls
  • →Full action history
Start 14-Day Trial
Enterprise
Custom
Regulated and large organizations
  • →Unlimited responders
  • →Custom service limits
  • →SSO, SAML, SCIM
  • →Multi-party approval policies
  • →Private execution runner (roadmap)
  • →Custom data retention
  • →Security review & SLA
  • →Dedicated support
Talk to Engineering
Launch pricing.Annual billing available — two months free.Compare all features →
[ Platform Integrations ]

Connect Viapoie to the stack that pages you.

Alerts come in through Vercel, built-in website checks, or a signed webhook from anything that can POST JSON. Execution goes out through Vercel rollback or webhooks you own. No agents to install.

VCVercelLive
WCSite checksLive
WHWebhooksLive
GRGrafanaVia webhook
◆Viapoie
DDDatadogVia webhook
AMAlertmanagerVia webhook
OGOpsgenieParser soon
SLSlackComing soon
[ FAQ ]

Frequently Asked Questions

Answers to common questions about Viapoie and how it fits your on-call.

What is Viapoie? +
Viapoie is a voice-first incident commander. When a production alert fires, it calls the on-call engineer, explains what broke and what deployed just before, talks through the options, and executes the registered fix — a Vercel rollback or a webhook you own — on a spoken yes.
How is this different from PagerDuty's call feature? +
PagerDuty calls you with text-to-speech of the alert title. Viapoie's call is a two-way conversation: Iris explains what failed and what changed, answers questions, and executes the registered fix the moment you approve it. And if you don't pick up, she dials the next responder on your roster instead of going quiet.
What can the agent actually execute? +
Only runbooks you register — a Vercel project rollback or a webhook URL you own. If no rollback runbook is registered, nobody can approve a rollback, not even by voice. Iris reads the exact action back before running anything, and an unclear answer never executes.
Which tools does it connect to? +
Natively today: Vercel, with deploy context and one-command rollback, plus built-in website checks that can assert on response content, not just status codes. Beyond that, signed webhook alerts — so anything that can send a webhook works now: Grafana, Datadog, Alertmanager, UptimeRobot, cron jobs, or your own AI agent. Native payload parsers and Slack streaming are next.
Is it safe to grant webhook execution over the phone? +
Workspace admins choose who Viapoie calls and which runbooks they can authorize by voice. Viapoie executes only those permitted actions, records the approval and execution history, and checks recovery. In phone-based authorization mode, your organization trusts whoever answers the registered number — the same contract you already accept with your existing paging tools.
Does it work in languages other than English? +
Yes. Viapoie understands and speaks the major global engineering languages — English, Spanish, Hindi, Portuguese, Japanese, French, German, Mandarin, Arabic — and tolerates code-switching with English service names. Multilingual flexibility never widens the blast radius: every production action is read back verbatim and requires explicit confirmation before it runs.
Can we deploy inside our VPC? +
Not yet — today Viapoie runs as a managed cloud service. An outbound-only execution runner that keeps credentials and execution inside your VPC is on the Enterprise roadmap. If that's your requirement, email team@viapoie.com and we'll talk through it.

Your next incident
shouldn't need a laptop.

See Viapoie answer a real alert, pull the context, and run the fix on your voice. Book a 20-minute walkthrough with the team.