Equestrian team collaboration — roles done right

Four roles per horse, enforced server-side

Horsies has four built-in roles you can assign per horse: Owner, Rider, Student and Viewer. Crucially, role-based access is enforced server-side — not just hidden in the UI. A Student really cannot read health or expense data, even with a direct API call. That matters for trainer–owner–vet relationships where information should be shared selectively.

• Owner — full control, including ownership transfer and billing.
• Rider — full edit on health, calendar, expenses, tack and competition data.
• Student — limited access (no health, no expenses) for lesson clients and pupils.
• Viewer — read-only access for vets, insurers, prospective buyers.

Sharing is always free

You only pay for the horses you own. Inviting your trainer, groom, vet or barn manager as a Rider, Student or Viewer is always free, no matter how many people you bring on. That keeps the maths simple and means there is no penalty for involving the right people in your horse's care.

Real-time sync across every device

When your groom logs a temperature reading at 7am, you see it in the dashboard before your morning coffee. Horsies syncs in real time across phone, tablet and desktop — no refreshing, no waiting, no version conflicts.

Privacy controls you actually need

Some entries should not be shared with the whole team. Horsies lets you mark individual diary entries, expense records and tack items as private — they stay visible to owners only and are hidden from shared users. Combined with role-based access, you can share what helps and keep what is personal.

• Private diary entries, expense records and tack items.
• Transparent expense visibility for the rest of the team — see who logged what.
• Ownership transfer with full or partial history handover.
• Original owner retains a read-only archive after a transfer.