Skip to main content
Yosemite Crew
Star★Get started
Developer portalComing soon

Fromideatotheclinic,in an afternoon.

Start with the open-source codebase and the authenticated, read-only developer API. Inspect organizations, usage and appointments today, then follow the public roadmap as write APIs and marketplace distribution are built.

zsh
$ git clone https://github.com/YosemiteCrew/Yosemite-Crew.git
$ cd Yosemite-Crew
$ pnpm install --frozen-lockfile
$ pnpm --filter frontend run dev
→ open http://localhost:3000/docs
GET /v1/developer/organizations200 OK
[{
  "id": "org_demo",
  "name": "Demo Practice"
}]
AGPL-3.0
Every line, public
The user is changing

For thirty years, good design meant hiding the machinery from a tired human. Soon most of the things using your software won't be people at all, and a machine wants the opposite: the structure naked, the fields exposed, the meaning spelled out. We built a warm face for the human and a clean, exposed spine for the machine.

Authenticated developer API

Read the data plane that exists today.

Create an API key in the developer portal and send it as a Bearer token. Organization and usage discovery are available directly; appointment reads also require the documented scope, practice header and a current practice membership.

GET /v1/developer/organizations
GET /v1/developer/usage
GET /v1/developer/appointments
bundle.json
{
  "resourceType": "Bundle",
  "type": "searchset",
  "total": 3,
  "entry": [
    { "code": "rabies-vax",
      "validYears": 3,
      "authority": "EU" },
    { "code": "rabies-vax",
      "validYears": 1,
      "authority": "US" }
  ]
}
Speaks the language of health data

FHIR-native, all the way down.

Records are not trapped in a shape only we understand. Animals, visits, labs and medications are modelled as FHIR resources, the same standard human health systems run on, so your integrations read clean, typed data instead of reverse-engineering a private format. Interoperability is the default, not a paid add-on.

Patient
Encounter
Observation
MedicationRequest
DiagnosticReport
Immunization
AI Scribe
Turns the consult into a SOAP note
Preview
Triage Agent
Sorts the inbox before the vet reads it
Preview
Voice Reminders
Calls pet parents about overdue vaccines
Preview
Your plugin here
Planned marketplace listing
Marketplace preview

Build now. Distribute it yourself.

The model is the one WordPress proved: build against the API, and every clinic running Yosemite Crew is a clinic that can run your work. The API and the FHIR layer are here today and the whole platform is open source, so you can build and self-host against a real practice now. The marketplace that turns that into one-click distribution is not built yet, and until it is, installing a plugin means deploying it yourself.

Open the developer portal Follow the capability roadmap
The economics

Bring your own AI. Deploy it directly. Choose your own terms.

Bring your preferred AI client and its provider credentials, then authenticate that client separately with a Yosemite API key. Direct deployment works today; marketplace distribution and payments remain planned work.

Plannedmarketplace
cut
Commercial terms are not live yet.
Marketplace payments and distribution are planned capabilities. Today, developers arrange deployment and commercial terms directly with each practice.
What the developer keeps on every sale
App stores & SaaS platforms70–85%
they take 15–30%
Planned Yosemite Crew marketplaceRoadmap
terms to be confirmed
01
Bring your own model
Use Claude, Codex or another client to call Yosemite Crew with a Yosemite API key. Your model-provider subscription is separate from Yosemite authentication.
02
Deploy practice by practice
Build against the available APIs and deploy directly for each practice while marketplace distribution remains on the roadmap.
03
Choose your terms
Arrange deployment and commercial terms directly with each practice until marketplace payments are designed and shipped.
Why it's open

Read every line. Change any of it. Leave with all of it.

Anyone can say they put you first, and because the words cost nothing, they prove nothing. The only way to prove you won't trap someone is to make trapping them impossible. So the whole thing is AGPL-3.0, every record exports, and you can fork it and walk. That costs us the lock-in every investor wanted us to keep, which is exactly why it's worth believing.

The whole repo
Frontend, backend and mobile, all public, all readable.
FHIR standard
Built on the health-data standard, not a private schema you'd have to reverse.
Audit trail
If a dose was given, the system can prove it. If it isn't written down, it didn't happen.
A real community
Contributors, a Discord and issues that get answered by people who wrote the code.

Clone it tonight.

Read the source, run it locally in one command, and ship your first plugin to a real clinic before the week is out.