LeBrain
Home · Platform

6 modules, one platform.

The Hub sits between your users and your IT systems. ARIA and the Studio automate. Digital Solutions and Legacy transform your systems and make them more reliable. Governance oversees it all. Hover over a module to see what it does.

AUGMENTED AUTOMATIONUSER AND IT INTERACTIONSIT TRANSFORMATION GOVERNANCE · OVERSEE · MEASURE · STEER DOCUMENTS TRANSFORMS DRAWS ON INTERACTS RELIES ON AUTOMATES INVOKES BUILDS ON RELY ON ARIAgenerates automations from the PDD The Studiobuilds automations The Hubconnects users and agents to IT Digital Solutionsbuilds business applications Legacyrebuilds knowledge of existing systems IT systemsapps · databases · screens · files

Legacy recovers the knowledge of an existing application from its code and data.Digital Solutions turns a specification into a business application, deployed and documented.The Hub turns a natural-language request into actions on your IT systems.The Studio builds reliable automations that call on Hub agents when something needs interpreting.ARIA generates end-to-end automation from the process definition document.Governance oversees every module, measures the value created and tracks model consumption.Platform 6 modules, one platform, under a single governance layer.

Each module has its place, and they all speak the same language.

Augmented automation

ARIA and the Studio

The Studio builds automations. ARIA relies on it to generate a complete process from the process definition document.

The StudioARIA
User and IT interactions

The Hub

The single entry point: a natural-language request, from any channel, becomes an action on your systems, executed and logged.

The Hub
IT transformation

Digital Solutions and Legacy

Legacy recovers the knowledge locked in existing applications. Digital Solutions migrates or builds the business applications you're missing.

Digital SolutionsLegacy
Above it all
Governance oversees, measures and steers.

It sees the usage and runs of every module, tracks model consumption and consolidates the value created. Governance

The principle shared by all 6 modules: AI proposes, clear governance decides

Every operation takes the most direct path.

6 questions, asked in order. The first yes sets the access mode. Nothing in your systems gets rewritten: we use what they already expose, and the Studio covers the rest.

  • 4 direct modes, handled by the Hub: API, database, MCP server, files.
  • 2 modes through the Studio, when your systems expose nothing: cloud workflow and bot.
  • Each mode becomes a capability that every agent can reuse.

The Hub and the Studio in detail

  1. 1Is the operation exposed through an API?OpenAPI contractREST API · Hub
  2. 2Can the data be reached in a database?predefined SQL queriesDatabase · Hub
  3. 3Does the application already have an MCP server?a standard connector that exposes its functions to AI agentsMCP server · Hub
  4. 4Does the data come as a file?JSON, CSV, ExcelResource · Hub
  5. 5Does the operation span several cloud applications?cloud automation, iPaaSWorkflow · Studio
  6. 6Can the operation only be done on screen?RPA botAutomation · Studio

We check in this order: the first yes sets the access mode. Workflows and automations run through the Studio: the agent gains the capability, and execution stays under control.

Open your systems to AI without giving up control.

Reading through the screen, reading from the database, writing to the database: each type of access carries its own level of risk and its own guardrails. LeBrain applies them all the same way, through the Hub, and keeps a record.

Access 1 · Studio bot

Read through the screen.

The bot sees what a user sees, with that user's permissions. The application's controls stay active.

Low risk

Dedicated bot account, action log

Access 2 · database connector

Read from the database.

Data is read outside the application's controls, and a heavy query can slow down production.

Moderate risk

Read-only, predefined queries, anonymization before the model

Access 3 · agent or connector

Write to the database.

The application's business rules are bypassed; one error could change a record with no check.

High risk

Approval before write, full log, rollback

The 5-guardrail chain

  1. Hub agentreads or writes
  2. Least privilegeapplied
  3. Predefined queriesapplied
  4. Anonymizationapplied
  5. Approval before writenot required for readsrequired for writes
  6. Audit log and rollbackapplied
  7. Your databasebusiness data

Read: 4 guardrails. Write: all 5. Illustrative diagram

  1. 1 · LEAST PRIVILEGEA dedicated service account, read-only by default; writes are limited to authorized tables.
  2. 2 · PREDEFINED QUERIESSkills run parameterized, validated queries, never free-form SQL written by a model.
  3. 3 · ANONYMIZATIONSensitive data is masked before any call to a model.
  4. 4 · APPROVAL BEFORE WRITERule-based checks and human approval come before any change to a record.
  5. 5 · AUDIT LOG AND ROLLBACKEvery read and every write is logged, replayable and reversible.

See the full Security page

Independent layers, managed consistently.

From your IT systems up to the models, each layer evolves without touching the others: a new model, a new agent or a new connection to your systems is added under the same governance.

Modelsyour choice, no lock-in LLM SLM OCR & vision Other models AI gatewayone entry point to models Single model access, per-team quotas, routing, call logs. The Hubagents, skills Extraction Anonymization Decision Tracking Capabilitiesused by skills MCP Database API Automation Resource The Studiogoverned execution RPA bot Workflow DB connector Hub connector Your systemsas they are today Applications, databases, screens, files. GOVERNANCE Consumptioncost per case, per agent Usageagents, users, volumes Audit trailevery call logged Accesswho can use which model Compliancesensitive data protected

Your systems We start from your systems as they are: nothing needs rewriting to get started. The Studio Bots, workflows and connectors carry out the actions on your systems, and call on Hub agents when something needs interpreting. Capabilities Each way of accessing your systems becomes a capability that agents can reuse. The Hub Agents combine skills; a skill written once serves every use case that follows. AI gateway A single access point to the models: quotas, routing and a log of every call. Models LLMs, SLMs or OCR: you choose, and you can switch without rebuilding everything. Governance Spans every layer: consumption, usage, audit trail, access rights and compliance.

What you build once serves every use case that follows.

Studio
2 ways to act on your applications

The Studio works through the screen, the way a user would, or directly through the database. The automations you already run don't need to be rebuilt.

Hub
Reusable agents and skills

A skill written for one use case carries over to the next, with no need to start over.

AI gateway
Your choice of model

LLMs, SLMs or OCR plugged into a single gateway, with no vendor lock-in.

Governance
Protected data

Sensitive data is anonymized before any model call, and database accounts run on least privilege.

Governance
Cost and usage tracked

Consumption by case, by agent and by model, with per-team quotas.

Governance
Controlled writes

Approval before any change to your data, and rollback if needed.

Our method: Scope, Pilot, Scale.

An iterative approach that builds step by step and proves its relevance and value at each stage. One use case, chosen for its value, goes into production and gets measured; the access, agents and rules it sets up then serve every new use case.

01

Scope

A workshop with your business and IT teams: the use case, the data involved, access to your systems, security constraints and success criteria. The scope and our commitment are agreed at the end of this phase.

02

Pilot

The first use case is built and deployed to production, with regular demos. From day one, the Governance module measures its usage, cost and value.

03

Scale

Each new use case plugs into the foundation already in place: the same access to your systems, the same skills, the same gateway, the same rules. It costs less than the one before.

What you can expect from us, on every project.

  • A clear commitment after scoping. Scope, cost and timeline are agreed up front.
  • You watch the solution take shape. Regular demos, in your environment: no surprises at the end.
  • You decide at every step. Each milestone needs your approval before the next phase starts.
  • Everything we deliver works, and it's yours. Code, documentation and deployment scripts are handed over to you. No lock-in.
  • Your teams are trained. Knowledge transfer is part of the project, not an add-on.
  • Value is measured. Usage, cost and gains are tracked in Governance, not estimated after the fact.

Our business model follows the value each module delivers.

Projects are billed per engagement, usage by subscription, and bots per license. You always know what triggers a cost.

Projects
Per activation day

Legacy and Digital Solutions: scope estimated before kickoff, go-live included.

Usage
By subscription

The Hub: based on the number of users, connections to your systems and agents.

Bots
By license

The Studio: per bot in production, support included.

Platforms
Access, then usage

ARIA and Governance: an access fee, then a usage component tied to the processes and bots monitored.

Before you start.

Do we need to modernize our IT systems first?

No. LeBrain starts from your systems as they are: it uses what they expose, and the Studio steps in wherever the screen is the only way in.

Which module should we start with?

Start with the use case, not the module. Scoping finds the shortest path; it often runs through the Hub and the Studio, or through Digital Solutions when an application is missing.

How long does scoping take?

A few workshops. The goal is to reach a clear commitment on a first use case, quickly.

Can our teams take over?

Yes. Everything we deliver is documented and belongs to you; training your teams is part of the project.

Let's see where LeBrain can create value in your organization.

A 30-minute intro call to talk about your needs.

Book a meeting See use cases