Why we built this

Six tools, six logins, six exports, and no answer to the question every organizer actually has: what is my relationship with this person? The CRM knows they gave. The events tool knows they came. Neither knows the other, and the volunteer holding both tabs open is the integration.

This is not a market failure that a better product category will fix. Movement tools are fragmented because the people who need them cannot pay, so each tool is built for whoever can — the professionalised campaign, the well-funded advocacy shop — and sold down-market at a price that assumes a budget line.

So Coram gives the whole stack away at the bottom of the market and takes a percentage of money that moves through it. A group with no budget pays nothing and gets everything. A group raising real money pays one percent. A bail fund pays nothing at any size, permanently, because taking a cut of somebody's bail is not a business we are willing to be in.

The other half is what we refuse to store. Organizing data is dangerous data. A list of who attended, who gave, who is on which committee, and what an organizer privately thinks of them is a map of a movement, and it is exactly what gets subpoenaed. So the notes are encrypted with a key we never receive. The check-in is a boolean, not a location. The audit log records that someone read a record type, never what it said. The burn switch destroys a workspace in under a minute with no backup to restore from.

None of that is a policy page. It is the schema. Every one of those decisions is something you could verify by reading a migration, which is why we publish audits instead of promises.