Stable Pastures is currently in private pilot. Public sign-ups are coming soon. Request Pilot Access

Security

Built for organizations, not a public bulletin board.

Stable Pastures is designed so operational information stays with the organization it belongs to. Access depends on who you are in that organization. We describe our approach conservatively — no product can promise perfect security.

Organization boundaries

Each organization is separate. People see the operational information they are allowed to see in the organizations they belong to — not a shared public feed of barn or club records.

How access is handled

Organization separation

Operational records belong to an organization. Another organization does not get that data by default.

Role-based access

What a person can see and change depends on their role and the access they have been given.

Authentication

People sign in to reach private operational areas. Public marketing pages do not require an account.

Private operational data

Horse records, people, schedules, finance, and day-to-day work are treated as private to the organization.

Server-side architecture

Application logic runs on the server for operational work. The marketing site does not query organization data.

Files and documents

Documents are handled separately from operational records where that separation is appropriate.

Row Level Security (RLS)

Stable Pastures uses database-level Row Level Security (RLS) so access rules are enforced close to the data itself. That is one layer of protection, not a claim that breaches are impossible or that we hold specific industry certifications.

Explore related areas

Access follows the organization and the role.

Sign in to reach your organization. Marketing pages stay public and separate from operational data.