Why we built River People

A long-term vision for offline river contributions

Paddlers often have the freshest firsthand information while they are where service is weakest. We built a real product first because we want any future partnership to begin with demonstrated care, capability, and commitment.

Published by BentzTech LLC - August 1, 2026

Independent today, collaborative in ambition

River People is not affiliated with, endorsed by, or integrated with American Whitewater. It does not currently write to the National Whitewater Inventory. American Whitewater maintains its own official website and mobile apps. This page describes our aspiration, not an announced partnership.

Why we built the product first

We did not want to approach a respected nonprofit with only a promise that we could build useful technology. We chose to invest the time, solve real paddling workflows, release an app, and learn from actual use.

River People is evidence of that commitment. It lets us demonstrate how offline-aware software, river-section context, community reports, crews, events, messaging, and detailed run records can work together. It also exposes the hard parts: attribution, data freshness, moderation, privacy, conflict resolution, accessibility, and long-term maintenance.

Traction would strengthen that evidence, but adoption alone is not the point. The product should show that our group is willing to listen, maintain what it builds, and do the unglamorous work required to make a community tool dependable.

Why American Whitewater matters to this vision

American Whitewater protects and restores whitewater rivers and improves opportunities to enjoy them safely. Its National Whitewater Inventory is a living public resource shaped by staff, volunteers, Stream Team contributors, clubs, and paddlers sharing firsthand knowledge.

American Whitewater already maintains official mobile apps and an established contribution process. We respect that existing work. If River People ever becomes useful to American Whitewater, we would approach that opportunity as collaboration with its staff, volunteers, current developers, and community - not as a claim on its platform or data.

Our hope is to earn the chance to help strengthen that shared resource, particularly where offline field collection could make responsible contributions easier.

Learn how the inventory is maintained through American Whitewater's Stream Team, and use its official channels for current river contributions.

A future field-to-review workflow

With an authorized integration, a paddler could prepare an update while offline without bypassing the people responsible for the public record:

  1. Capture: choose the exact river reach and document a hazard, access change, gauge relationship, photo, trip report, or proposed correction.
  2. Preserve context: retain the author, coordinates, observation time, flow context, media rights, device record, and whether the information is firsthand.
  3. Hold offline: keep the draft safely on the device while the paddler remains outside service.
  4. Synchronize: reconnect later and transmit through an approved, authenticated interface.
  5. Review: route the proposal into American Whitewater's editorial or Stream Team workflow, including duplicate and conflict handling.
  6. Publish responsibly: let the authorized system of record decide what becomes public while preserving attribution and change history.

The goal is not automatic, unreviewed changes. It is a respectful bridge from firsthand observation to accountable community review.

Principles for any future collaboration

  • American Whitewater governance: AW would define contribution policy, review authority, access, attribution, and what enters the National Whitewater Inventory.
  • Authorized access only: integration would require explicit permission and a supported technical agreement, never harvesting or reverse-engineering AW data.
  • Human review: consequential edits would remain visible, attributable proposals until accepted through the approved workflow.
  • Provenance by default: source, author, observation time, coordinates, units, media rights, and edit history would travel with the contribution.
  • Safety and privacy: the design would protect sensitive locations and personal information without presenting any report or flow as a safety guarantee.
  • Maintainability: documentation, accessibility, testing, support, security, and a sustainable handoff would be part of the product rather than afterthoughts.
  • Community design: staff, current developers, Stream Team editors, local experts, clubs, and paddlers would help shape the workflow.

What River People does today

River People currently operates as an independent whitewater app from BentzTech LLC. Paddlers can explore sections, review configured gauge and hazard context, save favorites, coordinate crews and events, communicate, and record GPS runs with notes, vessels, skills, media, and available flow context.

Its offline-aware behavior and community tools are a foundation we can test and improve. They are not evidence of permission to modify an outside database. Until a partnership exists, American Whitewater information and contributions should continue through American Whitewater's official website, app, and Stream Team process.

An open invitation to talk

If you are an American Whitewater staff member, volunteer, current app contributor, Stream Team editor, affiliate club, or paddler interested in responsible offline contribution workflows, we would welcome a conversation. We are prepared to listen first, document constraints, and begin with a bounded pilot if invited.

Email contact@bentztech.pro and reference the River People collaboration vision.

A real product is the beginning of the conversation

River People is our commitment to learn from paddlers, maintain what we build, and earn trust through useful work.