@ontoboom/b2b-saas

B2B multi-tenant SaaS: workspaces, members, roles, plans, entitlements, feature flags, usage events, invitations, and billing. The schema every B2B SaaS reinvents — agents that hop between products shouldn't have to.

Classes

Object properties

Data properties

Individuals

Connect this ontology

● Checking…

MCP endpoint

https://mcp.ontoboom.com/o/@ontoboom/b2b-saas@0.1.0

{
  "mcpServers": {
    "ontoboom": {
      "url": "https://mcp.ontoboom.com/o/@ontoboom/b2b-saas@0.1.0",
      "transport": "sse"
    }
  }
}

Two manifest-derived tools are exposed in this iteration:list_entities anddescribe_entity. More tools (find_relationship, enumerate_values) ship as followups.

README

# @ontoboom/b2b-saas

A B2B multi-tenant SaaS ontology covering the workspace → user → plan → usage
loop.

## Coverage

- **Workspace** (the tenant) with billing email + subdomain
- **User**, **Membership** (User × Workspace), **Role**, **Invitation**
- **Plan** + **Subscription** + **Seat** + **Entitlement**
- **FeatureFlag** + **FeatureFlagAssignment** (per-workspace rollout)
- **UsageEvent** for metering
- **APIKey** with scopes
- **AuditLogEntry** for compliance

## SHACL highlights

- Workspace subdomain must be DNS-safe.
- Email fields use a permissive regex.
- `Subscription.status` is enumerated `trialing|active|past_due|canceled`.
- `Role.systemRole` enumerated `owner|admin|member|viewer`.
- A Membership must reference exactly one User and one Workspace.

## Forking

Drop the FeatureFlag subgraph if you don't run per-tenant rollouts. Drop
APIKey if your product has no public API.

Reviews

No reviews yet · Be the first to review.

Sort: