The process, executable.

A process here is not a diagram on a wiki page: it is a model the platform runs, with steps, owners, rules and data.

One platform for your whole organisation.

Your systems stay. metamorphOS runs the work between them, for your team, partners and virtual employees.

Your tools

Business CentralERP
ShopifyShop
PersonioHR
OutlookEmail

plus your own systems

metamorphOS
Work moves on its own
Every step goes straight to the next owner: a colleague, a virtual employee, a partner or a system.
Reliable execution
Every run follows the same rules and approvals. No step gets skipped.
Secure by design
Everyone sees only the cases and data their role allows.
Always know what happened
Every action is logged as it happens, every run is fully traceable.

External

Suppliers
Customers
Tax advisor
Service providers

Do their step via a secure link, no account needed.

Virtual employees

AI agents take on steps in your processes, with their own task inbox, managed like your team.

  • Works with your team
  • Hands over when a person must decide
  • Learns from every run
EU AI Act ready

Your team

Your team gets its work as tasks, with the facts and links attached.

Also in Microsoft Teams, with Entra ID SSO

One run, end to end.

A request for 1,200 sensor housings. An AI agent drafts the quote, a rule checks its value, and above 20,000 EUR a person approves before it goes out.

above limitwithin the limitRule
Approve automatically
Inside Sales
Qualify the request
HubSpot
Create the lead
Production planning
Confirm price and lead time
Quote Agent
Draft the quote
Route by quote value
Katrin Vogel
Approve the quote
Gmail
Send the quote
Odoo
Book the offer

People keep the final say.

You decide which steps a person takes, which a rule settles and which an agent may take. Approvals are steps in the process, not a policy beside it.

One task inbox every step arrives with its facts and files, assigned by role, not by name
Approval where the rule requires it above the limit a person approves, within it the process goes on
Hand over a step a step a person runs today can go to an agent tomorrow
Correct a single run a run can be rewound and corrected, with the change on the record
A crop of the quote run: the rule routes the quote to the approval, and the trail shows Katrin Vogel's step, the rule's and the Quote Agent's.

The quote was above the limit, so Katrin Vogel approved it. The agent's step and hers stand in the same record.

Your process
outside your company
Supplier
Your process
secure link · verified by email
the result lands in the run

And the people who have no account with you.

A secure task link verified by email, one link for one step
No account, no licence and nothing to learn on their side
The result lands in the run dated and attributable, like every other step
A mailbox per process the fallback for anyone who prefers to reply by mail

Build. Run. Monitor. Evolve.

Not a one-time setup: a living model. Four movements, one loop.

Modeled visually. Executable immediately.

Processes are drawn as graphs: steps, owners, branches, approvals. What you see is what runs. There is no translation step between the drawing and the execution.

Drag-and-drop process builder
Steps for people, systems, or an AI step
Branches and approval gates on your data
Every definition versioned, with full history

The record is a by-product.

A run ends with its result values: the quote number, the customer, the quantity, the discount, the quote total. Beside them stands every step with the actor who took it and the time it happened. Nobody writes this up afterwards; it is what running the process produced.

The result panel of a finished quote, one typed value per field: the quote number, the customer, the quantity in pieces, the discount in percent and the quote total in euros.

Your systems play their part.

The process calls your systems, and waits for them: REST in both directions, files both ways, and email as a first-class surface.

Microsoft Teams
Microsoft Teams
Microsoft Outlook
Microsoft Outlook
Google Mail
Google Mail
Google Drive
Google Drive
Google Sheets
Google Sheets
DATEV
DATEV
HubSpot
HubSpot
DocuSign
DocuSign

What the approver asks.

Data is encrypted in transit and at rest, under strict access controls, and a dedicated deployment on your own infrastructure is available. Every run keeps a complete record of who decided what, when and on which basis, so an audit becomes a query.

European data residency

Hosted in the EU. Dedicated or private-cloud setup with full data sovereignty.

ISO 27001

Certification in progress

Based in Graz, Austria

Setup and support across the DACH region

The thinking behind the platform.

Automation is not orchestration

Why task automation alone cannot run a process, and what an orchestration layer adds on top.

How metamorphOS differs

How the platform compares to single-desk workflow engines, and why that gap matters as you scale.

How it works, in short.

A model the platform runs rather than a diagram on a wiki page. Steps, owners, rules and data are part of the model, so the same thing that describes the process is the thing that executes it, run after run.

Your team, your systems, AI agents and external partners, in one process. A step is assigned to whichever of them owns it, and the run moves on when that step is done.

Through a secure task link, verified by email. They complete their step and the result lands in the run, dated and attributable. A per-process mailbox is the fallback for anyone who prefers to reply by mail.

No. The first process is built alongside your team rather than rolled out: a discovery call, the build, then production with your team in it.

Every run as it happens, every participant and every step. The audit trail is a by-product of executing the work rather than something assembled afterwards.

Show us how you work today.
You'll know what to fix first.

A discovery call with Robert: thirty minutes on where coordination costs you most.