Composa

Integration platform, AI-assisted

Connect your systems so you can spend more time connecting with people.

Composa connects your ERP, web shop, accounting system and trading partners, and moves the orders, invoices and shipping notices between them by itself — so your team spends less time chasing files, and more with customers, colleagues and friends. Describe what you need, approve the plan, and see every message along the way.

AI-assisted, human-approved

Describe the integration in plain words. The Integration Wizard proposes a plan and builds it once you approve.

Connects what you have

APIs, databases, files, EDI, email and PDFs — your ERP, web shop, accounting system and trading partners.

Governed and secure

Development, Test and Production, approvals and roles, with every stored secret encrypted.

Nothing is a black box

Every message has a reference you can search for, and everything that was built can be opened and read.

See it in action

From a description to a running integration

One dashboard shows what is healthy, what needs your attention, and what is waiting for your approval — and every number on it opens the messages behind it.

Explore the platform
The Composa dashboard: platform health, live workflows, message volume, workflow status, items needing attention, capacity, approvals and connections.

Integration work is slow, opaque, and depends on one person who knows how it was built

Scripts nobody dares to changePoint-to-point code that works until the person who wrote it leaves.
Suites that need a teamEnterprise integration tools priced and staffed for enterprises.
Messages that vanishWhen an order goes missing, nobody can say where it stopped, or why.
Weeks per new partnerMost of it spent reading the partner's guideline document.

Composa's answer: visual, traceable, governed — and AI-assisted where the tedious work is.

How it works

Five ideas, and you can hold all of them in your head

Channel

Where messages come from or go to: a folder, SFTP, an API to poll, a webhook, email, a Kafka or JMS topic, Peppol.

Workflow

One channel in, a pipeline of steps, one channel out — drawn as a flowchart you can read.

Mapping

A reusable transform from one document shape to another, drawn in a visual mapper.

Partner

A trading partner. Composa works out who sent a message from where it arrived, its envelope, or its content.

Environment

Development, Test and Production — fully separated, with controlled promotion between them.

The building blocks

Twenty-one kinds of step cover the real cases

A workflow is built from ready-made steps, each with its settings in plain boxes. Fields are picked from lists built from real messages, and a setting that cannot work is refused when it is saved — with a reason — not discovered when a message fails at 2 a.m.

Reaches another systemAPI call · Database · Email
Changes the documentMapping · Adapter · Content modifier · Text file · Excel · EDI · Extract from PDF and Word · Combine · Join · Envelope · Python
Decides where it goesRouter · Splitter · Aggregator · Filter · Sync state
Looks without changingDebug checkpoint · Archive

One workflow, three steps, no code: a supplier's invoice arrives as a PDF; its fields are read; the customer's account is looked up through the ERP's API; a ready-made XML invoice is filled in and delivered.

The workflow editor: steps grouped by what they do on the left, the pipeline running top to bottom, and the selected step's settings on the right.
The workflow editor: what you see is what runs.

The Integration Wizard

Built with AI. Owned by you.

Describe the integration you need. The Wizard looks at the APIs, channels and mappings you already have, proposes a plan, and builds it with the platform's own building blocks — so everything it makes can be opened, read and changed by your own people.

  1. 1DescribeIn plain words: what comes in, what goes out, what happens in between.
  2. 2Review the planThe plan says what the Wizard assumed. Nothing is created until you approve it.
  3. 3Drafts, checkedIt checks its assumptions against real API specifications and sample data, and builds drafts.
  4. 4You go liveA person promotes the work to Production. The Wizard never does.

No hidden code

What the Wizard builds is an ordinary workflow, mapping or adapter — on the same screens as anything built by hand. Mappings are standard XSLT or JSONata.

Held to the same rules

The checks that refuse a setting that cannot work apply to the Wizard exactly as they do to a person. It cannot save what a person could not.

Never sees secrets

Credentials are entered by a person and are never shown to the Wizard. Designing a database query, it reads table and column names — never rows.

"An AI that writes code hands you something to trust. Composa's Wizard hands you something to read."

Transparency

Always able to answer “what happened to that order?”

Every message

  • Its own reference, carried end to end and searchable
  • Found by order or invoice number — even when it arrived as a PDF
  • A failure emails you a link, the likely causes and what to check
  • Debug checkpoints show a message at any point in the pipeline
  • Reprocess a message, or replay a delivery once the receiver is back

Every change

  • Every save of a workflow or mapping is a version, with who and when
  • Open any earlier version; make any version the live one
  • Saving a draft never changes what is running
  • Promotion between environments is logged: what moved, who asked, who approved
  • The Wizard's work is traceable: what it was asked, planned and assumed

Governance and security

Control without bureaucracy

The rules live in the platform, not in a process document.

Promotion with gates

Development, Test and Production, fully separated. Prerequisites are checked, Production needs approval, and a go-live checklist is read from the configuration — not ticked by hand.

Roles and sign-in

Permissions per section and per environment, enforced by the server. Sign in with Microsoft 365 work accounts, and require two-factor authentication per role.

Secrets encrypted

Every stored password, key and token is encrypted (AES-256-GCM), with the key held outside the database.

Each customer isolated

Tenant isolation enforced in the data layer. Each customer's Production runs in its own instance, so one customer's peak never slows another's.

No path out of a message

Mappings and expressions cannot read files or call URLs; outbound calls are guarded against being pointed inwards; user scripts run sandboxed with no network.

Failures you hear about

Nothing is lost silently: failures are recorded with their reason, duplicates are detected, and EDI acknowledgements are matched — an overdue one raises an alert.

Your data stays yours

Encrypted, or not kept. Your choice, per workflow.

  • Encrypt what is stored. One switch encrypts every stored message, failure detail and archive. A copy of the database holds no readable invoice or order.
  • Or do not keep it. For the most sensitive documents, Composa records that a message arrived and was delivered — and stores nothing of what it said.
  • Still find every message. Choose a few search fields, such as invoice or order number. Only those stay readable, so “did it arrive?” always has an answer.

What connects today

The connections a mid-sized business needs

FilesLocal and shared folders, SFTP
REST APIsRegistered from their OpenAPI specification; API key, Bearer and OAuth2
WebhooksInbound with a token per channel; outbound HTTPS push
DatabasesPostgreSQL, MySQL, MariaDB, SQL Server, Oracle
MessagingKafka and JMS
EmailIn and out, with the message attached as Excel, CSV or XML
EDIEDIFACT and X12, with adapters built from each partner's guideline
E-invoicingPeppol, through an access-point provider
DocumentsPDF and Word, read with AI-assisted extraction
ExcelReal .xlsx workbooks: numbers stay numbers, codes keep their leading zeros
SchedulingRuns on a schedule, in your time zone
Open standardsXSLT 3.0, XPath 3.1, JSONata, OpenAPI, OAGIS, GS1 envelopes

Built on proven open-source foundations: Apache Camel, the most widely used open-source integration engine, running on Quarkus.

Pricing

Pay for what flows through

Usage is metered per message by size, so a small message and a large batch are each charged fairly. You see your own usage month by month, down to the workflow, and every figure on an invoice traces back to messages.

Start with one real integration

We will set up a proof of concept on one of your integrations, with your own messages — so you judge Composa on your work, not on a demo.

Talk to us about plans

Three things to remember

1

Nothing is a black box

Every integration, every message and every change can be opened, read and maintained by your own people.

2

You stay in control

Drafts, approvals, environments and roles are built in, not bolted on.

3

The tedious part gets done

Field picking, partner guidelines and document reading are assisted, so people spend their time on the business rules.

Get in touch

See Composa on your own integration

Tell us a little about what you need to connect. We will come back to you to arrange a demo or a proof of concept.

  • A walk-through of the platform
  • A proof of concept with your own messages
  • Plans and pricing for your volumes