Products we build
We design, build, and run our own software. TripBridge is the first: a chat room a teacher opens for a field trip and closes when the trip ends. It is a web app first, with a native Android app in progress and an iOS app planned.
Moderated on the server, encrypted at rest, deleted on a schedule no one can extend. That is TripBridge™, our first product, and the standard behind everything else we build.
Two kinds of work, the same standards for both.
We design, build, and run our own software. TripBridge is the first: a chat room a teacher opens for a field trip and closes when the trip ends. It is a web app first, with a native Android app in progress and an iOS app planned.
We take on software projects for other organizations: web and mobile applications, APIs and integrations, cloud environments on AWS, Google Cloud, and Azure, and the DevOps, security, and observability work around them. You work directly with the engineer doing the work.
Temporary, moderated field-trip chat rooms for teachers and students. A teacher opens a room for a trip, students join with a short code, everyone stays in touch during the day, and the room closes when the trip ends. No personal phone numbers change hands.
Teachers and students message inside the trip room, so no one has to share a private number to stay reachable.
Staff set the rules: open group chat, read-only announcements, or direct messages only. Students can send direct messages to staff, never to each other. Moderation runs server-side, always.
Students join with a trip name and short passcode. The room is time-boxed and closes automatically when the trip ends.
A teacher sets up a room for the trip, picks the chat rules, and gets a short join passcode to share.
Students enter the trip name, passcode, and a username. No account, no app install, no phone number.
Staff message and moderate throughout the trip. When it ends, the room becomes read-only and is cleaned up automatically.
TripBridge is a web app first: it installs on any phone as a progressive web app, and its home will be tripbridge.chat. A native Android app is in progress and an iOS app is planned. The product is pre-launch. A pilot with teachers comes before general availability.
Student privacy is the design constraint, not a feature. Students join with a username: no account, no phone number. Message content is encrypted while stored, and every trip’s data is deleted within 90 days of the trip ending. The product’s own privacy policy will be published when TripBridge launches.
Web and mobile applications, the cloud they run on, and the operational work that keeps both healthy.