Progull is the agentic AI layer that detects, diagnoses, remediates and closes mainframe batch incidents end-to-end — natively wired into z/OS, CICS, DB2, JCL and ServiceNow.
Progull operates as a 24/7 mainframe SRE — across detection, reasoning, remediation and ticket lifecycle. Each surface is a dedicated capability.
An agentic loop that detects, reasons over and remediates batch abends — governed by policy and explainable end-to-end.
Explore the solutionTickets are created, enriched, worked and closed inside ServiceNow with a full audit trail of every agent action.
See the workflowNative ingestion of SDSF, SYSLOG, JES spool, CICS region state and DB2 diagnostics — not a screen-scraper.
Inspect telemetry92% of recurring abends auto-resolved, MTTR cut by 85%, and a knowledge base that finally compounds.
Read the impactLeast-privilege access, on-prem-friendly deployment and an answer to every question your CISO will ask.
Review securitySee Progull resolve a real abend — from JES spool to closed ServiceNow ticket — against your environment profile.
Request a demoSector-wise view of the operators trusting Progull with their nightly batch. Click any logo to read the engagement story.
Click a client to read the engagement story in our Newsroom.
Each tab streams a representative reasoning and remediation trace as Progull would handle it inside ServiceNow.
A representative S0C7 abend, handled end-to-end by Progull agents inside ServiceNow.
S0C7 surfaced in JOB PAYRUN02 within seconds of the JES spool event.
SYSOUT, SYSUDUMP, JCL and DB2 SQLCODE pulled from SDSF — no human in the loop.
Correlated to a recent COBOL packed-decimal change and upstream feed file.
Approved playbook re-submits STEP0040 with corrected parm; ServiceNow notified.
INC0098231 auto-resolved with the full reasoning trail attached.
No 3270 screen scrapers, no parallel ticketing — Progull fuses native mainframe telemetry into ServiceNow under your existing controls.
Drag the sliders to your environment. Numbers refresh in real time using Progull's measured baselines (92% auto-resolution, 85% MTTR reduction).
Indicative only. Excludes downstream SLA recovery, deferred change, and avoided escalation cost.
Start with an isolated sandbox to prove the model against your own abend corpus, then move to a usage-metered enterprise rollout once the playbooks are yours.
A pre-wired sandbox cloned to your runtime profile — JCL libraries, DB2 catalogs, abend corpus — so your team can stress-test Progull against representative batch loads in isolation.
For production rollouts spanning multiple LPARs, sites and ServiceNow scopes. Priced against measured outcomes — auto-resolved incidents, autonomous remediations, and operator hours reclaimed.
Pricing is indicative. Final terms reflect deployment topology, integration depth and audit scope.
"We took a 3 a.m. payroll abend and watched Progull close it in 4 minutes — with a worknote our auditor was happy to sign off. That is the bar."
"Every other vendor wanted to put a 3270 scraper in front of z/OS. Progull is the first team that actually understood SDSF, JES2 and surrogate IDs on day one."
"92% of recurring abends now auto-resolve. Our SMEs spend their time on the long tail and on writing playbooks — not chasing S0C7s at midnight."
See a live walkthrough of Progull resolving a real abend — from JES spool to closed ServiceNow ticket — against your environment profile.