Skip to content

What your system knows, with the lines of code that say so

Reelease reads your systems’ code and documentation, from the mainframe to your APIs, and builds a map your team reviews. From it come the use cases you can turn into tasks for your agents, and the knowledge now held only by the people who’ve run the system for decades gets documented, with its sources.

We email you the link to open on your computer.
Read the transcript

Your agent already knows your system. It uses that knowledge to write your documentation.

With “Create with AI” you pick a template: architecture, functional, user manual or executive summary.

Each template brings its outline. You remove the sections you don’t need…

…and tell the AI what each section must cover.

Reelease drafts section by section from what your agent knows, and you follow it live.

When it’s done, the document is saved in your agent’s library.

Every statement cites its source: the file and the code lines behind it.

Each section also shows its quality and how many of its citations are verified.

Export it to PDF or Word, including with your company’s own Word template.

And you decide whether operators see it: the agent uses it as a source in the chat.

Your documentation, written from your code, with its sources.

From code to a map of your system

In seconds, the pre-analysis recognizes what kind of system it is, tells you what you'll be able to do with it, and what's left out and why. Watch it with Bank of Z, IBM's sample banking application in COBOL, CICS, PL/I and Java, whose code is public.

01Before the analysis: the pre-analysis

Your system

You know what your system is and what the agent can do before anything is analyzed.

github.com/IBM/Bank-of-Z · a6fe76f

Mainframe monolith with web, API facade, in 9 parts

88% of the files: 306 files in 6 parts.

What the agent will be able to do

Operable

Every data-changing operation in the selected scope becomes a use case the agent can run.

What gets read

Read with AI

7 of 9 parts · 308 of 485 files

Size

308 files

  • Limit per analysis: 50,000 files
  • Estimated time: Medium

A ZIP of up to 100 MB on Free, 1 GB on Pilot and 10 GB on Pro and Enterprise.

Analysis profile

Recommended

  • To operate and renew (full)

On a large system, start with a pilot or read the structure of the whole estate at once.

Technologies

It identifies the technology of each part.

  • COBOL
  • Java / Kotlin
  • SPA + API client
  • Quarkus / JAX-RS

Reliable detection

From the mainframe and IBM i to .NET Framework, Python or React, read from the code itself

Left out of the analysis

2 parts with 40 files left out.

  • 2 test, example or documentation files

Every sync grows the map, and “Expand knowledge” adds what was left out

To review

It flags what's worth checking before you analyze.

  • Check what gets analyzed before you continue.
  • Web application: 20 files left out by default. Web channel over the mainframe: it would duplicate use cases with the CICS screens.

02After: what it understood, with the lines that say so

308 of 485 files read · 43 COBOL programs · 9 CICS transactions

Pick a rule, a screen, a table or a program.

Business rule

Distinct accounts

Transferring funds to the same combination of sort code and account number is not allowed; the operation ends with abend SAME and a diagnostic in ABNDPROC.

Source code: src/base/cics/cobol/XFRFUN.cblView on GitHub

Lines 313–317 of this file, as the analysis checked them.

* Are we trying to transfer from and to the same account?
* We don't allow that.
*
IF COMM-FACCNO = COMM-TACCNO
AND COMM-FSCODE = COMM-TSCODE

Reelease doesn't store your source code: you only see the cited lines here.

Try it with an agent in the banking space

Bank of Z is a public IBM sample application under the Apache 2.0 license. The rules, the screen, the table and the programs come from Reelease's analysis, and the lines from commit a6fe76f.

Every analysis, with its report

Before you build on it, you know what was understood and how well. When it finishes, you see whether what was read matches the forecast.

Quality report

What was imported and validated, how each stage went, any warnings and the highest quality your plan allows. Every time you expand the knowledge, too.

Security checks

Six code checks on every sync: exposed passwords, open permissions, unprotected CICS, unvalidated certificates, personal data on screen and unprotected APIs.

Your system’s technologies on one map

Bring your system as it is, whatever its technology: Reelease reads it into a single map. Look yours up.

Try:

43 systems and tools

  • An agent can act on it
  • It understands and documents it

IBM Z mainframe

z/OSCOBOL, CICS, JCL and 6 more

Reads.cbl .cob .cpy .copy .pco .bms .csd .jcl .proc .prc .pli .pl1 +3

Acts throughCore transactionWeb API

Oracle

PL/SQL, Forms and ReportsPL/SQL, PL/SQL web, Oracle Forms and 2 more

Reads.pkb .pks .sql .pls .psp .fmb .olb .pll .mmb .rdf .pc .pcc

Acts throughDatabase, through the Client BridgeWeb API

IBM i

AS/400 · iSeriesRPG and RPGLE, CL, DDS

Reads.rpgle .sqlrpgle .rpg .clle .clp .pf .lf .dspf .prtf

Acts throughWeb API

Natural and Adabas

Software AGNatural, Adabas

Reads.nsp .nsn .nsm .nsl

Acts throughWeb API

Desktop applications

Client-serverPowerBuilder, Delphi, Visual Basic 6

Reads.pbl .srw .srd .dfm .pas .dpr .frm .bas .cls .vbp

Acts throughDatabase, through the Client BridgeOperator's computer

.NET Framework

Web Forms, WCF and ASMXASP.NET Web Forms, WCF and ASMX services

Reads.aspx .ascx .master .svc .asmx

Acts throughWeb API

Java and the JVM

Spring, Quarkus and JAX-RSSpring, Quarkus and JAX-RS

Reads.java .kt

Acts throughWeb API

Web, scripts and APIs

From the contract to the screenOpenAPI and Swagger, NestJS, Python and 3 more

Reads.yaml .json .ts .py .rb .erb .graphql .gql .tsx .vue .svelte

Acts throughWeb API

Databases

In your networkSQL Server, Oracle Database, PostgreSQL and 1 more
Acts throughDatabase, through the Client Bridge

Business tools

Email, tickets and codeMicrosoft 365, Gmail, Jira and Confluence and 4 more
WithEach operator's work accountOrganization app

Trademarks and logos belong to their respective owners. They are shown to identify integrations and do not imply affiliation or endorsement.

A catalog your team reviews

Use cases, screens, connections, business rules and domains stay as suggestions until your team reviews them. The use cases you publish become executable for your agents; the rest stay as documentation use cases, for reference.

  • Use cases with their steps, their data and what they need to run
  • Agents only work with what is published
  • The same catalog powers chat answers and documents
  • Your own use cases too: you describe them, AI drafts them and your team reviews them, with validated fields
A custom use caseA custom executable use case: describe it in your words, AI prepares the draft from what your agent knows, you choose who approves, publish it and test the target system.
Read the transcript

A custom use case starts with your words: you describe what the agent should do.

Here, resolve a held transfer and tell the customer, with a person who approves.

AI prepares the draft from what your agent already knows about your system.

Each step comes with its type: core transactions, an AI step, an approval and the email.

Your team reviews and adjusts it before saving.

Once saved, the platform checks what’s missing, such as who approves each change.

From the flow, you choose who approves that step: here María, who isn’t the one launching the task.

Now it has an approver. You publish it, and it asks you to test the target system.

One click to test it: it responds, and the use case is ready to run.

Your use cases, in your words and under your rules.

Documentation sourced from your code

Pick a template, adjust the outline and Reelease drafts every section with its sources. What it documents (screens, business rules, flows) is the basis for rebuilding each piece on a new system when you decide to replace one.

  • Architecture

    Context, components, data, integrations and decisions, with C4 diagrams.

    10 sections

  • Functional specification

    Actors, use cases, business rules and flows: the foundation for building your new system.

    10 sections

  • User manual

    Every screen with its mockup, user flows, common tasks and roles.

    8 sections

  • Executive summary

    Scope, business capabilities, main use cases and how well the system is understood.

    9 sections

  • System README

    What it is, how to start it, its modules and APIs, configuration and operations.

    10 sections

  • Your own templates

    Start from scratch or save your outline as a template to reuse it.

    Up to 40 sections

  • An outline that fits you

    Edit, reorder or add sections, with instructions for the AI in each one.

  • Sourced and reviewed

    Every section cites where it comes from and, before publishing, flags what is verified, inferred or missing.

  • Diagrams and screens

    Tables, diagrams (flow, sequence, data and C4) and every screen with its mockup.

  • PDF or Word, in your format

    With standard styles or your company’s own Word template.

Ask and write from the chat

Operators query what the agent knows and write documents with it without leaving the conversation. While they only ask, nothing on your systems is touched.

  • Answers with their sources, plus a warning if one comes from documentation not checked against the code
  • The draft is written in a side panel; ask to change one section and only that one changes
  • Your team decides which documents operators can see

Frequently asked questions

Which systems does it understand?

Mainframe: COBOL and CICS, JCL, PL/I with its SQL and CICS, IMS, MQ, VSAM, DB2 and z/OS Connect. IBM i (AS/400): RPG, CL and DDS. Natural and Adabas. PL/SQL, Oracle Forms and Oracle Reports, with their libraries, menus and the navigation between forms, and SQL embedded in C and COBOL (Pro*C and Pro*COBOL). Classic .NET (WebForms, WCF and ASMX) and desktop applications in PowerBuilder, Delphi or VB6. Java, Python, Ruby, Node, OpenAPI and React; COBOL programs that run as stored procedures on SQL Server; and SQL Server, Oracle or PostgreSQL through the Client Bridge. Of everything Reelease understands, agents only do what you publish.

Is the map a documentation dump?

No. You upload the code with a purpose (operate, replace or both) and your team reviews the result: screens, rules, connections and use cases. Dependencies between programs, transactions and data come from the code itself, each with its file, and you can find any piece by its file and line. Agents work from what has been reviewed, with someone accountable behind it.

Which documents can we create?

Architecture with C4 diagrams, a functional specification, a user manual with every screen, an executive summary, a system README or a free-form document. You can adjust the outline, give instructions per section and save your own templates.

Does it help when we replace a system?

Yes. The functional specification and business rules Reelease extracts from your code are the starting point for building the new system. Meanwhile, agents keep working on the one you already have.

Where does a document’s content come from?

From what the agent knows: the catalog your team reviews (use cases, screens, connections, rules, domains and architecture) and the documents in its library. Every section cites its sources and shows its quality before you publish.

Which formats do we get?

PDF and Word, including your company’s own Word template. Diagrams come out fully drawn.

Who sees each document?

Documents live in the agent’s library and your team decides which ones operators see. What an operator writes in the chat is saved to their own documents.

Does documenting or asking change anything on our systems?

No. Writing and asking don’t run anything. Changing something in a system is a different action: it follows the agent’s rules and, by default, a person approves every step that changes data.

See it on your own system

We’ll show you Reelease on one of your cases: what it understands, the plan an agent would propose and what you’d sign off on.

You choose the cookies

We use technical storage to remember your choice and, only if you accept, analytics cookies (Google Analytics) to understand how the site is used. You can change your choice at any time. Learn more in our cookie policy.