is coming

EDI middleware. Every protocol your partners insist on, every format they send, and a mapper that is a canvas and code at once.

Every protocol they ask for

SFTP, FTP, AS2, OFTP2, HTTP, SMB and plain mail — incoming and outgoing, in one place.

The formats, both ways

EDIFACT, X12, XML, JSON, CSV, Excel, SAP IDoc and fixed-width records: read, and written.

A mapper that is both

Draw the mapping on a canvas or write it as code. Neither one is a generated copy of the other.

Workflows you can see

Triggers, branches, conditions, splits and error paths — drawn where anyone can read what happens.

Answers that are owed

A CONTRL or a 997 is expected, matched against what arrives and reported overdue. Nobody keeps the list.

A face for your partners

They bring their own certificates, keys and logins — and a rotation is planned for a date instead of for an outage.

Structures to start from

EN 16931, Peppol, EDIFACT directories and FORTRAS on the shelf, and your own beside them.

Yours to run

It runs on your own machines, and every message your partners send stays in your own database.

The mapping editor: the structure of the incoming message on the left, the structure to be written on the right, lines between the fields that are connected, and the same mapping as LUA code beside them.
The mapper. The drawing and the code are one mapping, and either side may be the one you work in.
The workflow editor: two triggers, a parser, a branch, a split, mappings, a serializer and senders, connected on a canvas, with the paths taken when a station fails drawn in orange.
A workflow. What happens to a message, drawn - and written beside it, down to the paths taken when a station fails.

See both of them working, on YouTube