Available now
Discover publicly. Operate privately.
Public camp profiles can help people understand a camp. Member workspaces are a different boundary, with authenticated access and role-aware operating surfaces.
See public campsFull systemFeature 05 / 09
Collective logistics
Run camp without running everyone down.
A permissioned workspace for the real work behind camp: projects, people, shifts, inventory, logistics, communication, and shared context.
Explore the camp directory
Stokd study / Camp OS
Current stateFoundation in place
Public camp discovery exists. Operational workspaces are separate, permissioned surfaces whose available modules depend on the camp, membership, and role.
05.0 / The premise
The magic is visible. The labor often is not. Camp OS is for the build calendar, the missing adapter, the meal shift, the inventory check, and all the quiet coordination that makes a shared experience possible.
Foundation in place
Give the work a home.
Planning, projects, boards, chat, shifts, inventory, logistics, and finance routes form the operating foundation. What a member can see or change depends on the workspace and permissions.
Foundation in place
Let agents carry context, not authority.
The long-term agent layer can surface missing information, summarize decisions, and prepare next steps. Sensitive actions should remain bounded by the same permissions as the people using the workspace.
05.4 / Product boundaries
Built around what it should not fake.
- P1Public identity and private operations stay separate.
- P2Roles shape access.
- P3Shared memory needs provenance.
- P4Agents do not invent authority.
Read before relying
Camp records and workspace access vary. A public profile does not imply recruitment, membership, operational readiness, or endorsement by an event organizer.
Next move
Make room for the people doing the work.
The best operations software fades into the background and gives a crew more time to build the thing they came for.
Explore the camp directory