Skip to content
Fifteen modules. One deployment.

Run your whole alumni community from one place

Metrolo gives your organisation a public website, a member portal and an admin panel — with the directory, events, dues, fundraising, jobs, mentoring and elections already joined up behind them.

  • Your domain, your branding
  • GDPR rights built in
  • One deployment per organisation
15
modules, shipped together
Not add-ons. Not a marketplace.
3
surfaces from one database
Public site, member portal, admin panel.
1
deployment per organisation
Your data never shares a table with anyone else's.
100%
of admin actions audited
Every change to member data is recorded.
One system, three front doors

Everyone gets the surface they need — from one database

Most organisations end up with a website from one vendor, a member database from another and an events tool from a third. Metrolo is one system that presents itself three different ways.

A public website

Prospective members, donors, the press

Your own pages, events listing, business directory and news — carrying your organisation's name, on your own domain, indexed and shareable.

  • /
  • /events
  • /business-directory
  • /news

A member portal

Signed-in members

The directory, their profile, tickets, mentoring requests, jobs, campaigns and their own data rights — everything a member came for, behind one login.

  • /users/feed
  • /users/directory
  • /users/profile
  • /users/settings

An admin panel

Your team, with named permissions

Approvals, events, dues, campaigns, elections and the audit trail. What each admin sees is decided by the grants their role carries.

  • /admin/members
  • /admin/events
  • /admin/finance
  • /admin/audit
Directory & profiles

A directory members actually trust with their details

Every field carries its own visibility tier — public, members-only, private or hidden — and the member chooses. The rule is enforced in the API, so a hidden phone number is not merely absent from the page: it never leaves the database.

  • Search, filter and paginate across thousands of records
  • Custom fields you define, filterable like any other
  • Career history, education, publications, projects and awards
  • CSV export for the office, signed URLs for every photo
Events & ticketing

Real ticketing, all the way to the door

Ticket types with capacity and pricing, guest registrations without an account, custom questions per event, and QR check-in that stays correct when a steward scans the same code twice.

  • Draft and live states — nothing publishes by accident
  • Per-event registration questions with precise error messages
  • Automatic 24-hour reminders to everyone holding a ticket
  • Public event pages built for search and for sharing
Dues, tickets & gifts

One ledger behind every pound that moves

Membership dues, event tickets and donations all run through the same payment machinery — including a complete offline path for the bank transfers and cheques a great many organisations still live on.

  • Reference numbers, cheque images and an approval queue
  • Gross and net after service charge, side by side, always
  • Lapsed memberships close the right doors automatically
  • Campaign goal meters that move as gifts are approved
The whole platform

Fifteen modules, and none of them is an upsell

Turn off what you do not need — module flags are per organisation. What stays on is fully built, not a placeholder waiting for a paid tier.

Roles & permissions

Committee volunteers should not see everything

A chapter secretary needs the events module. They do not need the finance ledger or the erasure queue. Metrolo was built with that distinction in the foundations rather than bolted on afterwards.

GrantSuper adminChapter adminMember
view_pending_member_list
approve_member
create_job
manage_business_directory_category
view_mentorship_dashboard
export_member_csv
  • Named grants, not job titles

    Permissions are specific things a person may do. Roles are bundles of them, and you decide what goes in each bundle.

  • Double-gated visibility

    A screen appears only when the module is enabled for your organisation and the user holds the grant. Otherwise it renders nothing — no greyed-out teases.

  • Owners keep their own

    Whoever created a record can always edit it, even without the blanket permission. The obvious rule, applied consistently.

Security & data protection

Built for organisations that hold other people's data

An alumni database is one of the more sensitive datasets a university or association keeps. The obligations that come with it were designed in from the first migration, not added when a customer asked.

  • Single-tenant by design

    One customer, one deployment, one database, one domain. Your member data is not a row with a tenant ID next to somebody else's.

  • Sessions, not tokens in storage

    HttpOnly, Secure, SameSite cookies. No JWT sitting in localStorage waiting for the first cross-site script to read it.

  • Export and erasure, for real

    A member can download everything you hold on them, and request deletion — with referenced records anonymised rather than orphaned.

  • An audit trail that exists

    Every admin action on member data is written as it happens. Read-only afterwards, because history is not something you edit.

  • Uploads treated as hostile

    Files are MIME-sniffed on the server, stored outside the webroot and served only through short-lived signed URLs.

  • Consent that can be re-asked

    Privacy and terms are versioned. Bump a version and members are asked to accept again at their next login.

Read how Metrolo handles your data
FAQ

Questions we get asked

If yours is not here, ask us directly — a real person answers.

What is Metrolo?

Metrolo is a management platform for alumni associations and member organisations. A single deployment gives you a public website, a member portal and an admin panel, with fifteen modules — directory, events and ticketing, membership and dues, fundraising, jobs, mentoring, business directory, elections, email campaigns and more — sharing one database.

Who is Metrolo for?

University alumni offices, alumni associations, professional bodies, chambers of commerce and membership charities — any organisation that maintains a roll of members, collects dues or ticket money, and runs events or campaigns for them.

What does single-tenant mean, and why does it matter?

Each customer gets their own deployment, their own database and their own domain. Your member records are never stored in shared tables alongside another organisation's. It simplifies data protection questions, makes backups and exports yours alone, and means a change for another customer cannot affect your data.

Can we use our own branding and domain?

Yes. The public site, the member portal and the admin panel all carry your organisation's name and identity on your own domain. Metrolo is the software underneath; your members see you.

Do we have to use all fifteen modules?

No. Module flags are set per organisation. A module that is switched off does not appear anywhere — not as a disabled menu item, not as an upgrade prompt. It simply is not part of your deployment.

How does Metrolo handle GDPR?

Data-subject rights are built in rather than promised. Members can export everything held about them and request erasure, with referenced records anonymised instead of orphaned. Consent is captured and versioned, so bumping your privacy policy asks members to accept again. Every admin action on member data is written to an audit log.

Can members pay by bank transfer or cheque?

Yes, and it is a complete path rather than an afterthought. Offline payment gives the member instructions, a reference number, a place to upload a cheque image and a clear pending state, and gives your team an approval queue with a full record. Stripe and PayPal adapters are on the roadmap.

How is a deployment set up?

Metrolo runs on your own infrastructure or on hosting we arrange — Nginx, PHP-FPM and a Node process, with a scheduler and a queue worker. We handle provisioning, migration of your existing member data, and the first-run configuration with you.

See it with your own member data

A 30-minute walkthrough against a scenario that looks like your organisation — your modules, your roles, your renewal cycle. No slide deck.