WakeUp Dev FAQ

WakeUp Dev is a voice-first on-call alerting platform. It receives critical alerts from monitoring systems via HTTP webhook, places a phone call to the on-call responder, and requires explicit acknowledgement by pressing 1 on the phone keypad.

Push notifications, email, and chat can be missed when you are asleep or away from your desk. WakeUp Dev is designed for incidents where a human must actually respond—not just receive another notification.

DevOps engineers, SREs, and small teams that need critical production alerts to reach a human on call. It fits teams using Grafana, UptimeRobot, or any monitor that can send HTTP webhooks.

Your monitor sends POST https://api.wakeupdev.com/v1/alert with your x-api-key. WakeUp Dev validates credits, summarizes the payload for voice when Groq is configured, starts an on-call cascade, and calls the first target. The responder presses 1 to ACK or the system escalates.

WakeUp Dev is a lightweight, voice-first option focused on webhook-to-phone-call alerting with human ACK and usage-based pricing (not per-seat licensing). It is not a full incident management suite like PagerDuty. Teams often use it when they need phone escalation without adding another seat license for every engineer.

A phone call can cut through silent-mode push, unread email, and busy chat channels in a different way than text notifications. WakeUp Dev adds an explicit ACK step so you know someone confirmed the alert—not just that a message was delivered.

ACK (acknowledgement) means a human confirms they received the alert. During the call, WakeUp Dev asks the responder to press 1 on the keypad. When digit 1 is received, the alert is marked ACKNOWLEDGED and escalation stops for that incident.

Twilio connects the call, plays a voice summary of the alert, then prompts: press 1 to confirm. The IVR callback records digit 1 and marks the alert acknowledged in the database via oncall_marcar_ack.

If the call is not answered, fails, or completes without ACK within the wait window (about 45 seconds while calling), WakeUp Dev claims the timeout and calls the next phone in the cascade—up to 8 attempts across shift phones, roster members, or your verified emergency number.

Targets are chosen in order: active on-call shift phones, then roster members sorted by orden_escalamiento, then your account verified emergency phone. Each failed or unanswered attempt moves to the next target until someone ACKs or the list is exhausted (EXHAUSTED).

Yes. Configure Grafana to send an HTTP webhook to POST /v1/alert with your x-api-key header. Send the alert body as plain text or JSON—WakeUp Dev reads the raw request body.

Yes. Point an UptimeRobot webhook alert to https://api.wakeupdev.com/v1/alert. WakeUp Dev requires the x-api-key header. Check that your UptimeRobot webhook configuration supports custom HTTP headers before using this integration. UptimeRobot's default webhook payload can be used as the alert body.

Yes. Any system that can POST HTTP with a custom header can integrate. The endpoint expects POST, header x-api-key, and a request body up to 4000 bytes.

Yes, as long as it supports outbound HTTP POST webhooks. There is no proprietary agent—only the public /v1/alert API.

A cascade is the ordered list of phone numbers WakeUp Dev calls for one alert. It can include shift-based phones, a CSV-imported roster, and a fallback verified phone on the account.

Yes. Import multiple roster members with escalation order, or define weekly shifts. If the first person does not ACK, the next number is called automatically.

In the dashboard you can import a CSV with columns: nombre, telefono, orden, email. orden (orden_escalamiento) sets call priority—1 is first. The same import replaces the roster atomically.

Signing up with GitHub includes 5 free voice alerts for testing. No credit card is required for the trial plan shown on the website.

Pro International: 50 monthly alerts for $29 USD/month (Lemon Squeezy), +$0.50 USD per extra dispatched alert. Pro Chile: 50 monthly alerts for 25,000 CLP/month (Transbank Oneclick), +450 CLP per extra alert. Both include unlimited users.

No. WakeUp Dev charges based on dispatched alert volume, not per-seat licenses. You can add engineers to the workspace without opening a new license line for each person.

API keys are stored as hashes in Supabase (with optional pepper on the Worker). The dashboard shows a newly generated key only once; the Worker validates x-api-key against the hash, never the plain text.

GitHub OAuth is the primary sign-in method. After Chile checkout, a magic link can be sent to the payer email to claim the account without GitHub.