Skip to content

The platformOwnership and security

Owned, not rented.

Ownership is not a line in a contract. It is a set of practical facts a board can check. Here they are, and here is what happens if MemberWright disappears.

Start with an auditSee how it works

What you own

Four things, from day one.

  • Source code

    In a repository the association controls from the first commit. Documented, with a written handoff. Any competent product team can take it over.

  • Data

    In a standard PostgreSQL database in your account. A full export is a command, not a support ticket, and the platform keeps running afterwards.

  • Accounts

    Hosting, database, domain, email and payment accounts opened in the association's name on day one. We hold access while we work, and hand it back when we stop.

  • Roadmap

    Yours. The monthly improvement backlog is what your members and staff ask for, prioritized by you, not by a vendor's average customer.

Security

Enforced where the data lives.

  • Permissions in the database

    Row-level security means a member can see only what their role allows, even if a screen has a bug. It is enforced where the data lives, not only in the interface.

  • Encrypted, backed up, tested

    Encrypted at rest and in transit. Daily backups, with a restore tested and dated, because a backup nobody has restored is a hope.

  • Staff sign in with their organization

    Single sign-on through Google Workspace or Microsoft 365, so leaving staff lose access the moment their account is closed.

  • An audit log

    Who changed what, when, on every record. For the board, for disputes, and for the day someone asks.

  • An accessibility statement

    WCAG 2.1 AA as the target, in both themes, with a statement your association can publish. Associations are increasingly asked for one.

If MemberWright disappears

The platform stays.

The stack is open and widely used: Next.js, PostgreSQL on Supabase, Tailwind. The codebase is documented and lives in your repository. The accounts are yours. The handoff is written before launch, not after a falling out.

A competent product team, in-house or another studio, can take it over. That is the test we design for, and it is a fair question to ask any studio before signing.

The board's ownership checklist

Own it from day one.

Start with a three-week audit: every tool mapped, a blueprint and a fixed quote. No demo, no sales deck.

Start with an audit