Pricing
Core, Scale, and Enterprise plans for each stage of control maturity.
Start with Core for foundational governance, move to Scale for cross-team operations, and standardize on Enterprise for organization-wide controls and assurance.
Core and Scale support controlled self-serve entry for pilot and rollout stages, while Enterprise supports complex control design, identity, and compliance requirements.
What OBAM is
OBAM is a governance system for public references with a public verification surface and auditable authorization lifecycle records.
Who it's for
OBAM is for legal, IP, procurement, and security stakeholders that need external references to map to explicit operational controls.
What it verifies
OBAM verifies whether public logo and reference usage is currently authorized and whether the reference status is active, expired, or revoked.
How status changes
Status transitions are part of an authorization lifecycle. Revocation and expiry update the public verification surface to reflect current authorization state.
What OBAM is and is not.
OBAM is lifecycle governance for public references, not a one-time internal approval step.
| Comparison | OBAM model | One-time/internal model | Evidence |
|---|---|---|---|
| OBAM vs DAM | OBAM governs public reference claims through an ongoing lifecycle: approvals, revocation control, and externally visible verification output. | DAM systems are built for asset storage and internal distribution, typically without a public authorization lifecycle and revocation-backed verification surface. | See docs |
| OBAM vs CMS approvals | OBAM keeps governance active after publication by tracking status changes and reflecting current authorization on verification pages and outputs. | CMS approvals usually end at publish time and are internal workflow checkpoints, not continuous governance with revocation and public verification. | See verification surface |
| OBAM vs reference management | OBAM links each public claim to accountable lifecycle governance, including revocation and evidence-ready verification output for external review. | Reference management is often relationship coordination for point-in-time use, not legal-grade lifecycle control for ongoing public authorization status. | See legal solution |
Plans
Select the governance control level that matches your rollout.
Core and Scale are available through self-serve checkout as a controlled pilot entry path, so teams can launch governance workflows quickly before broader rollout.
For legal & IP teams getting control in place
Core
Best fit: a focused team establishing governed reference workflows and baseline controls.
A strong starting point for companies that want to authorize references, control logo usage, and introduce revocation without heavy rollout friction.
- Up to 5 seats
- Up to 50 active references
- Authorization & revocation controls
- Expiry policies (basic)Set a simple expiry date and manually renew.
- Basic audit trailRecord who approved or revoked a reference and when.
- Vendor email workflowsUse governed vendor communication templates to request, approve, and update references.
- Logo & language governance
For active governance across legal, procurement, and brand
Scale
Best fit: cross-functional rollout with shared governance across business and control teams.
For teams managing ongoing reference workflows, larger reference volumes, and stronger operational governance across multiple stakeholders.
- Up to 20 seats
- Up to 250 active references
- Lifecycle & renewal controlsFull lifecycle governance with automated renewal reminders.
- Full audit historyTrack every lifecycle change (draft, approval, edits, expiry, renewal, revocation).
- Advanced roles & policy routingConditionally route approvals based on templates and roles.
- Testimonial & case-study workflowsCapture approved titles, evidence and scope for narratives.
- Priority supportFaster response targets for operational and rollout requests.
For high-volume or regulated organizations
Enterprise
Best fit: enterprise-wide controls with custom workflows, identity, and compliance integration.
For organizations that need enterprise rollout, advanced security, contractual support, and governance at scale.
- Custom seats & references
- Custom lifecycle policiesDefine organization-specific expiry & renewal rules.
- Audit export & enterprise controlsExport audit logs and integrate with external compliance systems.
- API & bulk operationsAutomate lifecycle actions and updates using APIs and bulk tooling.
- SSO / SCIMUse enterprise identity providers for single sign-on and lifecycle provisioning.
- Dedicated support & SLAIncludes dedicated support coverage with SLA-backed response commitments.
Plan comparison
Choose based on control needs, not feature confusion.
| Capability | Core | Scale | Enterprise |
|---|---|---|---|
| Team seats included | Up to 5 | Up to 20 | Custom |
| Active public references tracked | Up to 50 | Up to 250 | Custom |
| Expiry & renewal governance depth | BasicSet a simple expiry date and manually renew. | Full & remindersFull lifecycle governance with automated renewal reminders. | CustomDefine organization-specific expiry & renewal rules. |
| Audit history depth | BasicRecord who approved or revoked a reference and when. | Full historyTrack every lifecycle change (draft, approval, edits, expiry, renewal, revocation). | ExportableExport audit logs and integrate with external compliance systems. |
| Roles & permissions model | BasicAssign roles for legal, marketing, procurement and partner managers. | AdvancedConditionally route approvals based on templates and roles. | CustomCreate bespoke roles and approval workflows. |
| Team management scope | Single admin | Cross-team | Custom & SCIM |
| Approval policy routing | — | Templates & rules | Custom workflows |
| Case study & testimonial workflows | — | Included | Included |
| Vendor communication workflows | Yes | Yes | Yes |
| API access & integrations | — | — | Yes |
| Support coverage | Priority | Dedicated |
What happens after I choose a paid plan?
If you are new to OBAM, you will create your account first and then continue directly into checkout with your selected plan and billing cadence. If you are already signed in, checkout starts immediately.
Which plans are available?
OBAM offers Core, Scale, and Enterprise plans. Core and Scale are self-serve, while Enterprise is scoped with sales for custom controls.
Can we start with one team and expand later?
Absolutely. Many customers begin with a single control owner, then extend to procurement, brand, and security teams as process maturity grows.
What determines pricing?
Pricing is based on deployment scope, control requirements, and enterprise features needed for your workflow. We structure plans so teams can start lean and scale as adoption expands.
Do you support enterprise controls (SSO/SCIM roadmap or plan-tier gating)?
Enterprise controls are supported based on plan and rollout scope, with SSO and lifecycle identity integrations managed as part of onboarding. We can align required controls with your phase and governance needs.
Need a pilot first?
We can scope a focused rollout around one team, one workflow, or one public verification surface before broader adoption.
Next step
Start self-serve, or talk through rollout.
Start with Core or Scale through checkout, or contact us if your rollout and governance needs require an Enterprise setup.