The business applications built on MemberJunction. Each one is an MJ Open App — its own repository, database schema and npm packages — installed into any MJ instance with mj app install, which installs the apps it builds on first.
BizApps
14
Released
11
In development
3
Levels
5
Scroll sideways to see the whole map.
Hover or focus an app to trace what it builds on and what builds on it. Select it to jump to its details.
A won deal becomes a signed agreement, then an order with its payments and subscriptions, then balanced journal entries that batch to the ERP that owns your general ledger. Sales records intent and never computes money; Orders prices and bills; Accounting is the subledger, not the general ledger.
The apps
Every public bizapps-* repository in the MemberJunction organization, in alphabetical order. Each card is read from the app's own mj-app.json.
Accounting
Level 2 · Accounting, Finance
v0.24.0
AR subsidiary ledger of record and journal entry primitives (GL accounts, balanced JEs with multi-currency, dimensions, tax) for MemberJunction. Not a general ledger — batches to ERP/QBO/NetSuite/BC.
@mj-biz-apps/collaboration-core-entities-server Server
@mj-biz-apps/collaboration-ng Client
@mj-biz-apps/collaboration-ng-widgets Client
@mj-biz-apps/collaboration-entities Shared
@mj-biz-apps/collaboration-actions Shared
@mj-biz-apps/collaboration-core Shared
Committees
Level 2 · Governance
v1.4.0
Unified governance platform for managing committees, memberships, meetings, action items, and documents — with AI-powered minutes generation and health analytics
The record of customer agreements — executed documents, which version of the standard agreement each one incorporates, the provisions negotiated away from it, and the renewal, notice and escalation terms that appear nowhere on an order. A record-keeping and lookup surface: it does not price, bill, recognize revenue, or create orders.
Reusable case / issue / ticket primitives — Issue, IssueType, IssueStatus, IssueComment — the shared foundation for ticketing UX (Izzy) and the cloud-feedback destination
Unified order management for MemberJunction — products, orders, payments, subscriptions. The Order is the transactional substrate and the A/R primitive; payments and subscriptions are aspects of the same business event. Emits balanced journal entries into BizApps Accounting.
Deal pipeline management for MemberJunction — accounts, contacts, pipelines, deals with priced lines, deal teams, stage history and forecasting. Sits at the top of the revenue stack: sales records intent and asks BizApps Orders for every number, so a closed deal becomes a contract and an order in one transaction rather than a notification to re-key it by hand.
A secure client portal for exchanging messages, documents, and e-signatures with external contacts. Passwordless magic-link entry deep-links contacts into subject-lined conversation threads; staff work the same threads from an inbox in MJ Explorer. Includes file requests with a full lifecycle, e-signature via the MJ eSignature engine, and an embeddable <mj-secure-messaging> Angular Element widget any site can host.
Configurable engagement scoring engine on the MemberJunction entity graph. Define any number of concurrent scoring models over any anchor entity, with explainable, trending scores and an action layer.
Not BizApps, but worth knowing about. These are picked by hand and are never added to the catalog automatically.
Demo association
More Cheese
The MoreCheese demo association (International Cheese Federation): a generated, causally-consistent dataset demonstrating the MJ platform across composed BizApps.
Deterministic, causal business-world and data simulation engine for MemberJunction. It generates the connected, realistic data behind demos such as More Cheese.
This page is built from GitHub every time the documentation site is deployed (last read 2026-10-21). It lists every public repository in the MemberJunction organization whose name starts with bizapps-; an app counts as released once its mj-app.json is on the repository's main branch at a real version. To add a BizApp, create a public bizapps-<name> repository with an mj-app.json at its root. It appears here on the next deploy with no documentation change.
A plain-markdown copy is kept in the MJ repository as guides/BIZAPPS_GUIDE.md and refreshed automatically when the catalog changes.