About Vetware
A veterinarian, two engineers and a radiologist
Vetware is built inside a working veterinary hospital rather than for one. The vet who runs it is the first person to use everything we make, and the last word on whether it is good enough to sell to anyone else.

Who does what
Four people, and one of them decides what ships
The veterinarian
Dr. Samee Berger
Samee owns and practices at Mountain View Animal Hospital. She is our first customer, our first tester, and the source of most of what we build.
Every product runs in her hospital, on real patients and real staff, before anyone else sees it. If the vet is not happy with it, we do not ship it.
The builders
Gunnar and Chuck
We write the software. Gunnar spent twenty years building software products, most recently leading product teams at Amazon, and now does this full time.
We sit in the building where the problem is, so the distance between "this is broken" and "try this" is a conversation at the end of a shift.
The radiologist
Dr. Kris Brand, DACVR
Kris tunes the imaging AI against real cases, decides what it should and should not flag, and checks every AI report while that feature is in beta.
They are also who answers when a practice asks for a full consult, which is how a board-certified read sits one click from the study you are already looking at.
How it started
One hospital, and a software problem nobody wanted to sell us out of
My wife and I own Mountain View Animal Hospital. She is the veterinarian. I build software products for a living. Every problem the practice hit had the same answer waiting for it: another vendor, another subscription, another login for one more point solution, each one priced as though it were the only thing we bought that year.
So I built the fixes myself. The imaging backup came first, because we were paying thousands a year to store data that costs pennies to keep. Then an AI second opinion on every radiograph, because a solo doctor second-guesses herself and a second set of eyes should not be a phone call. Then the keepsakes, the client surveys, the booking page, the clinical reference. Each one started as a problem in our own building.
None of it was built to be sold. It was built because the alternative was writing another check. That is still the test we apply to everything: would we pay someone else for this, or is it cheaper and better to make it ours and share it with practices in the same position.