Macula Mesh Use Build Macula for… Docs Contact

Macula · makers · All Macula for… pages

With Macula, a developer or a small firm builds a service that runs on its own machine, dials out to the Macula Mesh, and answers callers anywhere, with no cloud account, no public address and no open port. 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. Your realm's admin admits who may call. Martha, our open source crew tool, and the corpus of rules and templates it works from take a business idea to that service the same way every time. We are looking for partners to build it with.

Without Macula: a small service needs a cloud, a login system and a lot of glue

A maker with a good idea for a service, a booking tool for a club, a price feed for a trade, a register for a cooperative, usually rents a cloud server, gives it a public address, writes a login system and API keys, and pays every month whether anyone calls or not. Coding agents now write that code fast, and nobody can read it a year later.

open to the internet

Every service needs a public address and an open port

To be reachable, a service sits on a rented server with a port open to the whole internet, and every scanner on the internet finds it.

identity is homework

Login and access are built again for every service

Each service gets its own accounts, passwords and API keys, and each one is a new place for a mistake or a leak.

code nobody reads

Agent-written code with no shape

A coding agent writes whatever compiles. Without a method, every service is shaped differently, and the next person, or the next agent, starts from zero.

With Macula: your service runs on your box and dials out to the mesh

Your service runs next to a small Macula node, on a laptop, a box in a cupboard or a server you rent. 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 calls and messages 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, organisations, 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. Your service offers its answers as named procedures, publishes what happened as signed facts, and keeps its own record of events on its own disk. No station keeps a copy of what it relays or any of your application data.

Every node connects outward, so your box has no open port facing the internet. A caller reaches your service by its name on the mesh, not by an address. The stations carry the calls and facts but keep no copy of them; your records stay in your event store, on your box.

From a business idea to a service on the mesh

Martha runs a crew of Claude Code agents on any repository: one builds, another reviews, and a person says yes before anything ships. The mcl-corpus gives that crew the rules, the templates and the mistakes not to repeat. The mesh part comes from the Macula SDK and a small service library every service stands on. The whole method is on the Martha page; here is the short version.

  1. Event stormingfind what happens

    The people who know the business name what happens, in the past tense: a member registered, a book was procured, a reading finished. That list is the service's vocabulary, and the business owner can read it.

  2. One folder per capabilityregister_member/

    Each thing the service can do lives in one folder: the command, the event it produces, the rule that decides, and the door the mesh knocks on. A stranger, person or agent, finds a feature by reading folder names.

  3. Event sourcingwrite · project · answer

    The service keeps what happened, in order, in its own event store. One part writes events, one turns them into tables, one answers questions from those tables. Each part is small and dull on purpose.

  4. TemplatesErlang · scaffold

    Because the shapes repeat, the corpus holds a template for each: a command, an event, a projection, a query. One script lays out a new service with its mesh identity, its health check and its release pipeline already in place.

  5. A crew builds ittest first · review

    A builder agent writes the failing test first, then the code. A reviewer agent passes it or sends it back, and CI runs on the exact commit. Work lands only on a person's yes.

  6. Signed releasecanary first

    A version tag builds the service's image, signs it and attaches what went into it. A fleet repository rolls it out to one box first and to the rest once that box reports healthy. Nobody logs in to a server.

The method makes everything after the first storm boring, so the thinking is the only hard part.

A worked example: the book club

mcl-bookclub is a whole service built this way, with the code public. A club initiates, members register, books are procured, readings start and finish, a party gets planned. It is four parts, and every boundary between them is a test, not a promise.

does

The commands

Nine capabilities, one folder each, from register_member to plan_party, and a rule that reacts when a member registers.

records

The tables

Clubs, members, books and readings, each filled from the events, one small projection per event.

answers

The questions

A book, a member or a reading by its id, and the readings of one member.

on the mesh

The door

It answers calls for a club by its id. Three small desks publish facts on the mesh: a member registered, a book procured, a book retired. The tables and the questions never touch the mesh.

What Macula promises

no open door

No machine opens a port

Every node connects out to a station; a station never dials in. There is nothing on your box for a scan from the internet to find.

identity built in

No login system to write

Every service and every caller carries its own key, and your realm's admin admits it with a certificate. Your service checks who is calling against your realm instead of keeping its own passwords.

closed by default

Nobody is served until you say so

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

No one can speak for your service

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

Post-quantum identities

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

End-to-end encrypted by default

Every call is sealed to the receiver's own key, so the stations in between carry only ciphertext. A call in the clear is refused unless the service has explicitly allowed it.

Where it fits

Developers and small firms who want to offer a service without renting a cloud for it, and who want code the next person can read. A single service for one club, one trade or one cooperative is the natural start.

Solo developersSmall software firmsIntegrators building for SME clientsCooperatives and associationsServices on owned hardwareTeaching event sourcing

Build it with us

Makers bring the ideas, the machines and the customers; we bring the mesh software, Martha and the corpus, and each maker's service gets a place in the community realm or a realm of its own under a Macula licence. We are looking for partners in three roles.

build a service

Makers

You have a service in mind for a club, a trade or a cooperative. Build it on the mesh with us, from the first storm to the first release, and help us find where the method is still hard.

build for clients

Integrators and small firms

You build software for small and mid-size clients. Run a crew on your own machines with the method, and deliver services that your clients run on their own boxes.

teach it

Schools and trainers

You teach software design. Use the book club and the corpus to teach event storming, vertical slices and event sourcing on code that runs.

In one sentence

Your service on your own box, reachable by name from anywhere, with no open port and no login system to write.for developers

One method from the first storm to a signed release, so every service you build has the same readable shape.for small firms and integrators

Services that run on their makers' own machines, not on a rented cloud.for funders and policy makers