The four verticals Progull is being built for.
Progull is pre-revenue and does not yet have production customers. These are the regulated batch estates the platform is designed to serve once the build cycle and design-partner pilots complete.
No production deployments yet — by design.
The first target customer is Month 18, following a 12-month development cycle and a 6-month design-partner pilot phase. Until then, everything runs against a controlled Hercules emulator with synthetic SMF, JES and CICS corpora.
Banking & Capital Markets
Overnight settlement, core banking and payments batch — regulated, latency-sensitive and heavily instrumented. The canonical target for agentic abend management.
Insurance
Policy administration and claims adjudication run on long-tail COBOL and Db2 batch. Small MTTR gains translate directly into settlement SLAs.
Aviation
Passenger service systems and revenue accounting depend on nightly batch that cannot slip. The operational cost of a delayed dispatch job cascades into the day-of-operation.
Government
Tax, benefits and records systems run mission-critical z/OS batch under strict audit obligations. Every action needs an explainable, reviewable trail.
Synthetic corpora, Hercules emulator, sandbox environments.
Every abend pattern and reasoning trace shown elsewhere on the site is generated inside a controlled test harness. No real customer telemetry is involved because there are no live customers yet.
Hercules-based test harness
A sandboxed z/OS environment loaded with synthetic SMF records, JES2 spool output and CICS transaction logs derived from published reference material. Deterministic, repeatable, and safe to iterate against.