[ ˈɑː.ɾa ] · noun, from the Latin
An altar. A raised place set apart, where ordinary work becomes worth doing well by the attention given to it.
A refuge. Shelter from what wears people down: noise, churn, the demand to be efficient about everything.
A sanctuary. A protected ground. A place where the people in it agree to belong, and to be accountable to one another for the belonging.
In ancient times, an Ara was a protected space. A point of connection between the earth and the divine. We chose this name because a community’s digital home should feel like a sanctuary.
When people hear “project management,” they recoil. They imagine Gantt charts, nagging bosses, and soulless efficiency metrics. They worry that tracking their community’s work will quietly suck the soul out of it.
We understand the instinct. Most software in this category was built for offices that treat their people like resources, and the language has rotted accordingly. So communities try the opposite: keep things informal, trust the goodwill of whoever shows up.
But informality has its own cost. Without a shape, the work falls on whoever happens to care most. The same three people end up doing the dishes. Tools go missing because nobody was supposed to track them. Decisions made in the kitchen are forgotten by Tuesday. What looks like a refusal of structure is usually just structure that wasn’t said out loud, and structure left unsaid is rarely fair.
ARA is built on a small paradox. Good organisation makes it feel like there is less management. Done right, the tool recedes. What you notice instead is that things happen, on time, by people who said they’d do them, and that you have a little more space in your week.
When a wheel tells you it’s your week to cook, the message is impersonal. Nobody had to ask. Nobody had to remind you. The chore goes round, and the friendship survives.
It is quietly joyful to know exactly where the tools are, who borrowed the truck, what the council decided last spring. Competence reduces anxiety. The community feels like a place that knows itself.
When the Library, the Shed, and the Ledger hold what the community knows, no single person has to be its memory. New villagers can read what’s been done and why. Those who leave still leave something behind. The place keeps its shape across the people who pass through it.
The words a tool gives you are the shape it leaves on what you do. Corporate software speaks in tickets and queues and sprints, and over time the work begins to feel like that: a thing to be processed.
We chose different words. The kind that pre-date the office and might outlast it. A way of remembering what the work is for.
We don’t say “Workspace”
We tend a Sanctuary.
We don’t say “Project”
We grow a Garden.
We don’t say “Task”
We plant a Seed.
We don’t say “Backlog”
We honour Dormancy.
We don’t say “Meeting”
We hold a Gathering.
We don’t say “Doc”
We open a Scroll.
We don’t say “Manager”
We name Architects & Caretakers.
We don’t say “User”
We are Villagers.
Naming is a form of commitment. It says: this is the kind of place we mean to be.
For a longer look at where these patterns come from, read the regenerative roots.
Most software is designed for the next quarter. ARA is designed for the next thirty years.
The communities we build for don’t move on sprint cycles. A garden takes years to mature. Trust takes longer. The kitchen rota you set up today is the one your grandchildren may inherit, with the names changed.
That is the time horizon we built for. Decisions are recorded as if someone fifty years from now will need to understand them. Tools are catalogued as if they will be repaired and passed on, not replaced and binned. Contributions are remembered, because the strength of a place is partly the slow accumulation of what its people did for it.
There is no streak counter. No daily badge. No notification arms race trying to convert your attention into our growth chart. The tool gets out of the way. The community is the point.
We chose not to be a platform.
Platforms grow by flattening the people on them into interchangeable parts. ARA does the opposite. Every sanctuary keeps its own shape, its own pace, its own language for itself. Two ecovillages, three co-ops, a land trust, and a maker’s collective can all use ARA, and none of them will look the same once they’ve made it home.
That choice costs us something commercially. We can’t promise venture-scale growth, because we aren’t trying to capture markets. We’re trying to be useful to a particular kind of place, in a particular way, for a long time.
If your community is small enough that everyone knows everyone’s mood, ARA is for you. If it’s grown large enough that it has begun to forget how to listen to itself, that is the moment we want to be there.