Macula · sectors · All Macula for… pages
With Macula each company runs its own node: it publishes what it has done (order confirmed, goods shipped, payment made) and reacts to what its customers, suppliers, carriers and bank publish. No company in the chain owns the process or stores the others' orders. Stations pass messages on and keep none of them; the admin of the chain's realm decides who and what is admitted, and nothing else. Without Macula, by contrast, an order between companies runs through customer portals, EDI networks and e-mail. We are looking for partners to build it with.
An order touches the buyer, the supplier, a carrier, a warehouse, sometimes customs, and a bank. Each keeps its own systems. Between them, people fill the gaps by hand: a supplier portal per customer, PDFs by e-mail, phone calls to ask where the truck is, and spreadsheets that are out of date by lunchtime.
retyped by hand
Each one asks you to log in, retype data your ERP already holds and follow its data model. Small suppliers often cannot afford to connect at all.
one outage stops all
Maersk, June 2017: the NotPetya malware took down the company's corporate network, and with it 17 of the 76 port terminals its APM Terminals arm ran. The cranes and trucks worked. The shared IT behind them did not.
a rival sees your orders
The platform's owner sets the price and sees every order that passes through it. TradeLens, the shipping platform of Maersk and IBM, closed in 2023; its owners said it never reached full global industry collaboration.
The usual B2B integration puts one engine in charge: a platform or workflow engine owns the process and sends each company commands. Between companies that breaks, because the other company may refuse, be late or be offline. With Macula each company publishes what it has done, and the others decide what to do about it. Architects call this choreography instead of orchestration.
Nobody owns the process. It is the sum of what each company does with the facts it receives, so a new partner joins by subscribing to the facts it needs and publishing its own.
Sometimes one company has to ask another for something. Macula has exactly two message types and keeps them apart.
Request · asking for something
"Please deliver 40 pallets by Thursday."
Fact · something that happened
"Order 7731 confirmed. Goods despatched at 14:02."
Sending a request does not mean it happened. Plan only once the other company publishes that it did. Each company owns its own facts; nobody owns the whole process.
Each company runs its own small Macula node next to the systems it already has. The node dials out to the Macula Mesh, a network of stations that link up to form the mesh, keep its phonebook (a Kademlia DHT: which node offers what, and where to reach it), and relay requests and facts between authorized members. One mesh carries many Macula Realms. Each realm is an identity space on the mesh with its own key: its operator admits anything that can be given an identity, such as people, companies, services, machines and devices, gives each a certificate signed with that key, and can revoke it. Macula runs the community realm; a company or sector body can run its own under a Macula licence. Each company then decides which of them may send it which requests, and whose facts it accepts. No company opens a port, and no station keeps a copy of what it relays or anyone's business data. Anyone can run a station, as many as they like; the more stations, the stronger the mesh. Macula runs a number of seed stations and a community realm.
Every node connects outward, so no company has an open port facing the internet. The stations carry the traffic but keep no copy of it and none of your application data; each company keeps its own record of the shared process on its own machine.
Each step belongs to the company that does it. Each already has an industry standard, and Macula sends the messages that standard defines.
place_order
The buyer's purchasing system asks the supplier for 40 pallets by Thursday.
Peppol BIS Ordering · RosettaNet 3A4 "Request Purchase Order"
order_confirmed
The supplier accepts. Only now does the buyer plan the goods in.
Peppol Order Response · the confirmation half of RosettaNet 3A4
goods_despatched
The pallets leave the dock. The buyer's warehouse and the carrier both hear it at once.
DESADV (VDA 4987, Peppol Despatch Advice) · RosettaNet 3B2 · GS1 EPCIS ObjectEvent
shipment_departed · shipment_arrived
The carrier publishes its own progress. Nobody phones to ask where the truck is.
DCSA TransportEvent · IATA ONE Record LogisticsEvent · e-CMR
goods_received
Counted and booked in. The supplier now knows its invoice will be accepted.
GS1 EPCIS ObjectEvent (receiving) · papiNet BusinessAcknowledgement
invoice
The legal invoice still travels over Peppol, as Belgian law requires since 1 January 2026. Macula sends the process messages around it, not the invoice.
Peppol BIS Billing 3.0 (UBL, EN 16931)
invoice_approved · payment_executed
The supplier sees approval and payment as they happen, instead of chasing them.
ISO 20022 camt.054 debit/credit notification
The fact names are illustrations; the standards are real and in use.
your record
Every fact you publish or receive goes into your own log, in order. Replay it, audit it, and build any view you need, such as every order that has shipped but not been invoiced. There is no shared database to breach or switch off.
your rules
What you do when a partner's fact arrives is your decision, written as your own rules. Change them without asking anyone. Partners see only the facts you choose to publish, never your internal events.
your circle
You decide which partners may send you which requests, and whose facts you accept. Anything from anyone else is refused before your code sees it.
your machines
Your node runs where you choose. When one company is down, the orders that need it wait. Orders between the other companies carry on, because no shared system went down with it.
Macula does not invent a new business language. Every sector has settled on its own vocabulary, and many of those split cleanly into requests and facts: RosettaNet's "Request Purchase Order" is a request, its "Notify of Advance Shipment" is a fact. The newest standards are event standards outright. They usually run through an EDI network, a central repository or a platform. Macula sends the same messages these standards define, company to company.
These rules say what must travel between companies and leave open how. Each deadline below is one a group of partners has to meet.
no open door
Every node connects out to a station; a station never dials in. There is nothing at your site for a scan from the internet to find.
closed by default
A service answers nobody until you list who may call it, and delivers no one's facts until you list whose you accept. Serving anyone is something you have to write down on purpose.
signed facts
Every published fact carries its publisher's signature, and the receiving node checks it before anything is delivered. A station that relays a fact cannot make it look like someone else's.
post-quantum
Keys and signatures use the new methods chosen to resist future quantum computers, so a signature made today is not expected to be forgeable by one.
sealed content
Every request is sealed to the receiver's own key, and a group's facts to the group's key, so the stations in between carry only ciphertext. A request in the clear is refused unless the service has explicitly allowed it.
your own record
Each company keeps its own log, in order, so audit, replay and new views never depend on a partner or a vendor being there.
Processes shared by a handful of companies, where no single company should own the platform. A mid-size company is the natural start: it has to use each big customer's portal, and it is itself the hub for small suppliers that no platform reaches.
Partners bring the companies, the connections to their systems and the orders; we bring the station software, seed stations and each company's own log, and the chain runs a realm of its own under a Macula licence. We are looking for partners in three roles.
run a pilot
A mid-size company and a few of its customers, suppliers, carriers or its bank, ready to run one shared process across the mesh with us, such as order to cash around the invoice.
connect the systems
You connect ERP, warehouse and transport systems and already carry the standards your clients use. Help us turn those messages into requests and facts on the mesh, so your clients keep the systems they have.
pilot or research
A port, a logistics cluster, a sector association or a university group that wants to run a shared process without a platform with us, measure it, and publish what they find.
No company in the chain owns the process or stores the others' orders. Each company publishes the facts it is responsible for and reacts to the facts of others.for buyers
A request can be refused; plan only once the other company publishes that it accepted.for architects
Data spaces such as Gaia-X share data between companies; Macula passes the process messages between them.for funders and policy makers