What Horbit is

Horbit runs the operational side of a membership organisation: who belongs to it, what it puts on, what it sends, and what it charges. Every workspace is a tenant with its own members, branding, domain and billing, and each tenant switches on only the parts it needs.

How the product is shaped

A tenant is the unit of isolation. Everything below — every member, event, campaign and certificate — belongs to exactly one tenant, and no query crosses that line. Inside a tenant, features arrive as modules that an administrator turns on or off.

Two ideas worth knowing first

Modules gate features, permissions gate people. Switching a module off hides it from the console, strips its permissions from the tenant's roles, and blocks its endpoints for that tenant. Permissions then decide which administrator may touch what remains. The two are independent: a module being on does not grant anyone access to it.

Members are the spine. Events, campaigns, certificates and segments all resolve back to member records. An email campaign's audience, an event's attendee list and a certificate's recipient are the same people seen from different angles — which is why a member's email address, affiliation and membership status turn up as merge tags, filters and columns throughout.