A Pack is people who share compute.
Your laptop. Your friend's gaming rig. The mini-PC in the closet. A Pack pools them into one private mesh, and a turn runs on whichever machine has room. No datacenter, no broker, no monthly bill.
From install to shared compute
- 01
Install & run
Each machine runs the Maylyn desktop app. First launch provisions a local model and a stable node identity — an ed25519 key in its data folder.
- 02
Create or join
One person starts a Pack and shares an invite link. Everyone else accepts the participation agreement once per machine, and their node enrolls.
- 03
Advertise capacity
Each node tells the Pack what it can spare — CPU, RAM, GPU. Sharing is mutual: joining makes your machine available too.
- 04
Turns find room
Ask Maylyn something and the turn runs on a Pack machine with room, node to node over a signed envelope. No relay in the path.
A Pack turn crosses one hop between people who know each other. Nothing is stored or inspected in between.
No one in the middle
- Direct transport. Nodes exchange signed envelopes over plain HTTP between themselves. No relay server can log, meter, or read the traffic.
- A hub, not a broker. An optional coordination hub handles sign-in and the public directory of open Packs. It never sees a turn or its content.
- Your data stays put. Files, memories, and history live on your machine, encrypted at rest. A borrowed node runs the model, not your life.
The participation agreement
Before your machine joins a Pack you read and accept a short, plain-language agreement — once per machine. In brief:
- mutual
- Sharing goes both ways. Joining a Pack makes your spare capacity available to it, not just the other way around.
- both sides
- You're responsible for what you run on other people's machines, and for what runs on yours.
- not a party
- EchoBark isn't a partner, agent, or party to what members do. No warranty; liability between members is capped.
- rogue member
- If someone misbehaves, the other members and owners aren't bound by or liable for it. They can be removed immediately.
The full text ships in the app and the CLI, and is served at /mesh/terms/text. It is not legal advice.
Standalone
Just you. Run Maylyn locally with no Pack at all — the default.
Client of a hub
Your app signs in through a coordination hub, sees the directory of public Packs, and can request to join.
Hub
maylyn hub runs identity and the public directory for a community. It brokers no compute and runs no model.
The guardrails don't move
Approval gate travels
A turn on a borrowed node still can't touch the filesystem, run a shell, or hit a server without an explicit yes from a live approver.
Sandbox on the executor
Tools run inside the sandbox of the machine that executes them. Forbidden and destructive patterns are refused in code, not by prompt.
Signed, not trusted
Every envelope between nodes is signed by the sender's node key. A node only accepts work from Packs it has enrolled in.
Start with the people you trust.
Install Maylyn, start a Pack, send a couple of invites. Your compute, pooled.