Zero-touch abend managementfor mainframe batch.
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.
- 92%
- Auto-resolved abends
- <3m
- Mean time to recovery
- 24/7
- Hands-off operations
One agentic loop, from abend to closure.
Progull operates as a 24/7 mainframe SRE — across detection, reasoning, remediation and ticket lifecycle. Each surface is a dedicated capability.
The Solution
An agentic loop that detects, reasons over and remediates batch abends — governed by policy and explainable end-to-end.
Explore the solutionServiceNow Workflow
Tickets are created, enriched, worked and closed inside ServiceNow with a full audit trail of every agent action.
See the workflowMainframe Telemetry
Native ingestion of SDSF, SYSLOG, JES spool, CICS region state and DB2 diagnostics — not a screen-scraper.
Inspect telemetryOperational Impact
Design goal: auto-resolve the long-tail of recurring abends and compound a playbook library that outlives any individual SME. Numbers below are targets, not measured deployments.
See the design goalsSecurity & Governance
Least-privilege access, on-prem-friendly deployment and an answer to every question your CISO will ask.
Review securityRequest a Demo
See Progull resolve a real abend — from JES spool to closed ServiceNow ticket — against your environment profile.
Request a demoThe verticals we're building for.
Progull is pre-revenue and has no production customers yet. The logos below represent the regulated batch estates the platform is designed to serve once the build cycle and design-partner pilots complete.
Logos are trademarks of their respective owners; shown for illustrative purposes. Click any client to read the engagement story.
* Illustrative only. Company names and logos are the trademarks of their respective owners and are shown to describe the industries and workload patterns Progull is being built for. Their inclusion does not imply endorsement, partnership, or a commercial relationship with Progull.
See the target-industry rosterPick an abend. Watch Progull resolve it.
Each tab streams a representative reasoning and remediation trace as Progull would handle it inside ServiceNow.
What used to take hours, closed in minutes.
A representative S0C7 abend, handled end-to-end by Progull agents inside ServiceNow.
- 00:001
Abend detected
S0C7 surfaced in JOB PAYRUN02 within seconds of the JES spool event.
- 00:152
Telemetry ingested
SYSOUT, SYSUDUMP, JCL and DB2 SQLCODE pulled from SDSF — no human in the loop.
- 00:423
Root cause reasoned
Correlated to a recent COBOL packed-decimal change and upstream feed file.
- 01:304
Remediation executed
Approved playbook re-submits STEP0040 with corrected parm; ServiceNow notified.
- 02:145
Incident closed
INC0098231 auto-resolved with the full reasoning trail attached.
One ingestion plane. One reasoning plane. One ticketing plane.
No 3270 screen scrapers, no parallel ticketing — Progull fuses native mainframe telemetry into ServiceNow under your existing controls.
Hover a node · click to pin
- SYSLOG events
- SDSF SYSOUT
- SYSUDUMP
- DB2 SQLCODE
- JCL deltas
The same incident. Two operating models.
What does an abend cost you today?
Drag the sliders to your environment. Numbers refresh in real time using Progull's design-goal assumptions (92% auto-resolution, 85% MTTR reduction). These are targets the platform is being built for — not measured deployment results.
Indicative only. Excludes downstream SLA recovery, deferred change, and avoided escalation cost.
No commercial price yet — by design.
Progull is pre-revenue. The only engagement available today is a design-partner slot at no charge. Commercial pricing publishes after the first pilots close.
Design-Partner Pilot
While Progull is being built, we onboard a small design-partner cohort at no fee. Pilots run in Advisory mode against a scoped, non-production subset of your batch fleet.
- Bounded, non-production or shadow-mode integration
- Weekly build increments on a shared agenda
- Named engineer on the Progull side
- Advisory tier only — no autonomous z/OS actions
- Anonymized learnings roll into the shared playbook library
- No obligation to a paid contract at pilot end
Commercial Plan
Commercial pricing is deliberately unpublished. It will be set against real deployment evidence from the design-partner cohort — not a guess made in advance.
- Priced against measured outcomes, not seat counts
- Tiered Autonomy — Advisory, Approval, Autonomous
- On-prem, BYOC or managed-tenant deployments
- Custom integrations (ServiceNow, SIEM, IdP, paging)
- Governance workflow co-authored with your change board
- Terms will publish once pilots complete
Progull is a pre-seed company. Engagements today are limited to the design-partner cohort described above.
The State of Mainframe Operations.
41 operations leaders. 90 days of normalized telemetry. The numbers behind on-call load, autonomy adoption, and where LLM pilots are still falling short.
Bring zero-touch operationsto your mainframe batch.
See a live walkthrough of Progull resolving a real abend — from JES spool to closed ServiceNow ticket — against your environment profile.