About OpenPasture

Built in Raymond. Built from the inside.

OpenPasture was built by a rancher, tested on real operations, and designed to give you back the part of this work you actually showed up for.

The problem

I run a mixed operation in Raymond, California. Five years in, mid-size herd, and at some point I stopped feeling like I was running one ranch and started feeling like I was running twelve businesses at once.

Feed vendors. Health records. Pasture rotations. Sale timing. Treatment logs. Every piece of the operation lived somewhere different — a notebook, a spreadsheet, a text thread, memory. And I was completely at the mercy of all of it. When something slipped, I was the last to know. When a vendor called, I was scrambling. When it was time to sell, I was guessing.

That's not ranching. That's just surviving the week.

Why I built this

I built OpenPasture because I couldn't find anything that actually fit the way a ranch operates day to day. Everything I tried was either built for a desk job or built for an operation ten times my size.

So I built what I needed — a simple morning read on what actually needs attention today. The animal that needs watching. The pasture that's ready to move. The record that'll matter when a buyer or inspector shows up. Two minutes instead of an hour of cross-checking things I should already know.

I built it myself. No outside team, no agency, no tech co-founder. Just five years of running a real operation and knowing exactly where the gaps were.

How it's built

OpenPasture is being validated on my own operation in Raymond and with a small number of nearby ranches in a guided research preview. Real feedback from real working days shapes the product — but we are early, and not everything works yet.

It's designed to work the way ranchers actually work: voice notes in the field, plain language instead of dashboards. Offline support for areas without signal is on the roadmap — coming soon.

Note: Any product examples or demonstrations shown on public pages are illustrative and may not reflect any specific operation's records. for what is and is not available today.

Where this is going

In five years, I want every rancher using OpenPasture to have their time back. Not time spent on reports, not time spent chasing down records. Time spent on the actual work — the animals, the land, the reason any of us got into this in the first place.

This business is hard enough. The tools you use shouldn't make it harder.

Who this is for

OpenPasture is built for operators who are serious about their ranch but don't have time for complicated software. If you're managing records across too many places, making calls from memory, and going to bed wondering what you missed — this was built for you.

Alexandria Dames, founder of OpenPasture, on the ranch road at sundown

We are talking with a small number of operators about how they run the day. If that is you, tell us how you work.

— Alexandria

Founder · Raymond, CA