Case Study: Community SaaS Platform
A multi tenant community platform I built in Brisbane for local councils, community groups, and neighbourhood associations. Events and RSVPs, a business directory, a buy, sell and swap marketplace, and secure messaging on Matrix, all in one package, running under their own branding.
Overview
Most community groups I deal with (Lions clubs, P&C associations, neighbourhood watch groups, rural fire brigades) run their communication across three or four different platforms that don't talk to each other. Facebook for announcements, a separate spreadsheet for the directory, email chains for RSVPs, and WhatsApp for the daily chat that nobody outside can see.
I built LocalBuddy to consolidate those into a single platform that runs under the community's own branding. The council or group gets their own subdomain, their own colour scheme, and their own data. The underlying infrastructure is shared across tenants, which is where the (re)-usability of the platform keeps the cost down. They look independent even though they aren't running their own server.
The four modules cover the four things communities actually need: knowing what's on this weekend, finding a local tradie, selling a second hand lawnmower, and talking to each other without the feed algorithm deciding who sees what.
"Nextdoor exists. Facebook Groups exist. Neither is owned by the community, neither runs on Australian servers, and neither lets the group admin control what data is collected and where it goes. That is the gap."
Core Modules
I designed each module for how a community group actually works. No feature chasing, no "engagement metrics", just the tools that reduce the admin burden of running a local organisation.
Post events, collect RSVPs, send reminders. The calendar view shows what's on this week and this month. RSVP confirmation emails go out automatically. The admin sees a live headcount. No spreadsheet required.
The local business directory with categories, search, contact details, and community reviews. Businesses can claim their listing. The directory admin approves new listings and removes stale ones. Replaces the printed community guide.
A neighbourhood marketplace for second hand goods, free items, and services. Listings expire automatically. Photo uploads supported. Not Facebook Marketplace, but it's yours: no algorithm, no data mining, no ads.
Group and private messaging runs on the Matrix protocol. Open standard, federated, encrypted end to end. The community's messages are stored on Australian infrastructure I manage. No vendor lock in; the protocol is publicly documented.
Each community gets their own subdomain and their own colour scheme. The Dayboro Lions Club looks like the Dayboro Lions Club, not "powered by LocalBuddy with a logo in the corner." Branding is configurable from the tenant admin panel.
Tenant admins can see how the platform is being used: active members, event attendance trends, directory search terms, marketplace listing activity. The data belongs to the tenant and stays in Australia, on infrastructure I run.
Pricing
Community groups don't have IT budgets, so I priced the tiers around that. The free tier costs nothing and does the real job. Councils and larger organisations that need SLAs, custom domains, and support have a path to paid tiers that reflects the value, whilst the free tier stays functional rather than a crippled demo.
Clubs, sporting groups, neighbourhood associations
Active community groups, RSLs, Lions clubs
Business chambers, regional groups, large associations
Local councils, regional development boards
Under the Hood
LocalBuddy runs on a multi tenant architecture where all tenants share the same underlying infrastructure but are isolated at the data layer. A community in Dayboro can't see the data of a community in Toowoomba. As the platform admin, I can see all tenants for operational purposes.
The landing page at localbuddy.au is a static HTML site I wrote. No WordPress, no framework. It loads fast, it doesn't break, and it doesn't need updating every time a WordPress plugin releases a security patch. I keep the platform application on separate infrastructure behind the scenes.
Matrix for messaging was my deliberate choice. The Matrix protocol is open, federated, and well documented. If LocalBuddy ever shut down or a community wanted to host their messaging themselves, they could export their room history and move to any Matrix compatible server. That isn't possible with WhatsApp or Facebook Messenger.
Each tenant has their own database schema prefix. Events, directory listings, marketplace items, and member records are scoped per tenant. Cross-tenant queries are not possible from tenant-level code.
Paid tiers get their own subdomain or custom domain. The platform provisions SSL automatically. From the community's perspective, it's their website.
I store all data in Australia. No content moderation AI, no advertising targeting, no data sharing with third parties. The community owns their member data.
LocalBuddy is in active development. The platform architecture and landing page are built. The deployment model and tenant provisioning system are functional. The first community tenants are the Dayboro Lions Club directory (which runs on the same infrastructure as dayboro.au) and a pilot group in the Moreton Bay region. I haven't opened public sign up for new communities without prior contact. That's deliberate while I refine the onboarding process.
Technical Details
If you're managing a community organisation on a mix of Facebook, email chains, and shared Google Docs, I built LocalBuddy for exactly that situation. Get in touch and I'll talk you through whether it fits.