Handing Shramdan to the community that built it with us

We started Shramdan with a plan to let go of it. That sounds like a contradiction until you've watched a community outgrow the people who seeded it — which is exactly what we were hoping for.

Build it to be given away

Designing for handover changes your decisions from day one. You document differently. You pick tools people can actually run without you. You resist the urge to make yourself necessary.

The Sanskrit shramdan means a donation of labour — work given freely for the common good. A tool for that has to be ownable by the people doing the work, not rented from us forever.

The practical shape of letting go

Handover isn't an event; it's a slope. We moved from doing, to doing-alongside, to advising, to watching. Each step we removed a dependency on YantraCore and added one the community controlled.

We're not all the way there yet. But the direction is set, and the destination — fully community-owned and run — is the whole reason we built it.