Designed, built, and deployed in the United States.

guideOS was designed and developed by two U.S. software engineers who love to fly fish and wanted a better operating system for guide businesses.

The core platform, software components, and intellectual property are founder-owned. The product direction, engineering choices, and deployed software remain close to the people responsible for them.

The platform messaging and product direction are aligned around a simple point: guideOS is built and hosted in the United States, with product decisions made by the same founders building the software.

That matters for teams who care about ownership, continuity, and knowing who is actually responsible for the platform that runs bookings, payments, and client operations.

guideOS is not a thin skin over generic booking software. The workflows are being custom-developed around guide operations: scheduling, public guide pages, client records, waivers, payments, launch prep, and post-trip follow-up.

The aim is not to resell a bundle of disconnected SaaS tools. The aim is to build one coherent system that fits how professional guides actually work.

AI has been used as a support tool inside the engineering process, not as a substitute for product ownership or final technical judgment.

Within guideOS, that support has been intentionally limited to three practical areas that help the founders move faster without giving up control of the product.

Guides do not need vague software ownership, diffuse accountability, or a platform that nobody can clearly explain. They need software that is understandable, responsive, and aligned with the realities of the business.

guideOS is taking the position that product ownership, hosting clarity, and engineering accountability are part of the value proposition, not background details that should be hidden from the customer.