Gluecode
This sheet summarizes value, pricing and use cases. From here you can move to the dedicated areas or to the client portal for the next action.
Modernize legacy IBM i (AS/400) and z/OS systems by exposing RPG and COBOL programs as modern REST APIs — without rewriting existing code, with automatic code conversion via local AI.
What it solves
- Legacy data isolated, accessible only from 5250/3270 terminals
- Impossible to integrate IBM i and mainframe with web, mobile, and cloud
- Rewriting COBOL/RPG costs 500k-5M EUR with enormous project risks
- Le competenze RPG/COBOL stanno andando in pensione
What it does
Gluecode is a multi-runtime platform for modernizing and integrating legacy enterprise systems. It does two complementary things: converts legacy sources to modern stacks through an AI-assisted governed workflow, and exposes IBM i and z/OS legacy programs as REST JSON APIs without having to rewrite everything immediately. The Avalonia Dashboard and the official CLI gluecode constitute the single control plane for conversion, analysis, benchmarking, reporting, and operational readiness.
| Area | What it offers |
|---|---|
| Code Conversion | COBOL, RPG, PL/I, CL, REXX and legacy SQL to Java, C#, Node.js, Python, TypeScript, ILE RPG Free and target COBOL (AIX, Micro Focus) |
| IBM i Integration | Exposure of program and service program ILE (RPG/COBOL) via XMLSERVICE, stored procedure and direct call, with DB2 for i and QSYS2 services |
| z/OS Integration | Connectivity CICS, BATCH, DB2, IMS via FTP, z/OS Connect EE, IBM MQ and CICS Web Services |
| Analysis and parity | Pre-conversion risk and complexity analysis, dependency map, source vs target parity and post-conversion confidence score |
| Governance | RBAC, audit trail, quality gate, Go-Live Readiness badge and readiness pack |
| AI Engines | Configurable LLM without code changes: Ollama (local), OpenAI, Azure OpenAI |
Key Features
- Multi-language batch conversion with preview dry-run, quality score and migration notes.
- Runtime probing to deduce the signature of legacy programs lacking sources or documentation.
- Flow Studio: dependency maps (call, copybook, file) with graph rendering and architecture generation.
- Automatic extraction of business rules and pseudo-code from legacy sources.
- Parity Assurance and Confidence Report to validate equivalence between source code and converted code.
- Quality gate and Go-Live Readiness (Pass/Warn) tied to release criteria.
- Export Readiness Pack and multi-format reports for audit and release documentation.
- Real-time monitoring with WebSocket metrics and IBM i vs z/OS performance comparison.
- Enterprise security: JWT authentication, API key, resource-level authorization, RACF integration for z/OS.
- Billing and metering system with automatic tracking of API usage.
Architecture
The official runtime is based on C#/.NET 10 with ASP.NET Core and Entity Framework Core. The architecture is organized into bounded contexts: Gluecode.API handles REST, authentication, RBAC, workflows, and auditing; Gluecode.Worker runs asynchronous jobs (analysis, parity, confidence) with retry and persistence; the specialized analysis engine is invoked via CLI and its results are normalized into unified JSON contracts. The user control plane is the Avalonia Dashboard complemented by the CLI gluecode. Current persistence is on PostgreSQL; there are platform adapters for IBM i (ODBC, XMLSERVICE, DB2 for i) and z/OS (FTP, z/OS Connect, MQ). The API exposes automatic OpenAPI/Swagger documentation and is distributable via Docker or Windows installer.
Requirements
- Runtime platform: .NET SDK 10; operating system Windows x64 (native installer/executables) or containerized deployment via Docker.
- Database: PostgreSQL (application persistence); MySQL 8.0+ for the billing system; optional Redis for caching.
- IBM i (target): IBM i 7.3 or higher, PASE environment, DB2 for i, ILE COBOL and ILE RPG compilers, SSH access and 5250 emulator.
- z/OS (target): z/OS 2.3 or higher, Enterprise COBOL 6.3+ (for native JSON), optional DB2 for z/OS 12+, CICS TS 5.3+, z/OS Connect; TSO/ISPF access, FTP/SFTP, 3270 emulator.
- AI Engine (optional): configurable LLM provider between local Ollama, OpenAI or Azure OpenAI.
Compliance & regulations
Fatturazione elettronica italiana
Il modulo di billing genera fatture conformi al tracciato FatturaPA con gestione IVA, stati fattura e persistenza dedicata.
Reports & dossiers
- Readiness PackHTML + CSV + XLSX + JSON
Pacchetto di readiness esportabile dalla Dashboard, allegato al runbook di rilascio per validare il go-live.
- Conversion ReportHTML, PDF, CSV, XLSX, JSON
Report di esito conversione con quality score, livello e migration notes per ogni sorgente elaborato.
- Dependency MapJSON + Mermaid
Mappa delle dipendenze del programma (call, copybook, file) generata da Flow Studio per l'analisi architetturale.
- Benchmark ReportJSON + CSV
Riepiloghi di benchmark della conversione legacy per confronto e portfolio view.
- Audit / Governance ExportCSV + JSON
Export dei record di governance e audit trail per tracciabilita' e compliance tecnica.
- Billing ReportPDF + XLSX
Reportistica di fatturazione e revenue esportata dalla Dashboard.
Try it
Frequently asked questions
What does it expose exactly?
Legacy programs running on IBM i and z/OS, written in RPG and COBOL, made available as REST APIs. Gluecode does not rewrite or touch them: it sits in front of them, so the code that represents thirty years of corporate rules stays where it is and becomes callable by modern applications.
Che cosa succede quando una chiamata fallisce?
Finisce in una coda di rilancio invece di perdersi. Da lì si rilancia — subito, a orario programmato o in blocco — e si possono modificare i parametri prima di riprovare, che è quello che serve quando l'errore era nella richiesta e non nel sistema.
Is there sufficient traceability for an audit?
Each request and response is automatically logged with a complete trace that can be consulted. This is why Gluecode is used even where the requirement is not technical but one of compliance: to know who called what, when, and with what outcome.
Can the two platforms be compared?
Yes: the metrics arrive in real time and there is a side-by-side comparison between IBM i and z/OS, with the identification of slower endpoints and historical analysis. It serves to decide where to intervene, not just to know that something is slow.
Use cases
Banca: core banking su mainframe esposto via API
Integrazione dei programmi COBOL del core banking con i canali digitali senza toccare il codice legacy.
Manifatturiero: ERP AS/400 verso e-commerce
I programmi RPG dell'ERP esposti come REST API per alimentare e-commerce e applicazioni mobile.
