Miri analyzes legacy application code and artifacts, then migrates them to Simplifier. Source artifacts Miri handles include:

• SAP ABAP — reports, function modules, includes, custom programs
• Neptune SAP Edition — DXP widgets, project structure, backend logic
• Neptune Open Edition — standalone apps and OData connectors
• Lotus Domino / Notes — NSF structures, forms, LotusScript logic
• Vibe Coding — prototype / AI-generated code (Cursor, Claude, Copilot, etc.)

The LLM that is used by this service is hosted on servers located in Germany and the model is exclusively accessed by Simplifier. We do not use customer data to train models.

Usage data collected for product improvement

To continuously enhance our product, we collect the following anonymized data with each usage:

• Timestamp
• Request duration
• Number of input and output tokens
• User input
• LLM-generated output
• Anonymized customer ID

This data is securely stored in infrastructure accessible exclusively by Simplifier and is deleted after two months.

Data is encrypted at rest and in transit.

The legacy source code you upload as a migration task is processed in your private workspace. Miri documents every migration decision and maps old artifacts to new ones so you can audit and validate the result.

Learn more in the Miri Documentation and on miri.simplifier.cloud.

Miri natively supports the following legacy source platforms:

• SAP ABAP — custom reports, function modules, includes, programs, modules
• Neptune SAP Edition — DXP applications running inside SAP
• Neptune Open Edition — standalone Neptune apps, including OData-connected ones
• Lotus Domino / Notes — Notes databases (NSF), forms, LotusScript logic
• Vibe Coding / Prototype Apps — AI-generated code from Cursor, Claude, Copilot, Windsurf, or any other agentic dev environment

Miri produces a production-grade Simplifier application — including tested business logic, documented mappings, and deployment-ready assets — in all of these cases.

Common scenarios:

• SAP Clean Core — move custom ABAP extensions off the S/4HANA core
• Consolidation — multiple Neptune / Domino apps → one Simplifier platform
• Prototype → Production — harden AI-generated code for real-world use

Want to see it in action? See the example prompts and use cases or the Miri in Action video.

Yes. Miri and Anna are designed to work together:

• Miri — analyzes the legacy codebase, identifies dependencies, migrates the application to Simplifier, and produces tested + documented artifacts.
• Anna — takes the migrated application and delivers a modern SAPUI5 / Fiori user interface on top of it.

Typical flow:

1. You give Miri the legacy app (ABAP, Neptune, Lotus Domino, or prototype code).
2. Miri migrates it to Simplifier — data model, business objects, connectors, workflows, tests.
3. Anna takes over and generates the Fiori UI in a single step.

Result: a production-ready Simplifier application — with Clean-Core alignment, modern UX, and full traceability of every migration decision.

If your goal is not migration but building a new app from scratch with AI, Anna is the right starting point.

Learn more: Miri Application Migration · try Miri

Miri has 2 major software components where your data are stored and processed:

• Miri Web Interface – Orchestrating the Miri Agents and Subagents via Task Board, Cost Control, User, Roles, Rights and Cost Management
• Miri Agent – process the Task via your own LLM , connect your Sytems via MCP within your own network

Miri Agent

Miri runs a local agent on your own environment (Windows, macOS, or Linux — via daemon or Docker). That agent scans and analyzes your legacy sources — ABAP, Neptune, Lotus Domino, or prototype code — within your own network.

The LLM is your choice. You configure which AI model Miri uses — the one that has been approved by your security and data-protection officer. This can be an on-premises model, a private cloud, or a SaaS endpoint you have already cleared. Miri does not lock you into a specific provider.

In practice this means:

• Source code stays in your network — analysis, scanning and refactoring run on the local agent
• You pick the applied LLM — your approved model of choice, not a vendor-predefined one
• Compliance on your terms — the setup satisfies your security / data-protection requirements because the model endpoint is your decision

Installation of the local agent:

1. Daemon / Docker installation guide
2. miri.simplifier.cloud

Miri Web Interface

The Miri platform (miri.simplifier.cloud) is hosted at AWS in Frankfurt (EU). Only non-AI data is processed there, in particular:

• Task descriptions — the task descriptions of your migration tasks
• Attachments — files you attach to a task
• User data for login — the email address of the user used to log in to the platform
• Token Costs per User / AI Agent
• Audit Log Data (Which User do what within the Interface)

The model used lies within your responsibility. Simplifier itself does not store any data for AI training.

The data in the Miri web interface is backed up daily and retained for a maximum of 30 days. The backups are stored encrypted (AES 256).

The data processed locally in the agent depends on your personal setup and can be adapted to your requirements.