Macula Mesh Use Build Macula for… Docs Contact

Macula · office work · All Macula for… pages

With Macula, a team writes one document, one spreadsheet or one slide deck together, each person in a desktop app on their own machine, over the Macula Mesh, with no server holding the document. Every edit travels sealed to the people the host invited by name, and every editor holds a full copy. 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 belongs. The concept is proven in three office apps, and we are looking for partners to take it further.

Without Macula: the office cloud holds every document

To write a document together, most teams put it in Microsoft 365 or Google Workspace. Every letter, every budget and every board deck then lives on the provider's servers, under the provider's terms.

their copy

Your documents sit on someone else's servers

The provider stores every version of every file, and holds the keys that open them. You trust it not to read what it can read.

their account

Lose the account, lose the files

A locked account, an unpaid invoice or a closed tenant cuts a team off from its own work, often all at once.

their price

A subscription per seat, for ever

Writing together costs a monthly fee per person, the provider sets the price, and moving thousands of files away is hard enough that few teams try.

With Macula: the edits travel sealed between the people you invited

Each person opens the document in a desktop app on their own laptop. The app runs a Macula node, which 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 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 firm, a school or a public body can run its own under a Macula licence. The person who shares a document is its host: the host invites colleagues by name, and only they get the key that opens the edits.

Every node connects outward, so no laptop has an open port facing the internet. The edits are sealed under a key only the invited people hold, so the stations in between, and anyone on the mesh who was not invited, carry or receive only ciphertext. Each editor keeps a full copy of the document on their own disk.

The apps

Three open-source office apps by the ArtCraft team, written in Rust and licensed MIT OR Apache-2.0, each built for the mesh with one Macula crate. Credit for the apps goes to their authors; the Macula part is the sharing. See all three in one take in the four-minute demo below.

Three people in two realms, three cities, one document: Eve in Amsterdam, Hana in Helsinki and Ines in Nuremberg editing together over the mesh.

documents

WordCraft

A word processor with the Word workflow people know: the ribbon, styles, tables, track changes, references and mail merge. It reads and writes .docx.

spreadsheets

GridCraft

Spreadsheets and data, a clean-room take on the Excel workflow. No subscription and no licence server.

presentations

DeckCraft

Slide decks with themes, layouts, pictures, tables, charts and transitions. It opens and saves PowerPoint files and presents them full screen.

the sharing

macula-craft-collab

The Macula side: identity, invites, the share's key and the sealed edits. Any app built on the same collaboration seam can use it.

How a share works

  1. 1 · Share

    The host opens a document and shares it. The share gets a fresh random id and its own key, and the host's app hands out that key, to invited people only.

  2. 2 · Invite

    The host invites a colleague by name. The invite is signed by the host and names that one person's machine; nobody else can use it.

  3. 3 · Join

    The colleague's app asks to come in, the host approves, and the colleague receives the document and the key.

  4. 4 · Write together

    Both type at once and see each other's edits within seconds. Every edit is signed by its author and sealed under the share's key.

  5. 5 · Revoke

    The host can revoke a person at any time. From then on, the host refuses that person the share's key.

The sharing crate also lets a host in one realm invite a member of another realm the host trusts, so two organisations can write together, each under its own realm.

The concept is proven

Each of the three apps was run on two machines, over a public station, with a fresh invite each time.

named invite

Only the invited person gets in

In every run the colleague joined through an invite naming their machine, and only after the host approved.

together

Both sides see both edits

Each side saw the other's edits within a few seconds, in the right order, in WordCraft, GridCraft and DeckCraft alike.

a stranger listening

The station sees only ciphertext

A machine that was never invited listened at the station relaying the share. It received every edit, sealed, and none in the clear: not a word of the text and not the document's name.

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 laptop for a scan from the internet to find.

membership

Your realm's admin admits who belongs

Every person and every device carries its own key, and a realm's admin admits it with a certificate and can revoke it. Pick a realm whose rules you trust, or run your own.

sealed content

Sealed end to end, always

A shared document has no clear path at all: an edit that cannot be sealed is not sent, not even when the key is out of reach.

signed edits

No one can edit in your name

Every edit carries its author's signature, and an edit whose author is not the one who sent it is dropped.

post-quantum

Post-quantum identities

Keys and signatures use the new methods chosen to resist future quantum computers, so a signature is not expected to be forgeable by one, even years later.

your copy

Every editor holds a full copy

The document lives on the machines of the people writing it. No station keeps a copy of what it relays, and no provider holds your files.

Where it fits

Teams whose documents should not sit on a foreign provider's servers, and who want to stop paying per seat to write together. A small team or one department is the natural start.

Law and accountancy firmsMedical practicesPublic bodies and townsSchoolsSmall and medium firmsAssociations and boards

Take it further with us

The concept works; turning it into an office suite a firm runs every day needs partners. Partners bring the users, the machines and the support; we bring the mesh software and the sharing crate, and each organisation 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.

put it in front of users

Integrators and IT partners

You run the office tools for your clients. Package the apps with mesh sharing, run a realm and a station or two for them, and support them.

use it first

Firms and public bodies

You want your documents out of a foreign cloud. Be the first team to write its own documents this way, and tell us what is missing.

build the next piece

Developers and app makers

You build editors. Bring sealed, server-free co-editing to your own app with the same crate, the way the three apps above were built.

In one sentence

Write one document together from your own laptops, with no server that holds it or can read it.for teams and their managers

Office apps your clients own, shared over a mesh you can run for them.for integrators and IT partners

An office suite that keeps documents on the machines of the people who write them.for funders and policy makers