For hiking, running and riding groups
Find the plan that fits and the community you’ll go back out with.
A hike, a run or a ride, with the pace, distance, route, start and end stated up front. Join the people who are actually going.
Members-only by design — every screen sits behind a verified account. No logged-out browsing, no public feeds.
Not another meetup app.
Event platforms organise people around a date and a join count. Outdoor groups fail around everything else: pace mismatch, dropped riders, unclear routes, kit that doesn’t match the terrain.
| Meetup / events app | Goaty |
|---|---|
| The atomic unit is an event — title, date, join count | The atomic unit is a plan — organiser details, options, map, date |
| Success is the event filling up | Success is the community completing the route together — and coming back |
| The host is a remote event organiser | The organiser leads the group on terrain and sets this week’s details |
| “Who’s in?” | “Which option am I doing — 10k or 5k, this pace or that — and what is the route?” |
| Comments are social | Comments and chat follow visibility — coordination first, no algorithmic feed |
| Recurrence is a copied calendar entry | Recurrence is a community rhythm with the same organiser-defined details |
| After the event, the product is idle | After the plan: posts, recaps, activity — and the next date is the default |
Ready to see it from the inside? Sign in.
Built for what actually breaks on the trail.
One plan, several ways to do it
Two distances, two paces — one plan. The organiser sets 1–4 options instead of splitting the group into parallel events.
The route lives on the plan card
Line, points and meetpoint stated up front — never a link buried in chat scrollback.
Start and end on the map
Point-to-point days account for where the ride finishes. No seat maths, no stranded runners.
One card replaces the group chat
Who’s in for 10k vs 5k, the route, the kit and the headcount — in one place, before you commit.
Community, not strangers-of-the-week
Followers and repeating series are the retention unit. The same people, out again — a filled one-off is a side effect.
Conditions change, the community doesn’t
Ice, mud, wind, closures: organisers postpone and keep the date alive, instead of only cancelling.
Trail-sized groups
A 25-person meetup is a liability on a ridge. Capacity is a terrain and safety constraint the organiser sets when it matters.
A home between plans
The community’s posts, recaps and activity live in one place — no algorithm decides what you see.
One plan holds everything.
A community keeps a rhythm (a series) or leads a one-off. Either way, what participants join is a plan — the organiser’s details, options and map under one date.
The organiser’s brief
Details stated up front: meet and depart times, kit, the extra question — the plan’s contract is organiser-defined.
1–4 options
10k or 5k, this pace or that — same start and end, so mixed abilities stay in one community.
The route
One map per plan: points via search or markers, an optional meetpoint, a trail line. No GPX imports, no downloads.
Participation and rhythm
One person, one option. Repeat plans are a series that generates them — one follow row powers belonging and reading.
The social layer never replaces the plan — it keeps the community alive between dates. Sign in to see it.
Questions people actually ask.
Do I need an account to see anything?
Yes — Goaty is members-only at the front door. Sign in with an email link or a one-time code and verify your address; only then can you open plans, communities or profiles. There is no logged-out browsing and no public feed.
Is this a trail catalogue like AllTrails or Komoot?
No. Routes are organiser-set context on a plan — points, an optional meetpoint and a trail line. There is no public route library, no GPX import or download, and no recorded workouts or GPS tracking.
How many people can join a plan?
As many as the organisers allow — one-person and one-on-one plans are valid. When terrain demands it, the organiser sets a capacity as a safety constraint; there is no platform default limit.
What does "private community" mean here?
A followers-only club with a public front door. The community card is listed in the directory so you can find and request to follow it — but its plans are only visible to accepted followers.
Is there an algorithmic feed?
No. Home is the profiles you follow plus one’s own content, alongside discovery of communities, plans and people. Suggestions are never contact- or graph-derived.
Does it work on the web?
Fully — signed-in users get web parity including comments and community chat. There is no native push on the web by design; email lifecycle notices and in-app notifications carry the load.
Ready? Sign in — verification takes an email.