We build the AI that doesn't leave the building.
Harmonee is an on-prem AI infrastructure company. We build the hardware, the engines, and the operational tooling that let regulated organizations run AI inside their own walls — and own the long-term value of that work.
Most AI tooling was built for a different customer.
The dominant AI products of the last few years were built for companies that operate primarily in the cloud — software-first businesses with permissive data postures and product teams who can ship to production on Tuesday. That's a real customer. It's also a small fraction of the world.
Hospitals, county governments, school districts, tribal nations, regional banks, and manufacturers don't operate that way. The data is sensitive. The audits are regular. The procurement cycle is real. The IT team is small. Cloud-first AI tooling does not fit those constraints — not because the vendors don't care, but because the architecture wasn't designed around them.
We started Harmonee to build the AI infrastructure those organizations should have had from the beginning. On-prem hardware. Local inference. Auditable architecture. Ownership of the institutional knowledge that accumulates inside the system. The right architecture, sized for the rooms our customers actually have.
Built in Southern Oregon. Designed for everywhere.
Our team is based in Klamath Falls, Oregon — a region with deep ties to county government, regional healthcare, tribal nations, and the kind of operational businesses that have been quietly running the country for a long time. Our earliest customers came from this community, and the patterns we learned deploying here are the patterns we're carrying forward.
The hardware ships nationally. The deployment template works in any jurisdiction with the constraints we're built for. The team will grow where the customers grow.
We're explicit about the boundaries.
We are not a clinical decision-support tool. We are not a management consulting firm. We do not lease our hardware. We do not take a percentage of the value the system generates. We do not claim training rights on the data that runs through our customers' units. We do not build features that require an outbound connection.
Each of those boundaries was a deliberate choice. The set of things we've said no to defines the company at least as much as the set of things we ship.
Operators Who've Done It. Builders Running Hot.
Marcio Nunes
Zach Brown
Jason Aarstad
Engineering
Three divisions, each led by the engineer who owns the practice.
Tony Jewell
Leads research and development, the engine work behind Harmonee's on-premises architecture: model routing, organizational memory, and the systems that let the platform run with no outbound path. Sets the technical direction for what the product becomes next.
Oluwaseun Daniel Fowotade
Tesahe Tunson
Kayleb Cook
Chris Grende
Leads forward deployment: getting Harmonee units installed, integrated and running inside a customer's own walls. Built the systems behind the county government deployments, where units went from contract to live in under three weeks. Owns the field practice that turns an on-premises architecture into something a department uses daily.
Vlad Yoltukhivskyi
Artur Yoltukhivskyi
Benjamin Whitman
Works across the embedded systems and internal technology Harmonee's hardware depends on, from the software running on the unit itself to the infrastructure the team operates on. Has been with the company since the beginning.
Growth, Brand and Communications
The company's outward voice. Brand, communications, content and the customer stories that carry the work outside the building.
Nalicia Dubose
Cassady Brown
Issey Tanimura
Addison Brown
Jack Fleming-Jones
Erin Atkinson
Advisors and Support
Advisors who work alongside the company on client partnerships and institutional relationships. Not an operating division.
Kyle Cochran
Andrew Stork
Walk the dashboard before you commit.
Production demo at klamathlounge.com — request the password and we'll send it.