Fifteen modules that already know about each other, because they share one database rather than a nightly export. Each has its own page below. Switch off what you do not use — a disabled module disappears rather than nagging you to upgrade.
A searchable, filterable directory of everyone in your community — with each member deciding, field by field, who can see what.
The admin side of your roll: approvals, suspensions, role changes, bulk group assignment and a clean CSV export.
Experience, education, publications, skills, projects, awards and an address book — the parts of a career an alumni network is actually for.
A moderated community feed with posts, articles, reactions and threaded comments — plus announcements that surface above it.
Full ticketing, not a yes/no RSVP: ticket types, guests, custom registration questions, QR check-in and public event pages.
Member-owned businesses, listed with categories, logos, perks for fellow members and an approval gate before anything goes live.
A referral board where members post roles from their own companies — split-pane browsing, attachments and external apply links.
Mentors publish what they can help with; mentees request. The whole lifecycle — received, sent, ongoing, completed — is tracked.
Plans, packages, purchase and — the part most tools skip — a validity gate that actually closes doors when a membership lapses.
Campaigns with goal meters, anonymous giving, an updates feed and contributor lists — reusing the same payment machinery as everything else.
One payment path shared by events, membership and fundraising — including a genuinely complete offline flow for bank transfer and cheque.
Committee elections with ballots, voter rolls and secret voting — designed as a cryptographic requirement, not a UI state.
Build an audience from your own data, send from your own verified domain, and see what actually landed.
Every admin action on member data, recorded as it happens — who did what, to which record, and when.
Your public pages, your policies and your organisation's identity — editable without touching a deployment.
Permissions, hosting and a shared data model are not features anyone shops for. They are the reason the fifteen modules above behave like one product.
Named grants grouped into roles you define. A screen renders only when the module is enabled for your organisation and the signed-in user holds the grant — otherwise it is not there at all. Whoever created a record can always edit their own, without needing the blanket permission.
One customer, one deployment, one database, one domain. Nginx, PHP-FPM and a Node process, with a queue worker and a scheduler behind them. Runs on your infrastructure or on hosting we arrange with you.
Because the modules share a database, the joins that usually need a nightly sync are simply queries. A donor list knows who is a lapsed member. An event's attendee list knows who is a mentor. Nothing needs reconciling at month end.
Stripe and PayPal adapters, an integrated map view for the directory, and single sign-on for institutions. Ask us where a specific one sits — we will tell you honestly rather than sell you a date.
Ask about a moduleTell us how your organisation runs today and we will show the same flow in Metrolo — approvals, a paid event, a renewal cycle, a campaign.