No pause in the business
Nothing has to stop while a new platform is prepared: new applications are delivered on the technologies you use today.
Delivery from Request to Production
Merian builds rich, secure applications on the technologies you already use, at the agents' speed, and keeps every one of them portable. Reducing your dependence on one provider becomes a decision you take when you are ready, not a project that stops the business.
Delivery from Request to Production
Merian runs the delivery of a team's applications on one board. Each request becomes a card; the agents do the work, and the project's own rules decide what moves forward and when. The speed comes from the agents, the control stays with the team.
Every request reaches production through stages anyone can follow, and every release can be undone.
Strategic autonomy
A company that depends heavily on one cloud provider today cannot stop its business and wait for a new platform to be set up before it gains the freedom to move. Large or small, few of our clients can afford a strategy that starts by stopping.
So we propose the opposite order. Build new applications now, very fast, on the technologies you already use, and build them so that they can leave it. Every application delivered this way is one less thing tied to a single provider.
When the time comes to move, to your own infrastructure, to our European cloud or to another cloud provider, the applications move with their data, without being rewritten.
Nothing has to stop while a new platform is prepared: new applications are delivered on the technologies you use today.
Each application is built to run elsewhere from the start, so leaving a provider does not mean rewriting what you have built.
When you decide to move an application, it is done from the board, at the press of a button, not through a migration project.
The applications and their data belong to you, and nothing requires them to run on our platform.
The path
Like the metamorphosis Merian painted, each stage is complete in itself, and the business keeps running through all of them.
Applications run serverless inside Microsoft 365 today, with their data in SharePoint, so nothing new has to be installed or approved before the first one ships.
Where a team would assemble a Power Apps form, it gets a full application: the design its brand calls for, rich interactions, and screens people want to use.
The application does not depend on the platform under it, so the same application can run on another infrastructure.
Our European cloud is available today; Azure, Google Cloud, AWS and your own infrastructure come next. An application moves at the press of a button, when you decide.
At no stage does the business wait for the next one.
In practice
One of the groups we work for runs Microsoft 365, Power Platform and Azure. Here is what Merian changes for it, without asking it to change its technologies first.
What would have been Power Apps forms are delivered as full applications, at the agents' speed, with no limit on style or design.
The applications run serverless inside the group's Microsoft 365, and their data stays in SharePoint.
When an application meets a limit of the platform under it, our team handles it, so the limit never becomes a ceiling for the application.
When the group decides to move, to its own infrastructure, to our European cloud, or to Google Cloud or AWS, its applications go with it at the press of a button.
The platform inside
Merian is technology euphile develops entirely. It lets product builders deliver secure applications very fast, because what each stage needs is already there, with no integration to set up.
AI models, the LLM gateway, workflow management and the custody of secrets come from Tzu: every call to a model is routed, attributed and kept inside your boundary.
SAST, SCA and SBOM come from Vauban and work directly, with no integration to build: the code of every application is analysed before it reaches UAT.
Visual tests run in the browser through Merian's own runner, or in an isolated Atlas microVM when a test needs a clean machine.
Merian has its own test runner, used both for regression tests and for demos.
Used by euphile first
euphile is a digital-native company. Clients, delivery, contracts, vendors, professional services, assets and portfolio, expenses, travel and billing all have to be handled end to end, and we hold ourselves to one rule: whatever we do is digitalized before we do it, then used.
The applications that do it are built with Merian, the same way a client's are. Client relationships, recruitment, delivery management, expenses and travel already run on them, and we offer them to our clients, who use them too.
Clients, contacts and opportunities, from the first conversation to the signed contract.
Candidates, positions, interviews and offers. Good Time Group recruits its seasonal teams with it, managed in the EU and free to move.
Missions, the people on them and the time they take, followed as the work happens.
Expense claims, receipts and approvals, with no spreadsheet in between.
Travel requests and approvals, each tied to the mission it serves.
Contracts, vendor management, professional services automation (PSA), asset and portfolio management, and billing, under the same rule.
Capabilities
The agents do the work at every stage. The gates, the rules and the decision to put a version into production stay with the people who answer for the application.
Each request becomes a card. The agents write its requirements and its plan, build it on a branch of its own, and test every path it touches.
Development, Test, UAT and Production are one path, with a gate before each passage, so a card is always at a stage everyone can see.
Environments, the branching strategy and the merges from one environment to the next are managed by Merian, without the user having to think about them.
Before a card reaches UAT, its code goes to its repository and through code analysis and an AI review, so the people testing it are not the first to look.
Each project has its own rules, such as freezes and closed hours. The agents work at any time; a version goes into production only when the project's rules allow it.
Every release starts from a restore point, so any release can be undone.
Every change keeps its request, its stage and its release, so the history of an application can be read back at any time.
What the delivery of each application costs is visible in plain figures, with nothing left out.
Value stream maps show where the time goes between a request and production, and where it waits.
Every step is visible and configurable: you decide where a person must approve before the work moves on.
How it works
Five stages. The agents carry the card through each of them; a gate and a person's rules decide when it moves on.
Someone describes what the application should do. The request becomes a card on the project's board.
Requirements, a plan, the build on a branch of its own, and tests on every path the change touches.
The code goes to its repository and through code analysis and an AI review, before anyone tests it in UAT.
Development, Test, UAT and Production, with a gate before each passage and the project's release rules applied at every one.
The version goes into production when the rules allow it, from a restore point that lets it be undone.
At every stage the card shows where the request is and what it is waiting for, so nobody has to ask.
Built for
Describe what the application should do and follow the card to production, without a queue nobody can see into.
Deliver secure applications very fast, without setting up environments, branches or integrations first.
Set the gates and the release rules once for each project, and let the agents carry every card through them.
Nothing reaches production outside the project's rules, and every release has a restore point behind it.
Why Merian
Named after Maria Sibylla Merian, the artist and naturalist who raised caterpillars and painted every stage of their transformation, from egg to butterfly, on the plant they fed on. Her Metamorphosis insectorum Surinamensium, published in 1705, shows a change one stage at a time. Delivering an application is a transformation of the same kind, and Merian keeps each of its stages in sight.
Gaining autonomy is a transformation too, and it works the same way: one stage at a time, each one complete, with the business alive throughout.
A request is never somewhere nobody can see: the board shows the stage of every card, and the gate it is waiting at.
The agents do the work as fast as they can. The project's rules, set by a person, decide what reaches production and when.
A restore point comes before every release, so going forward never closes the way back.
Our experts configure the first projects with your team, train the people who will run the board, and hand the practice over to them.
Tell us about an application you need on the technologies you use now, and we will show you how it is built, and how it would move.
Meet an expert