Book a Meeting →
European Manufacturing & Supply Chain Summit We exhibited at the European Manufacturing & Supply Chain Summit, Munich, November 2026
20agents5gates

Read first, rebuild second. A person at every gate.

Orlian reads the code, screens and database you already have, writes every rule down as a requirement, then rebuilds it with tests first. Twenty specialist agents do the routine work; a named person signs every hand-off.

Book a Meeting → Or see how Orlian builds, stage by stage.

ISO/IEC 27001:2022 · Databricks partner · Claude Partner Network · EU AI Act & NIST AI RMF aligned

how orlian works governed throughout
Analyze & PlanRead what you have. Every rule becomes a requirement.
Human gateSigned and timed.
Build Stage · VerifyTests first. Proven, requirement by requirement.
Release & OperateA way back. Read-only in production.

7 stages, 5 human gates. Every action logged.

European Manufacturing & Supply Chain Summit We exhibited at the European Manufacturing & Supply Chain Summit, Munich, November 2026

Up to 90% less project cost*, from requirement to production.

Orlian, our AI SDLC platform. Specialist AI agents carry a software project from the first requirement to production. A named person approves every hand-off, and one ID traces each change back to the goal it serves. Come and see it run on a real project at the booth.

Book a Meeting → Or name one system and we'll tell you whether to keep, connect or replace it.
From requirement to production A person at every gate Your servers, your AI model

*Up to 90%: tested and verified on real, independent application development. Results depend on the project's scope, codebase and starting point.

where to find us both days
16 Booth
Event
European Manufacturing & Supply Chain Summit
Venue
Holiday Inn Munich City CentreHochstraße 3, 81669 Munich
Dates
Nov 3 & 4, 2026
Also
Tuesday evening reception, we'll be there
Who's on the standwho you'll meet → VR VenkatCo-founder & CEO PV PrasobhCo-founder & CTO MN MarceloSubject-matter expert KH KaiSubject-matter expert
We're speaking · EMS Summit 2026 We spoke at the European Manufacturing & Supply Chain Summit, Munich, November 2026

Do your systems own you, or do your processes own your systems?

The sessionPut the process back in charge, without ripping out your systems.

Marcelo Navarro Marcelo Navarro Subject-matter expert 25+ years in international manufacturing across CNH, ZF, PepsiCo and Jaguar Land Rover, on the side of the table that signs off the spend.

Wed 4 Nov · 12:50–13:20 · Room 1

Marcelo on why the licence isn't the real lock-in, and how to screen every platform as keep, connect or replace before your next renewal.

Book a Meeting → Bring one platform to booth 16

Can't make the session? Find us at booth 16 on both days.

The session30 min
12:50 → 13:20
Wed 4 Nov · CET
WhereRoom 1Holiday Inn Munich City Centre
What you'll take away Why the licence is the visible cost, and not knowing your own rules is the real lock-in A simple screen for every platform: keep, connect or replace Three questions to ask before your next platform decision
European Manufacturing & Supply Chain SummitStage programme
Day 2
The argument, in three beats

The licence isn't the lock-in. Not knowing your own rules is.

Most manufacturers have renewed a platform because leaving felt riskier than paying. Three things keep a system in charge of the process, and none of them is the licence.

Knowledge

Nobody can say what the system really does.

A decade of rules, exceptions and workarounds that nobody wrote down. Orlian reads the code, screens and database first, writes every rule down and flags what it can't verify.

Dependency

Everything downstream reads from it.

Reports, ERP, planning and pipelines. A rebuild has to serve every one of them exactly the same, or it creates a second truth. Orlian proves each rule, requirement by requirement, before cutover.

Rebuild cost

Rebuilding by hand used to cost more than years of licence.

So the renewal was signed again. Orlian takes up to 90% off the project cost, with a named person signing every gate, which is what finally makes the exit case add up.

Read what you have. Prove every rule. Replace only what earns it.

How Orlian works

Seven wings, one red thread, a person at every gate.

Seven wings of specialist AI agents carry your project from the first requirement to production, and keep watching it after. A person approves every hand-off, and one ID ties every change back to the goal it serves, so the savings never cost you control.

up to90%*less effort and cost
20specialist agents in 7 wings
5human gates, each signed and timed
Governedend to end, every action logged

Where a person signs

  1. 1
    Analyze→Plan

    Your team confirms it matches reality

  2. 2
    Plan→Build

    You approve the requirements

  3. 3
    Build→Stage

    An engineer approves every change that matters

  4. 4
    Stage→Verify

    Readiness: live, migrated, smoke-tested

  5. 5
    Verify→Release

    A person accepts the test evidence and signs the release

Every approval carries a name and a timestamp.

For you and for your auditors. Errors in production come back to Build as new work, and go through the same gates.

ISO/IEC 27001:2022 · TÜV RheinlandRuns on your own serversThe AI model you chooseNo lock-in: your code stays yours

Walk the Orlian campus at orlian.ai ↗

*Up to 90%: tested and verified on real, independent application development. Results depend on the project's scope, codebase and starting point.

We should talk if you have

Three reasons to stop by booth 16.

Bring the system you are thinking of rebuilding. We open Orlian on a real project and show you where a person approves, and what the record shows afterwards.

01

A legacy system nobody understands

Orlian reads the code, screens and database first, and flags what it can't verify.

02

Code that can't leave your building

It runs on your own servers, with the AI model you choose.

03

Auditors asking who approved what

One ID traces every change from goal to production. Every approval is signed and timed.

Security

Built to pass the security review, not to survive it.

More at orlian.ai ↗
  • Runs on your own servers, with the AI model you choose. Your code stays yours.
  • Production is read-only by default. Patches ship only on approval.
  • Every action is logged with actor, timestamp and correlation ID.
  • Threats are modelled at design time, and every change gets security scanning.
  • ISO 27001 certified delivery, audited by TÜV Rheinland.
Build with Orlian, our AI SDLC platform

Up to 90% less project cost. A person signs every gate.

Seven stages of specialist AI agents carry the work from the first requirement to production, and a named person signs each hand-off. On real, independent application development it has taken up to 90% off project cost, which is what moves borderline cases over the bar.

Seven stages, one red thread Build  ·  Prove  ·  repeat
  • Analyzereads the code, screens and data you have
  • Planevery rule becomes a typed requirement
  • Buildtests first, then the code
  • Human gatea named person signs every hand-off
  • Stage & Verifyreal data, proven rule by rule
  • Releasecut over, with a way back
  • Operateread-only in production
agents do the lifting a person decides every action logged
01

Read first, rebuild second

Before anything is rebuilt, Orlian reads the code, screens and database you already have and writes down what the system really does. Your own team confirms that picture before the work moves on.

02

Every gate is a person

The agents propose; a named person approves. Five signed and timed gates, and anything architectural, security-sensitive or wide-reaching always goes to an engineer.

03

One ID, from the goal to production

Every requirement keeps one ID through the ticket, code, tests, release and production. When something breaks, the error names the rule it broke and the goal at risk.

See every wing in 3D at orlian.ai ↗, or bring a system to booth 16 and we will walk the thread live.

The red thread

One ID, from the goal to the running system.

When something breaks, Orlian tells you which requirement it violates, and which business goal is at risk.

OBJ-0001goal
BRQ-0014requirement
#162ticket
PR 250code
AI-004test
RC 1.4.0release
ISS-0042prod error
Without the threadValidation error on table 87.

Someone now has to find out which rule broke, and why it exists.

With the threadViolates BRQ-0014, which realises OBJ-0001.

The rule, the goal at risk and the person who approved it, in one line.

Screen every platform: keep, connect or replace.

From Marcelo's session. Bring one platform to booth 16 and we will put it through the screen with you.

KeepConnectReplace
Licence and run costFair for what it doesFine; the process around it isn'tRising, used or not
Customisation depthMostly standardStandard core, side workaroundsDeep: your rules, not theirs
Where your rules liveInside the platform, documentedIn email and spreadsheetsDeep in vendor configuration
What the business getsA reliable system of recordLate, partial informationYour own logic, rented back

Thirty minutes. No slides.

We open Orlian, pick a live project and walk the thread with you: how a requirement becomes code, where a person approves, and what the record shows afterwards. Bring a system you are thinking of rebuilding.

Book a Meeting → Explore orlian.ai ↗
Governed: the band around everything

Nine phases, eight gates, from intake to the day it is retired.

Whether it is a planning application, a drawing pipeline or an assistant over plant data, the trust layer is the same. Ordinary controls don't cover a model that drifts, an output nobody re-checks, or a prompt turned against you, so every AI system we build runs a nine-phase lifecycle with eight documented go/no-go gates, structured on the NIST AI RMF functions and mapped to the EU AI Act and ISO/IEC 42001. Governance here is a design constraint, not a countdown.

Map: what this system is, and what it touches Phases 01 to 03

Classify the system against the EU AI Act and NIST AI RMF, name what it touches on the line and who owns it, inventory the data with recorded provenance, then set the risk tier that decides how hard the rest of the lifecycle has to work, and how much may run without a person.

01Initiate & scope02Data & knowledge03Design & architecture
Every phase has a named owner on a RACI: one person Accountable, not a committee. Eight go/no-go gates sit between the phases, each a short, documented decision. Gates are cheap; drift is expensive. Every approval carries a name and a timestamp, so the audit trail writes itself.
Four ways AI systems go wrong in a plant, and what catches each
The unbounded change A system allowed to alter more than the task needs (a line configuration, a schedule, a threshold) with nobody able to undo it. Caught by a permission matrix and a hard human-approval step on anything irreversible. Set at Phase 03 · Design & architecture
Prompt injection & leakage Instructions smuggled in through a supplier document or a drawing the model reads. Caught by adversarial and red-team evaluation against the OWASP LLM Top 10, before launch and on every material change. Tested at Phase 05 · Evaluate & red-team
Silent quality drift A system that passed at launch and quietly stopped being right: a new part family, a changed drawing template, a new supplier. Caught by sampled online evaluation against the launch baseline, with a human-feedback loop. Watched at Phase 08 · Monitor & observe
Unaccounted data Nobody can say where a piece of grounding or training data came from: which drawing revision, which plant's numbers. Caught by a data inventory with recorded provenance and a documented basis for use. Established at Phase 02 · Data & knowledge
The governance framework: nine phases, eight gates, in full →
Assurance stack Continuously verified
The companyISO/IEC 27001:2022 · ISMS
Your dataEncrypted · minimised · deleted
Your codeSecure SDLC · gated releases
Your AIEU AI Act · NIST AI RMF · ISO/IEC 42001
13+ years200+ clients0 unanswered questionnaires
ISO/IEC 27001:2022 Information Security Management System Certified by TÜV Rheinland, an accredited certification body.
Certificate holder
Focaloid Technologies Private Limited
Standard
ISO/IEC 27001:2022, the current revision
Certificate no.
9000041009
Issued by
TÜV Rheinland
Public register
Certipedia, TÜV Rheinland's open certificate database

Verbatim from the certificate scope “Information Security Management System covering Software Development Services encompassing AI, Data & Analytics, Cloud & DevOps and Digital Engineering including supporting functions such as Finance, IT, Administration and Human Resources.”

Verify the certificate on Certipedia ↗ Opens TÜV Rheinland's register in a new tab · no login, no gate
Vendor security review Cleared
Is the supplier ISO 27001 certified?
Where is our data stored, and for how long?
Who has access, and how is it revoked?
How is code reviewed before release?
What stops the AI taking an irreversible action?
How was it tested before it touched the line?
CAIQ · SIG-lite · your own spreadsheet Typical turnaround ≤ 2 business days
In most engagements we work inside your cloud tenancy: your account, your region, your keys. Your data never leaves an environment you control, and offboarding is a matter of revoking access rather than trusting a deletion promise.
Where this usually starts

Bring the system, not the use case.

You don't need an AI idea. You need the system that costs you every day. These are the ones we see most often on a plant's list.

A legacy system nobody understands

Built years ago, documented badly and owned by one person. Orlian reads it first and writes down what it really does.

Starts with a read

A platform renewal you'd rather not sign

The licence keeps rising, used or not, and your own rules are rented back to you from vendor configuration.

Keep, connect or replace

The MES add-on stuck on the list for years

Or the supplier portal. Ideas that never got funded because the build estimate was too high.

Often the surprise

A large OutSystems estate nobody has scoped

Where the real question is what genuinely has to be rebuilt and what can simply be lifted.

Starts with a map

Something else? That is fine. Name it and we will tell you honestly whether to keep, connect or replace it, including when the answer is keep. Name one system →

Proof

Thirteen years inside real plants: applications, data and connected products, still running.

Five engagements, described rather than named. Client names are shared under NDA when we meet.

Automotive · Fortune 500 Tier 1 safety supplier · Europe / Global

Six years and still running, across plants

For a Fortune 500 Tier 1 automotive safety supplier, the applications and data its European and global plants run on day to day:

  • Test-order planning across plants, scheduling around equipment capacity and site calendars.
  • Production-line configuration for process engineers, replacing the spreadsheets and email it lived in.
  • Supplier risk tracked across four operating divisions.
  • The daily reporting the plants run on.
In production · year six
Engineering & inspection · Enterprise · Europe

Safe operating limits for chemical and refinery plants

For a European engineering and inspection enterprise: sensor thresholds tracked against equipment wear, so the limit a plant runs to reflects the state the equipment is actually in.

7+ yrsworking relationship, and counting In production
Automotive components · Global group

One master data layer, and drawings that are no longer retyped

For a global automotive components group: master data management across plants and product lines, and the engineering drawings that used to be keyed in by hand now digitised, structured and searchable.

5+ yrsworking relationship, and counting In production
Automotive OEM · Connected car · IoT

A car that sets the house before it arrives

For a global automaker: a connected-car-to-smart-home bridge. The vehicle's position against a home boundary drives presets for lights, HVAC and the garage door, through a home control unit and a cloud layer, automatically or with the owner's confirmation. Two phones per home, presence resolved between them, a manual override that always wins.

Shipped · app, control unit, cloud
Industrial automation & robotics · Service platform

Service requests for CNC, robots and lasers, from the floor

For a global industrial automation maker's customers: register machines by model and serial, raise service, spare-part and repair requests against the installed base, confirm out-of-warranty charges by OTP, and track every request to closure, with an admin panel that runs the back office.

In production · end users, makers, dealers
The shape of the work above inside plants and around their products, for years
Plant applicationsPlanning, line configuration, supplier risk and the daily reporting: the systems a plant opens every morning.
Engineering & master dataDrawings digitised, master data governed, safe limits tracked, and the governed pipelines underneath all of it.
Connected productsA car that talks to a house, a service platform for an installed base: the software around the machine, not just inside the plant.

Applications and data first, AI where the number says so. Every rebuild on top of this work now runs on Orlian, with a person signing every gate.

Databricks partner ISO/IEC 27001:2022 certified Thirteen years building software
Who you will meet

Four of us, at booth 16 on both days.

Not a sales team. The people who would run the work on Orlian, so the conversation on the stand is the conversation you'd have on the project.

Venkat Ramakrishnan
Co-founder & CEO

Venkat Ramakrishnan

Talk to Venkat about the business case: the system that never got funded because the build estimate was too high.

LinkedIn →
Prasobh Veluthakkal
Co-founder & CTO

Prasobh Veluthakkal

Talk to Prasobh about how a requirement becomes production code on Orlian, and where a person signs off.

LinkedIn →
Marcelo Navarro
Subject-matter expert

Marcelo Navarro

25+ years signing off the spend in international manufacturing. Talk to Marcelo about the platform renewal you'd rather not sign.

LinkedIn →
Kai Hackbarth
Subject-matter expert

Kai Hackbarth

Twenty-five years in industrial IoT, much of it at Bosch. Talk to Kai about the legacy plant system you can't afford to replace the old way.

LinkedIn →

If you would rather not book anything, come by booth 16. We are on the floor both days, and at the evening reception on Tuesday.

From the floor

Two days in Munich.

Booth 16, a session on the Wednesday, and a lot of thirty-minute conversations about processes nobody had written down.

The Wednesday session under way, with the speaker's background slide on the screen beside the stage.
Speaking from the stage in front of the summit backdrop, with a question slide on the screen.
The session room from the back, tables of delegates facing the stage and the slide screens.
Three of the team at booth 16, in front of the stand screen and the roll-up banner.
The stand on the second day, laptops and tablets laid out along the counter.
A conversation at the stand, with the Orlian mark on the screen behind.
A delegate reading the roll-up banner at the booth.
The networking hall between sessions, delegates talking around standing tables.
The ask

Name one system. We'll tell you whether to keep, connect or replace it.

Tell us about the one platform or process everyone agrees is holding you back. We come back with a straight view on what it would take, including when the answer is keep. It is the first question we ask on Orlian, and the best signal either of us will get from twenty minutes.

Prefer to talk?

Book 20 minutes in Munich with one of the four of us. Bring the system; we'll bring the questions. Slots on both days, and at the Tuesday evening reception.

Book a Meeting → European hours · no deck · a working conversation
Practical
Event
European Manufacturing & Supply Chain Summit
Booth
16
Venue
Holiday Inn Munich City Centre
Dates
Nov 3 & 4, 2026

We are on the floor both days. If you would rather not book anything, just come by.

The system or process you would want us to look at

Four fields. One line on the system is enough, and we will come back within two working days with an initial view and a question or two.

No phone number, no job-title dropdown. We read the process line ourselves.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Thanks. We have it.

Someone will come back to you within two working days with an initial view, and a question or two if we need them. If you are at the summit in the meantime, come and find us at booth 16.