Software that
people can trust.

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.

What we do

Two kinds of work, the same standards for both.

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.

See what we’re building

Consulting we offer

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.

How engagements work

What we’re building: TripBridge

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.

  • No student accounts
  • Server-side moderation
  • Auto-closing trip rooms
  • No phone numbers shared

No personal phone numbers

Teachers and students message inside the trip room, so no one has to share a private number to stay reachable.

Teacher-controlled chat

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.

Temporary field trip rooms

Students join with a trip name and short passcode. The room is time-boxed and closes automatically when the trip ends.

Teacher dashboard listing upcoming field trips
Every trip on one dashboard.
Create-trip dialog with a trip name and dates
Set up a trip room in under a minute.
Moderated group chat with staff and student messages
Moderated group chat you control.
The trip room as a student sees it
The simple view students get.

How a trip works

  1. Create a trip room

    A teacher sets up a room for the trip, picks the chat rules, and gets a short join passcode to share.

  2. Students join with a code

    Students enter the trip name, passcode, and a username. No account, no app install, no phone number.

  3. Chat safely, then it closes

    Staff message and moderate throughout the trip. When it ends, the room becomes read-only and is cleaned up automatically.

Where TripBridge stands today

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.

Read the privacy summary

The student trip room on a phone
Built for the phone in a student’s pocket.

Consulting

Web and mobile applications, the cloud they run on, and the operational work that keeps both healthy.

What we take on

Applications
Web and mobile applications, from a first version through to maintenance
Integrations
APIs, integrations, and the glue between systems you already run
Cloud
Environments on AWS, Google Cloud, and Azure: set one up, move to one, or tidy the one you have
DevOps
CI/CD pipelines, infrastructure as code, and deployments that repeat exactly
Security
Access control, secrets, encryption at rest, and backups that have been restored
Observability
Logs, metrics, and alerts, so a problem is noticed before it is reported
Support
Ongoing support and improvement of existing software

How engagements work

Shape
A scoped project with a fixed deliverable, or a monthly retainer
Agreement
A written agreement before any work starts, with an NDA on request
Ownership
Clear terms on ownership of deliverables, in writing
Who builds it
You work directly with the engineer building your software