vbaa: what a business association platform looks like when membership data has to be governed, not just stored

The problem: association tools rarely take governance seriously

Most business-association software treats membership like a CRM list — names, dues, an email blast tool. What it usually skips is the part that actually matters to an association: who has the authority to decide what, and whether that decision trail is auditable after the fact.

vbaa (Navy #15243A + gold, independent brand) is BIXSO’s platform for exactly that — built around a strict member hierarchy (Admin > Officer > Member) with voting and audit trail as non-negotiable, not optional add-ons.

Where it stands — honestly

We’re not going to describe vbaa as finished, because it isn’t. It’s in active development (status: DEV), currently mid-migration off an early Base44 scaffold onto Firebase directly — authentication moving to Firebase Auth with Google OAuth, data access moving to a Firestore shim that replaces the old entity client. That’s real, in-progress engineering, not a stalled project: the role-based auth guard (replacing a placeholder admin bypass) is already committed and live in the codebase.

The architecture underneath

vbaa follows BIXSO’s Brain-as-Provider model: the app runs independently on its own stack, and only has a data-sync obligation back to BIXSO Brain while it remains inside the ecosystem — a relationship that can be cut if the app is ever sold or exits. The backend (vbaa_service/) is a standalone Node service, a Cloud Run deployment candidate once the migration lands.

Why we’re building it this way

Associations don’t need a flashier feed — they need decisions that hold up when a member disputes a vote six months later. That’s a governance problem before it’s a UX problem, and it’s why vbaa’s foundational work is role hierarchy and audit trail, not onboarding polish.

Book a consult if your organisation needs membership software that treats “who decided this, and when” as a first-class question.