What's New
We ship improvements continuously, and this page is where they land. It's updated as we release new features, enhancements, and fixes — so check back to see what's changed.
🔌 Monitor any Windows service, and migrate off PagerDuty
Updated — August 28, 2026
Windows Service Monitoring. Get paged when any Windows service stops — a SQL Server instance, a vendor agent, your own background worker — on any Windows server. Add the server, run the installer, and use Discover services to list what's actually installed on it rather than typing names in. No inbound firewall rules and no credentials: the Agent reports outbound and runs as LocalSystem. If a server already runs the JAMS Agent, there's nothing extra to install. See Windows Service Monitoring.
A silent server is no longer reported as healthy. Previously a powered-off machine showed every service as Running, because nothing had told us they'd stopped. Now an Agent that goes quiet raises its own alert saying exactly that, and its services show Unknown rather than a state we can't actually see. Service labels also name the machine they're on, so two servers running the same service stay distinguishable.
We now tell you when a monitor can page nobody. Monitoring switched on, services ticked, and no alert flow chosen — or the flow was later deleted, deactivated, or left with no reachable recipient. Any of those and the page says so, instead of looking healthy until an incident.
Migrating from PagerDuty. Bring across people, teams, schedules (both of PagerDuty's schedule types), rotations, escalation policies and overrides. You get a full report first — what would be created, the resulting coverage, and anything that can't be represented faithfully — and nothing is written until you press Import. Nobody is emailed: imported people are invited individually, from the Users page, when you're ready to cut over. See Migrating from PagerDuty.
JAMS service monitoring and queue depth. Watch the JAMS Executor, Scheduler and Server services, and get paged when one stops — with an Attempt to start button right on the alert and the dashboard. MSMQ queue depth is monitored too, with a threshold you set, sustained-breach detection so a brief spike doesn't page anyone, and a recovery notification when it clears. See JAMS Scheduler.
Per-user pricing, with SMS and voice metered separately. Plans are now priced per user, and seats are something you buy rather than a count of who happens to be in the account — so inviting or removing somebody never changes your bill. SMS and voice have their own allowances, which means running out of texts doesn't stop calls, and neither stops email, push, Teams or Slack. Top-ups are available for both. See Plans & Billing.
More than one person on call at once. A schedule can now be set so that every rotation covering a moment pages, simultaneously — for a deliberate handover overlap, or a shared pager — instead of the top rotation winning and the rest acting as fallbacks. Uncovered windows are also surfaced everywhere now: on the calendar, in the timeline, and on the dashboard. See Rotations and coverage and Coverage gaps.
Who's on call, on the dashboard. Today at a glance now lists who currently holds each schedule's pager, marks you if it's you, and names any schedule with nobody on call rather than hiding it in a count.
One alert, one row. The dashboard and history pages now collapse a multi-channel alert into a single expandable row, so an alert that went out by SMS, call and email reads as one event. History also gained an Ack Time column and collapsible filters.
AI Helper works with Anthropic too. Paste an Anthropic key instead of an OpenAI one and it's used automatically — the vendor is chosen from the key itself, with nothing to configure. See AI Helper.
Migrating from Opsgenie. A read-only check that reports exactly what would come across from your Opsgenie account. Worth running on its own — it finds problems in a current setup whether or not you migrate. Opsgenie closes on 5 April 2027. See Migrating from Opsgenie.
Clearer JAMS alerts and remediation. A failure alert now names the sequence or workflow the job belongs to, not just the job. Choosing Retry on a workflow tells the caller plainly that it starts a new job rather than resuming the old one, and cancelling a run no longer reports it as having finished successfully. JAMS's newer API is supported as well, with setup problems reported as something you can act on instead of a bare error.
Dashboard tidying. New cards for Windows Service Health and queue depth (with your alert threshold drawn on the graph), and the plan-usage meters are two lines each instead of five.
Trials are gentler. A trial is now metered per channel rather than ending the moment you hit a single cap, and an expired trial continues on Free instead of locking you out. The billing page shows trial status with days remaining, and there's an Enterprise option on it.
Privacy and security. Marketing analytics no longer run anywhere inside the signed-in app — only on public marketing and sign-up pages, with sign-in and other forms explicitly excluded. You can also anonymise one person's personal details in the audit trail on request, keeping the trail itself intact. And we fixed a flaw in how a caller's IP address was determined, which had made login rate-limiting bypassable and audit-trail IPs forgeable.
AI Helper answers read properly again. Answers grounded in this Help Center had been losing their numbered lists, and long articles were being cut short before the model saw them. Both fixed, so answers are better and formatted the way they were written.
⚡ A faster flow builder + JAMS multi-environment routing
Updated — July 24, 2026
Pick your source first. Creating a flow from New Alert Flow now starts with choosing what to monitor, then shows just the settings for that source — name, description, custom alert message, and configuration together in one step. Fewer clicks, less back-and-forth.
JAMS Scheduler and Azure Monitor are right in the flow builder. If your plan includes them, they show up as choices under New Alert Flow and take you straight to setup. After you save, a View Flows button drops you on your flow list.
Manage integration flows from the Flows list. JAMS and Azure Monitor flows now have Edit (which opens their setup form) and Delete right alongside your other flows.
JAMS: one alert path per environment. Running JAMS in more than one place (say Prod and Dev)? Install a connector in each, then bind a flow to the environment it belongs to — so a restart, continue, cancel, or acknowledge only ever runs against the right server. See JAMS Scheduler.
Clearer save confirmations. Saving now shows a brief on-screen confirmation, so you always know it worked.
🚀 Welcome to JAMS Incident Management
Launched — July 9, 2026
JAMS Incident Management makes sure the right person hears about the alert that matters — and can act on it from wherever they are. Here's what the platform can do:
Alerts on every channel Reach your team by SMS, phone call, email, push notification, Microsoft Teams, and Slack — choose the channels each person prefers, per alert.
Never miss a critical alert Sequential escalation, on-call rotations, and team groups automatically move an unacknowledged alert to the next responder until someone owns it.
Acknowledge and act from anywhere Reply to a text, tap an email or push notification, press a key or speak on a call, or click in Teams or Slack — no need to open the app. For JAMS Scheduler jobs, you can restart, continue, or cancel a failed job right from the alert.
Connect the tools you already use Two-way integrations with JAMS Scheduler, Azure Monitor, ServiceNow, and Zendesk — acknowledge or resolve here and the status syncs back to the source automatically.
Build alert flows in minutes A visual flow builder — or let the built-in AI Helper draft a flow for you from a plain-English description.
Some capabilities depend on your plan or add-ons — see Plans & Billing for what's included in yours.
Questions or ideas for what we should build next? We'd love to hear them. We're just getting started.