# Liitora

> Liitora is an integration platform hosted in Helsinki, Finland. Your AI assistant designs the integration between two systems, a colleague approves it, and Liitora runs exactly what was approved, and nothing else.

Liitora is run by a Finnish company. Liitora has no AI of its own: people connect their own AI assistant (Claude, ChatGPT, GitHub Copilot or another MCP client) with their own sign-in.

## What it is for

Connecting two systems that should talk. Most integrations are the same job: read what is new or changed in one system, put it in the shape the other system wants, and send it on.

- WooCommerce to a fulfilment partner: new orders from a WordPress shop go to the partner who ships them, every 5 minutes.
- Odoo to accounting: confirmed sales orders become invoices, and paid invoices are marked paid back in Odoo.
- An ERP to a web shop: prices and stock levels go to the shop. Only the products that changed are sent.
- A CRM to Odoo: new and changed customers are created or updated, matched by their customer number.
- Partner SFTP to an ERP: order files in CSV or XML are picked up, checked and posted to the ERP's API.
- An HR system to Microsoft Entra ID: new starters get their accounts and groups, and leavers lose their access.
- Any system with an API to any other. No connector to wait for.

What every sync needs is built in: it sends only what changed, nothing is lost when a run fails (the next run sends the same changes again), it retries after timeouts and "too many requests" within a request limit per system, and one bad record is set aside while the others still go.

## How it works

1. Your AI assistant designs it. It writes the workflow and its tests. When a step needs a password or key, it sends you a link to add it. It never sees the value.
2. A colleague approves it. Its tests must pass first. Then a person reads what it does in plain English, what changed, and every system it would reach. The AI can't approve.
3. Liitora runs exactly that. On a schedule or a webhook, with retries and alerts. The approved version runs the same way every time, and every run is logged step by step.

## Why an AI can't run loose in Liitora

When AI agents cause damage, it is usually the same story: the agent held live keys, decided what to do while it ran, and nobody approved the step. Liitora takes away all three.

- The AI never holds the keys. It writes drafts and tests. People add the passwords and keys, and the AI only ever sees their names.
- What runs is fixed. A person approves one exact version. That version runs as written, the same way every time, in a sandbox. It reaches only the systems it declares.
- You can prove it. Who wrote it, who approved it, what it can reach and what it did, in an audit log that can't be edited.

What the AI assistant can do: write workflow drafts and their tests, run those tests against fake answers, read run logs and explain failures, and ask a person to add a secret through a link.

What it can't do: see a secret value, approve a version, create API tokens, reach a system the workflow doesn't declare, or turn a workflow on (unless an admin allows that for that one workflow, and the workflow then shows it).

Who approves: the author of a version can't approve their own. By default, the person who asked the AI may approve its work. To make sure someone else always approves, an admin turns on Always require a second approver. Having that setting on by default for Business and Enterprise is coming soon.

AI steps inside a workflow run only if you add one. They are marked, confirmed by the approver, and an admin can turn them off for the whole company.

## Security controls

- Secrets: values live in a dedicated secret store (OpenBao), per company. They are masked in logs, outputs and errors. Showing one needs a permission and is logged first.
- Sandbox: scripts run in a WebAssembly sandbox with no file system or network of their own. HTTPS to public addresses only. Private and cloud metadata addresses are blocked. The approved version is checked again before every run.
- Network: calls to your systems leave through one fixed outbound address you can allow in your firewall.
- Records: an audit log that can't be edited, run logs with every step and secrets masked, and an export of everything as readable files.
- Stop it at any time: pause a workflow and no new runs start. Revoke an API token and it stops working at once.

## Questions your auditor asks

- Change management (DORA ICT change rules, NIS2): every version is kept. Someone who is not the author approves it. With the second approver setting, it is never the person who asked for it either. Evidence: approvals and version history in the audit log.
- Access and least privilege: each workflow declares the connections and secrets it may use. Calls to anything else are refused. Only people handle secret values. Evidence: the connections and secrets on every version, and refused calls in the audit log.
- Logging and monitoring: every run is logged step by step. Failures and late syncs raise alerts. Evidence: run logs, incidents and alerts.
- Data location (GDPR): hosted by UpCloud in Helsinki, Finland. Each workflow shows where its data goes. Evidence: the DPA and the list of subprocessors, published before launch.

## What Liitora doesn't do for you

- An approver who doesn't read approves anything. Liitora makes each approval readable.
- A wrong workflow that someone approved still runs as written. Fixed runs make it predictable, not correct.
- An AI assistant can be misled while it designs, for example by text it reads. That is why the change and everything it can use are shown before approval.
- Liitora holds your connection secrets. They are encrypted, masked and used only for the workflows that declare them.
- AI steps, if you add them, can answer differently between runs.
- We are not ISO 27001 or SOC 2 certified yet. The security overview describes every control.

Liitora keeps the record. Your compliance team decides what it proves, for example for DORA or NIS2 change management. Liitora does not claim to make anyone compliant.

## Who is behind it

Liitora is founded by Matti Lehmus, co-founder of Feedtrail and its Head of Integrations from 2015 to 2022. With major US health systems, his team took on one of HL7's biggest gaps, its missing security, and built an end-to-end encrypted integration layer with fully isolated customer environments. Feedtrail was named Best in KLAS 2024 and acquired by Relias in 2025. Profile: https://www.linkedin.com/in/matti-l-5775a412b/

## Pricing

Three plans, Team, Business and Enterprise, each a flat monthly price excluding VAT, with every safety control in every plan. Prices are not published yet. Early access is open, with half price for the first year.

## Pages

- [Homepage](https://liitora.com/): what Liitora connects, how it works, and why an AI can't run loose
- [For security teams](https://liitora.com/security/): what the AI can and can't do, how a change goes live, the questions auditors ask, and what Liitora doesn't do for you

## Docs

- [Customer guide, llms.txt](https://liitora.com/docs/llms.txt): every page of the guide, for language models
- [Customer guide](https://liitora.com/docs/): get started, how-to guides, reference and explanations
- [Connect your AI assistant](https://liitora.com/docs/get-started/connect-your-ai-assistant/)
- [Security overview](https://liitora.com/docs/trust/security-overview/)
- [Collect evidence for an audit](https://liitora.com/docs/how-to/collect-evidence-for-an-audit/)
- [AI in workflows](https://liitora.com/docs/explanation/ai-in-workflows/)
- [Security model](https://liitora.com/docs/explanation/security-model/)
- [Where your data goes](https://liitora.com/docs/explanation/where-your-data-goes/)
- [Who may approve](https://liitora.com/docs/how-to/approve-a-workflow/#who-may-approve)
- [Allow Liitora through your firewall](https://liitora.com/docs/how-to/allow-liitora-through-your-firewall/)
- [Export or delete your data](https://liitora.com/docs/how-to/export-or-delete-your-data/)
- [Workflow library](https://liitora.com/docs/library/): ready-made workflows

## Suomeksi

Liitora on suomalainen integraatioalusta. Tekoälyavustajasi suunnittelee integraation kahden järjestelmän välille, kollega hyväksyy sen, ja Liitora ajaa täsmälleen hyväksytyn version. Palvelu toimii Helsingissä, ja tietosi pysyvät EU:ssa. Sivusto ja ohjeet ovat englanniksi, mutta voit kirjoittaa meille suomeksi.

## Contact

- Email: hello@liitora.com. Early access: tell us the two systems you need to connect.