Nothing runs until a person approves it
The AI drafts. By default a person other than the author approves each version. An admin can let the AI activate tested versions of one workflow, and that is shown on the workflow.
Approve a workflow Integration platform, hosted in Finland
AI builds your integrations. People stay in control.
Ask Claude, ChatGPT or GitHub Copilot for the integration you need. Liitora checks it, a person on your team approves it, and only then does it run, with a record of everything it does.
Early access now, with half price for the first year. Tell us one integration you need and we set it up with you.
AI Your AI assistant
I wrote the workflow Leaver access check. It is in Liitora, waiting for someone on your team to approve it.
liitora · save_workflow · tests 4/4 passedApprove Leaver access check
Made by an AI assistant ✓ Tests 4/4 Version 3
When HR marks someone as left, check Entra ID and GitHub for access that is still there, open a ServiceNow ticket for each account and email the owner.
What this workflow can use
- EMicrosoft Entra ID read users and groupsConnection
- SServiceNow create ticketsConnection
- GITHUB_TOKEN name only, the value stays hiddenSecret
Runs in Helsinki · Approver: someone other than the author Approve and activate
By default, nothing runs until a person approves it
A person approves each versionThe default for every workflow. Not the AI, and not the author.How approval works
The problem
AI can build an integration in minutes. Nobody can let it run one safely.
So most teams pick one of two bad options.
Option 1: Wait for IT
The backlog wins
- Months for a simple sync
- People build shadow spreadsheets and scripts
- The AI tools you pay for sit unused
With Liitora: the safe lane
AI writes, a person approves, Liitora runs
- Integrations in days, written by the AI tools you already use
- Each one reaches only the systems it declares
- A person approves each change, and every run is logged
Option 2: Wire AI straight in
The keys go with it
- An agent with production credentials
- No review, no tests, no record
- Hard to explain to an auditor
How it works
AI writes. Liitora checks. A person approves. Liitora runs.
You keep using the AI assistant you know. Liitora is the careful part between its idea and your systems.
1. AI writes the workflow
You In your AI assistant
When HR marks someone as left, check that their Entra ID and GitHub access is gone. Open a ticket for anything left over.
name: Leaver access checkon: webhook: hr-leaverssteps: - id: entra uses: microsoft/entra.user-access@v2 with: { connection: entra-prod } - id: github uses: github/org.member@v1 - id: ticket if: ${{ steps.entra.outputs.active || steps.github.outputs.member }} uses: servicenow/incident.create@v12. Liitora checks it
What it does
When the webhook hr-leavers receives a delivery, look up the person in Entra ID and GitHub. If any access is left, open a ServiceNow ticket and email the owner.
Before it can be activated
- The file is valid and every action exists
- 4 of 4 tests passed in a sandbox, with no real system touched
- Every connection and secret it needs exists
- A person must approve this version
3. A person approves it
- id: ticket- uses: servicenow/incident.create@v1+ uses: servicenow/incident.create@v2+ - id: notify+ uses: platform/email.send@v1What changed in what it can use
- @Email to the account owner new in this versionAdded
Written by an AI assistant · Approver: Anna, IT securityApprove and activate
4. Liitora runs it
- Look up the person in Entra ID212 ms
- Check GitHub membership retried once after a timeout1.4 s
- Open a ServiceNow ticket388 ms
- Email the account owner95 ms
Every input, output and HTTP call is logged, with secrets masked. A failure alerts the people you choose.
Safe by design
Built for the person who has to say yes.
Every control below is part of every plan. None of it is an add-on.
Each workflow reaches only what it declares
Its connections, secrets and hosts are listed up front. A call to anything else is refused.
Least privilegeSecrets stay with people
AI assistants see secret names only. People fill in the values, which are encrypted and never shown again.
Add a secretEvery workflow ships with tests
Tests with mocked systems run on every save. A version can be activated only when its tests pass.
Workflow testsA full audit trail
Who wrote, approved, changed and ran what, and when. Run logs show every step's input, output and calls.
Read run logsYour data stays in Finland
Liitora runs on UpCloud in Helsinki, and calls to your systems leave from one fixed address you can allow.
Where your data goes Examples
Start with the work nobody has time for.
Ready-made workflows from the library, or your own. Each one is plain YAML you can read.
Security
New certificates for your domains
Check crt.sh for new certificates on your domains and alert security. A new certificate can be a phishing site or shadow IT.
See the workflowKnown exploited vulnerabilities digest
Match new entries in CISA's catalog against your software inventory and email security a CSV of the matches.
See the workflowRoute security alerts to the right team
Receive alerts from your tools, enrich them from the asset register and post them to the owning team's Slack channel.
Compliance
Major incident reporting clock
Keep the DORA reporting clock and remind you before each deadline. People still write and send the reports.
See the workflowPrivileged access review
List each privileged Entra ID group's members, nested groups included, and email the owner a CSV to confirm or remove.
See the workflowSanctions list updates
Fetch the EU consolidated list, compare it with yesterday's and flag new matches against your customer register for review.
IT and HR
Leaver access check
When HR reports a leaver, check Entra ID and GitHub for access that is still there and open a ticket for each account.
See the workflowOffboard a leaver in Microsoft 365
Disable the account, sign the person out everywhere and remove them from access groups. Try it safely first.
Read the how-toNew starter accounts
Read new starters from the HR system, create their accounts and groups, and email the manager a checklist.
Finance and operations
Bank reconciliation exceptions
Read the bank statement file from SFTP, match it against the ledger and send finance only the lines that don't match.
Partner file transfers
Pick up files from a partner's SFTP, check them, convert CSV to XML and deliver them to S3, with a receipt for each file.
Order sync between two systems
Copy new orders from the web shop's API to the ERP, and remember what was already sent so nothing is sent twice.
Works with
The AI you already use. The systems you already have.
AI assistants
- Claude
- ChatGPT
- GitHub Copilot
- Any MCP client
Connect your assistant to Liitora in a few minutes. It can write, test and explain workflows. It can't approve a version or read a secret value, and it activates a workflow only where an admin allows it.
Connect your AI assistantYour systems
- REST and JSON APIs
- Webhooks
- Schedules
- SFTP
- S3
- XML
- CSV
- Microsoft 365
- ServiceNow
- Slack
- AWS
Not a thousand connectors. One careful way to reach any system with an API, a file drop or an inbox.
Create a connection For regulated teams
Made for the audit, not only for the demo.
NIS2, DORA and the EU AI Act ask you to show who approved what, what each automation can reach, and what it did. Liitora keeps that record for you. Your compliance team decides what it proves.
- Two people for every changeBy default the author can't approve their own version, and an AI assistant can't approve one.
- A Finnish company on a Finnish cloudLiitora Oy, hosted by UpCloud in Helsinki. The list of subprocessors is published before launch.
- Your data, exportable and deletableExport everything as files you can read, or delete your company for good.
- Run it inside your own network Coming soonA runner in your environment keeps secrets, data and calls with you. Liitora only plans and shows the runs.
Pricing
One flat price a month. No surprise bills.
Every plan has unlimited people and workflows, and every safety control. You pay for the plan, not for each person or each run.
We publish prices soon. Early-access customers get half price for their first year.
Team
For a team that wants its first integrations done safely.
Price coming soon
A flat monthly price, excl. VAT
- Approval, tests, audit trail and export
- Schedules every 5 minutes
- Run logs kept 30 days
- Email support within 2 business days
Business
For companies that answer to auditors, with sign-in through your own identity provider.
Price coming soon
A flat monthly price, excl. VAT
- Everything in Team
- Single sign-on (SSO) and SCIM Coming soon
- Audit and logs to your SIEM Coming soon
- Audit kept 1 year, run logs 90 days
- 3 runner groups in your own network Coming soon
- Schedules every minute
- Support the next business day
Enterprise
For banks, the public sector and larger companies with their own terms.
Priced with you
Billed yearly, excl. VAT
- Everything in Business
- Your own encryption keys (BYOK and HYOK) Coming soon
- 20 runner groups Coming soon and more environments
- Run logs kept 365 days
- Uptime SLA and a named contact
- Help with your security review and DPA
Try Business for 30 daysNo card needed. When the trial ends, nothing is charged: workflows pause, and you can export everything for 30 days.
Need more runs one month?Add a run pack for that month instead of changing your plan. Nothing is billed unless you choose it.
Small company?Companies under 20 employees get Business at half price. Early-access customers get half price for their first year.
Our pricing promise
- Building and testing are always free: test runs and dry runs never count.
- 90 days' notice before any price or limit change, and no silent cuts.
- A public definition of a run: one start of a workflow, however many steps it has.
Questions
What people ask first
Does the AI run anything by itself?
Not by default. An AI assistant can write and test a workflow, but it saves drafts. A person on your team approves each version before it runs, and Liitora runs the approved version exactly as written.
An admin can choose, for one workflow at a time, to let the AI activate versions whose tests pass. Liitora doesn't run an AI model of its own.
Where is my data?
Liitora runs on UpCloud in Helsinki, Finland, and run logs and files stay there. Each workflow shows where its data goes before you approve it.
What counts as a run?
One production start of a workflow, from its trigger to its end, however many steps it has. A poll that finds three new items starts three runs, and a poll that finds nothing starts none. A workflow started by another workflow is its own run. Test runs, dry runs and workflow tests never count.
Is there a free plan?
No. Instead, you can try Business free for 30 days, with no card. We would rather spend our time helping teams who are evaluating Liitora seriously, and keep every customer's fixed outbound address clean. Building and testing workflows never count towards your runs.
Can I run workflows in my own environment?
Soon. A Liitora runner in your own network will keep a workflow's secrets, data and calls with you, while Liitora plans the runs and shows their status.
Which AI assistants work with Liitora?
Claude, ChatGPT, GitHub Copilot in VS Code, and other assistants that support MCP. You connect it once, and it works with your own account and permissions.
Can I leave and take my workflows with me?
Yes. Workflows are plain YAML files you can read, and you can export everything your company has in Liitora at any time.
Is Liitora certified, for example ISO 27001 or SOC 2?
Not yet. We are a young company and say so. Until then, our security overview describes every control, and the DPA and the list of subprocessors are published before launch.
When will prices be published?
Soon, once our production costs are confirmed. Every plan is a flat monthly price, excluding VAT. Ask us for early access and we tell you the price before you commit to anything.
Tell us one integration you need.
We set it up with you in the pilot, on your systems, with your approvers. If Liitora isn't the right tool for it, we tell you.
Or write to hello@liitora.com