Reelease in seven short videos
Each one shows a part of the product on real screens. New to Reelease? Start with the first one.
Read the transcript
The safe way to put AI to work on critical systems and in regulated sectors.
Here, a mistake is a transfer that never goes out or a missed deadline.
Laura asks for what she needs and the agent proposes a plan.
Reelease checks the rules and the permissions…
…and signs the plan: if anyone alters it, it doesn’t run.
The lookups go ahead on their own.
The change waits for someone else: whoever starts the task can’t approve it.
María approves and the transfer goes out, on the same core as always.
Resolved within the shift, with nothing rewritten.
Every task leaves its run record: who asked, what was done and who approved it.
And you can stop an agent instantly.
On the systems you already run. No migration, no rewrite. And it keeps working when you replace them.
And how does the agent know what to do?
First, Reelease has read your system, exactly as it is.
It reads the code and the documentation and builds a map your team reviews.
And it leaves everything documented, with its sources, as PDF or Word.
Your team chooses which use cases each agent can execute.
Only what your team publishes can run. Everything else stays documented, for reference.
Every agent starts with no permissions: an admin turns on only what it needs.
Your AI, where you decide.
It runs where you decide, with the AI model you choose.
Your data is looked up, never copied. Nothing is used to train models.
For sectors that can’t improvise: the same control, with concrete cases in every sector.
Reelease, the control layer between AI and your systems.
AI for critical systems. Under control.
- From code to operatorWhat the admin does: create the agent, analyze the code after its pre-analysis, publish executable use cases, decide who approves, connect systems and invite an operator.
Read the transcript
You create an agent for your team in a system under your control.
You give it the code: a repository or a ZIP file.
In seconds, the pre-analysis recognizes your system and what the agent can do.
You see what it will read, what stays out and what to review first.
The analysis reads the code and turns it into knowledge.
And it checks the result against what you confirmed.
The summary shows what it understood about your system, with the evidence.
Use cases, rules, screens and connections, all in one catalog.
You review each executable use case: its steps, its data and its status.
Once it has everything it needs, you publish it. Only what’s published runs.
You choose what the agent can do and what waits for approval.
And in the system rules you decide who approves: someone else, not whoever launched the task.
You connect your systems and the operator’s computer, with the Reelease Agent.
You invite an operator: they only see the chat and the agents you choose.
They get the invitation and start working with the agent.
From your systems to an agent under control, ready for your team.
- AI-generated documentationAI documentation from your code: pick a template, tune the outline and Reelease drafts each section with its sources in the code, ready to export to PDF or Word.
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.
- The operator chatWhat the operator does: choose an agent, ask and get an answer with its source, launch a task with its signed plan and get the result once someone else approves the change.
Read the transcript
Laura opens the chat and sees only the agents her team gave her.
Her home page has the templates her team left ready.
In Ask mode, the agent answers from what it knows about your system, without running anything.
And it cites its source: the rule in the core, with the program and the lines it comes from.
To get work done, Laura picks a template and fills in the detail it asks for.
Before it starts she sees the signed plan and which step waits for a person.
The task starts on her computer, through the Reelease Agent.
The step that changes data stops and waits for approval.
María sees it in her actions inbox, with the task’s data, and approves it.
The task finishes and the result comes back to Laura’s chat.
Your team works with the agent. You decide what gets approved.
- 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.
- The use case in actionA published executable use case from start to finish: the signed plan, the reads, the change someone else approves and the run record, with fingerprints of the plan and the change’s values.
Read the transcript
Laura looks for the template she needs: resolve a held transfer.
She adds the transfer ID and the agent prepares the plan before touching anything.
The signed plan reads the transfer and its hold, and leaves the retry for last.
The reads go ahead on their own. The retry changes data and waits for someone else.
Laura can’t approve her own task: she can only reject it.
María sees the change with its data and approves it, with a reason that stays on record.
The reads and the change finish, and Laura gets the result in her chat.
The admin opens the run record: who launched it, who approved it and why.
With the plan, the steps and every decision. And you can download it.
And in technical verification, fingerprints of the approved plan and the change’s exact values.
Every task, done to its plan, with its run record.
- The same control in every sectorEvery sector, with its own systems and cases: in all of them, the signed plan, the change someone else approves and the run record.
Read the transcript
Banking, insurance, healthcare, energy, industry, defense, justice and public sector: one control.
In banking, the signed plan reviews the held transfer and leaves the retry to someone else.
In insurance, it handles a home claim: notice, cover and settlement. The payment waits.
In healthcare, it prepares the referral and finds a slot. Sending and booking it waits.
In energy, it checks an abnormal reading against past usage and the bill. The correction waits.
In industry, it matches order, delivery note and receipt. Releasing the order waits.
In defense, it spots stock that won’t reach the minimum. Requesting more waits too.
In justice, it checks each party’s signature and channel. Sending the notification waits.
At a town council, it validates a change of address against the register. Recording it waits.
Whoever launches a task can’t approve it. María sees in Actions what’s waiting from every sector.
She approves with a reason, and the task finishes in Laura’s chat.
The run record keeps the plan, every step and who decided what, the same in every sector.
Every sector. One control.
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.