Mutual aid tools that belong to your community.

Your tools. Your data. Your rules.

From the first request to distribution day, run your mutual aid drive with one toolkit — on your own devices.

Works offline No company in the middle Speaks your neighbors' languages Free & open source
The whole workflow

Everything a distribution needs.

Follow a request from the first conversation to distribution day. Explore the toolkit your team will actually use.

A request starts with a neighbor.

Record what a household needs, from groceries to social services, in the language they speak. A guided form keeps each step simple.

01 / 06
Intake form at step 2 of 4, with Groceries and Soap & Shower selected for a sample household.
Select the items a neighbor needs.View full screenshot ↗

Turn open requests into a call list.

Find households by need or language, then prepare messages in the language each neighbor understands.

02 / 06
Outreach screen showing a list of sample households with open requests and a pipeline from requests to delivery.
Build a list from open requests, ready for follow-up.View full screenshot ↗

Find a neighbor. Hand things over.

Look someone up by the last four digits of their phone, check them in, and record what they received.

03 / 06
Check-in screen for the fictional household Ana, showing open groceries and soap requests.
Before: Ana has groceries and soap waiting.View full screenshot ↗

Keep distribution day on track.

Schedule your next event, see appointments and volunteer coverage, and account for no-shows when the day is over.

04 / 06
Distribution screen with a sample event at Maple Street Community Garden and a checklist of scheduling, shifts, appointments and check-in.
One place for the next distro and everything it needs.View full screenshot ↗

See what your community needs.

Open requests and the most-needed items, ranked. Use the real picture of your community's needs to plan the next drive.

05 / 06
Dashboard with sample request counts and ranked open requests for groceries, diapers, school supplies, clothing and soap.
Requests become a clear picture of what to prepare.View full screenshot ↗

Give volunteers the access they need.

Create a QR invite and choose which tools volunteers can use. Manage each person's access as your team changes.

06 / 06
Volunteer invite form named Saturday volunteers, with controls for tool permissions, expiry and number of uses.
Set up an invite for the next group of volunteers.View full screenshot ↗

Real toolkit screens, shown with fictional sample data. Choose a feature to take a look around.

Get started

Up and running in three steps.

No accounts to create, no server to stand up. Open the app and go.

1

Create your org

Set your name, colors and logo. It lives inside your own copy of the data — no config files, nothing to rebuild. You become the first admin.

2

Invite your team

Hand out a QR code. A volunteer scans it, types their name, and they're in — ready to work. You never need anyone's technical details. See the QR onboarding guide →

3

Run your drive

Intake, outreach, check-in. Everything syncs to your team's devices. When the day is done, all of it is still yours.

Launch the toolkit →
White-label

A shell you make yours.

The name on the door, the colors, the logo, and the catalog of what you actually hand out — you set them once, and they travel to every device on your team. A food pantry, a clothing drive and a tenants' union all need different things; the toolkit bends to fit.

Fork it, rename it, ship your own copy. It's a tool, not a service — so it's genuinely yours.

  • Name & brand — your community's name, colors and logo, set live when you start.
  • Your catalog — the goods, services and languages you actually work with.
  • Your words — plain, dependency-free view files you can relabel.
  • Your infrastructure — run your own sync relay, or none at all.
Local-first

Your data lives with you.

There's no server holding your community's information. Updates sync straight between the devices your team has put on the roster — so there's no company to ask permission from, and no one else's database sitting in the middle.

And because it's local-first, it keeps working when the internet doesn't. Out at a distribution with no signal? Everything still runs; it catches up when you're back.

  • No middleman — no account, no platform, no terms of service.
  • Offline-first — the whole app runs on your device.
  • You hold the keys — access is decided by your team, on every device.
  • Open source — read the code, verify the build, change what you like.

Start your own.

It takes about a minute, and nothing you do leaves your device until you invite someone.