What we stand for as an integration team

Heirapi was founded on a simple belief: legacy mainframes deserve better than being ripped out. Our principles shape how we design API bridges, talk to clients, and handle the messy parts of corporate integration.

Trusted by teams modernising mainframe estates

We work alongside Australian enterprises that run core operations on legacy systems. These are the organisations we partner with to design secure API bridges, translate protocols, and keep critical data flowing between old and new architectures.

Southern Cross Utilities

Billing and metering data on an IBM z/OS platform, connected to a modern customer portal through a custom API layer.

Harbour City Logistics

Freight tracking systems that needed real-time visibility across a legacy warehouse management backbone and cloud dashboards.

Meridian Health Network

Patient records stored on a decades-old clinical system, now exposed to secure internal applications via encrypted endpoints.

Outback Rail Group

Asset maintenance schedules running on a mainframe scheduler, integrated with field service tools for live updates.

Coastal Manufacturing Co.

Production line telemetry from legacy PLC controllers, bridged to an analytics platform for near-real-time reporting.

Westfield Insurance Brokers

Policy administration on an AS/400 system, linked to a modern claims workflow without disrupting daily operations.

People behind the bridge

Integration architect

Maxine McDermott

Twenty years inside mainframe environments, from CICS transaction routing to VSAM file layouts. Maxine maps the old system's constraints before a single line of API code is written, so the bridge fits the machine instead of fighting it.

Security lead

Daisha Fritsch

Daisha handles the hard part: keeping a mainframe session safe while it talks to modern services. She designs mutual TLS boundaries, credential vaulting for legacy logins, and audit trails that satisfy both the network team and the compliance officer.

Protocol specialist

Mallory Purdy II

Mallory translates between worlds that were never meant to meet. IBM MQ queues, TN3270 screens, COBOL copybooks, and REST payloads all pass through his hands. He writes the data mapping rules that turn cryptic byte streams into clean JSON.

Network engineer

Larry Lakin

Larry builds the actual conduit between corporate LANs and legacy racks. His work covers firewall segmentation, latency budgets, and failover paths, so the API bridge stays up when a switch blinks or a link drops during a batch window.

Delivery manager

Lee Fahey

Lee keeps the project honest. He schedules the cutover windows, coordinates with the mainframe ops crew, and makes sure every stakeholder signs off before production traffic flows. His job is to turn a technical design into a date on the calendar.

Who We Are at Heirapi

We are a team of integration engineers who build secure API bridges between modern corporate networks and legacy mainframe systems. Our work is for enterprises in Australia that run critical operations on older architectures but need them to talk to today's cloud services, data platforms, and business applications.

Heirapi started with a simple observation: many large organisations still depend on mainframe systems that were built decades ago. These systems process orders, manage inventory, and hold records that newer software cannot easily reach. The usual answer is to replace them, but that is expensive, risky, and often unnecessary. Instead of ripping out what works, we build custom API layers that sit between the old and the new. Our bridges translate protocols, map data structures, and enforce security rules so that modern applications can read from and write to legacy systems without compromising either side. We work with IT leaders, solution architects, and engineering teams who need a partner that understands both worlds. We speak COBOL and CICS as comfortably as REST and JSON. That dual fluency is what lets us deliver integrations that hold up in production, not just in a proof of concept. Our tone is direct and technical. We do not oversell or promise magic. We explain what a bridge can do, what it cannot, and what it will take to get there. Clients come back to us because we are honest about constraints and rigorous about the details that matter.

Principles That Guide Our Work

  • Security is designed in from the first diagram, not added as an afterthought.
  • We respect the legacy system's constraints and never force a square peg into a round hole.
  • Documentation is part of the deliverable, not an optional extra.
  • We test against real mainframe behaviour, not just simulated responses.
  • Clear communication with your team is as important as clean code.
  • We measure success by uptime and reliability, not by the number of endpoints we expose.

Cookie settings We use cookies to keep the site reliable, remember basic choices, and understand which pages are useful. You can accept, reject, or review the settings before continuing.