Radius.to Tests Free Local Groups Capped at 100 Members

Radius.to describes itself as a modern Meetup alternative for local groups, events and activities, focused on helping people with shared interests find each other across cities worldwide Radius.

The site says users can browse hundreds of groups in cities worldwide Radius.

One listing is a London Run Club event called "Saturday Morning 10K, Hyde Park," set for Saturday, Apr 12 at 8:00 AM in London, UK, with 23 going Radius.

On pricing, Radius says its Meetup-alternative tier is free for groups up to 100 members with no organiser fee Radius Meetup-alternative page. The same page says it offers groups, events and RSVPs with no organiser fee Radius Meetup-alternative page. The company says separately that joining groups and attending events is always free Radius FAQ.

The broader context here is how group platforms handle cost and responsibility. The stated model removes money from both sides. Organisers pay no fee to run groups, events and RSVPs. Members pay nothing to join or attend. That lowers the barrier to starting a group. It does not lower the day-to-day work of running one, which includes scheduling, venue coordination, uneven attendance and moderation. For technology professionals weighing community tools, that gap between cheap creation and steady operation is central.

In my view, the 100-member free limit is doing structural work. One hundred is large enough to give a recurring local activity a reliable pool of possible attendees, and small enough that social accountability still works. Small groups can coordinate with simple norms and direct messages. Larger audiences tend to need formal roles, permissions and enforcement steps. By capping free groups at that size, Radius keeps groups where informal coordination often works, and avoids the overhead of managing at audience scale.

Looking at what this means for operators and engineers, the tests are practical. Discovery has to solve the cold-start problem, meaning having enough relevant groups in each city from the beginning, without filling results with low-quality listings. Search, categories and recommendations have to match what a person wants with location and time. RSVP counts have to line up with who actually shows up, which depends on reminders, calendar links, waitlists and handling no-shows. Notifications have to reach members reliably without causing them to mute the channel. Identity, trust and abuse controls have to work for a brand-new group and keep working as it nears the member cap.

Looking at what this means for adoption, the Hyde Park example shows the intended unit of use. A 10K run at 8:00 AM on a Saturday selects for commitment. A count of 23 going describes a group that can gather, get briefed and move together. That pattern fits runs, workshops and other local activities where repeat attendance matters more than total signups. Free entry helps bring people in at first. Retention comes from regular schedule, reliability and the quality of the in-person experience.

Worth flagging is the long-term question common to free community tools, which is sustainability without organiser or member fees. The verified material does not state a revenue model beyond the free terms. From an engineering view, the key variables are hosting and delivery cost per active group, support load per organiser, and the work needed to keep discovery useful as the number of groups grows. Those pressures rise with scale. How they are handled will shape feature depth, reliability and the limits of the free tier over time.

The optimistic case is straightforward. When coordination gets easier, more local gatherings happen as planned. Organisers can try a run club, a study group or a technical meetup without budget approval. Members can join without paying. Software does not create the desire to meet. It lowers friction enough that existing desire can turn into a specific place and time.