An import that checks itself
For every schedule, Transmit asks Opsgenie who is on call right now and puts its own answer next to it. If a rotation did not map exactly, you see the mismatch and why, before you apply.
Opsgenie stops on 5 April 2027182 days left
The pager for when everything else is down.
Transmit pages whoever is on call and keeps escalating until someone answers. It imports your Opsgenie account and speaks Opsgenie’s API, so your integrations only need a new URL and key.
Pages go out by email today. SMS and voice calls are coming soon.
A sample incident in the Transmit dashboard. An alert from Alertmanager opens an incident for checkout-api. Escalation pages Dana Reyes, who is on call, by email. Dana acknowledges from the email, which stops escalation, and the incident resolves when the alert clears.
The way off Opsgenie
Built for the move, not just after it.
Atlassian shuts Opsgenie off on 5 April 2027 and deletes what was not migrated. Transmit brings your schedules, escalation policies, services and heartbeats across, and shows you exactly what it will do before it writes anything.
Same API, new URL
Alertmanager, Grafana and your own scripts keep speaking Opsgenie’s Alert API. Change the URL and the key; aliases, deduplication and close-on-resolve work as before.
Heartbeats come too
Names, intervals, messages and priorities carry over. The ping keeps Opsgenie’s shape, and an imported heartbeat starts watching at its first ping to Transmit.
Run both side by side
Nothing pages until you repoint a sender. Send alerts to both systems for a few days, compare, then switch. Re-import as often as you like; it updates what it made.
Repointing Alertmanager
The whole change is two lines.
Alertmanager has spoken Opsgenie for years. Point its api_url at Transmit and use the service’s new key. Everything else in your config stays as it is.
# alertmanager.yml
receivers:
- name: transmit
opsgenie_configs:
- api_url: https://oncall-api.transmit.dev/
api_key: tik_... # the service's keyWhat works today
Honest about what is ready.
Transmit is in early access. Paging is proven end to end in production, by email. Here is the line between what you can use now and what is next.
Ready
- Email pages with a one-click acknowledge
- Escalation policies with steps, delays and repeats
- Schedules with rotations, restrictions and overrides
- Heartbeats for cron jobs and backups
- Opsgenie import, checked against Opsgenie
- Opsgenie-compatible Alert and Heartbeat API
- Alertmanager and generic webhooks
- REST API with OpenAPI 3.1 documents
Coming soon
- SMS and voice calls
- Self-serve sign-up (early access for now)
An email at 3am rarely wakes anyone on its own. Until SMS and calls are on, the migration guide shows how to make Transmit’s emails break through Focus and Do Not Disturb.
Reliability
A pager has one job: work on your worst day.
Postgres decides every timer
Every escalation step and page is written in the same transaction as the change that caused it. Nothing is held only in memory, so a restart loses nothing.
Always on
The worker that fires escalation timers never scales down, so a step due at 3:02 pages at 3:02, not whenever the next request wakes something up.
Watched from outside
A separate watchdog on Cloudflare checks Transmit every minute, and Transmit watches the watchdog back with a heartbeat.
Product
Everything between the alert and the person.
Paging and escalation
Steps with delays, repeats, and a fallback to owners when nobody on a step can be paged.
Schedules that survive DST
Layered rotations, time restrictions and overrides, property-tested across time zones.
Integrations
Opsgenie’s API, Alertmanager, a generic webhook, heartbeats, and a typed REST API.
Move before the deadline, not on it.
Transmit is in early access. Tell us about your on-call setup, and we will help you import it and check it against Opsgenie before you switch.