Skip to content
A records keeper pulls a bound volume from the tall wooden shelves of a quiet archive

The control plane for intangible assets

Know what your business owns.

Connect every brand, software asset, domain, agreement, licence, repository and piece of evidence in one continuously maintained ownership graph. See who owns it, who can use it, why that is true, and what has to happen if it moves.

Evidence-backed relationships Multi-entity by design Built for transfer and diligence

Your intangible assets are already connected

Your systems just do not show the connection.

Your domains live with a registrar. Code lives in Git. Assignments live in PDFs. Trademarks live in IP systems. Licences live in contracts. Ownership is inferred from all of them — usually by a small number of people who remember how the pieces fit.

Intangible HQ turns that institutional memory into a maintained, evidence-backed system of record.

BrandMeridian PayPackage
Northgate IPLegal ownerVerified
Northgate LtdOperatorLicensed
meridian.comDomainVerified
MERIDIANTrademarkVerified
core-ledgerRepositoryShared
AssignmentEvidenceVerified

Verified Licensed or shared Needs review

An example ownership graph. The brand Meridian Pay is connected to its legal owner Northgate IP (verified), its operator Northgate Ltd (licensed), the domain meridian.com (verified), the MERIDIAN trademark (verified), the core-ledger repository (shared with other brands) and an assignment recorded as evidence.
Legal truth

Who owns the right?

Which entity holds it, and which evidence supports that position.

Operational truth

Who controls it?

Which account, repository, team or operator holds it day to day.

Economic truth

Who earns from it?

Which brand, product or business package it economically belongs to.

Chain of title

Follow the right from creator to current owner.

A file, an invoice or a Git repository is not the chain of title. Intangible HQ connects the contributor, the agreement, the assignment, the contribution, the asset, the current owner, the licence, the operator and the brand — with the evidence behind every material step.

  1. ContributorPerson
  2. Contractor agreementAgreement
  3. RepositoryEvidence
  4. Software componentAsset
  5. AssignmentAgreement
  6. IP ownerEntity
  7. LicenceRight
  8. Operating entityEntity
  9. BrandBrand
A chain of title reads: Contributor, then Contractor agreement, then Repository, then Software component, then Assignment, then IP owner, then Licence, then Operating entity, then Brand.

Built for the moment something moves

Prepare a spin-out before it becomes a legal scavenger hunt.

Select a brand package and model the transaction. Intangible HQ classifies every item in scope — what transfers, what stays and is licensed back, what needs a novation or a counterparty's consent, what is an account that has to change hands, and what a lawyer needs to look at.

Nothing in the live graph changes until the transaction does.

Scenario — sell Meridian PayDraft
An example transfer action plan for the sale of a brand package
ItemAction
Brand domainTransfer
Shared core platformLicence
Customer contractNovate
Cloud accountMigrate
Third-party licenceConsent
Uncovered contributorResolve
A brand manager reviews logo sketches and colour swatches at a studio table
Brand Asset Package — Meridian PayEconomic grouping
  • MERIDIAN (word mark)Owner: Northgate IPVerified
  • meridian.comOwner: Northgate IPVerified
  • core-ledgerOwner: Northgate IPShared
  • Merchant onboarding moduleOwner: Northgate LtdVerified
  • Support & payment accountsOwner: Northgate LtdNeeds review

Members keep their real owner. A package describes what a business consists of; it never changes who holds title to anything inside it.

Brand Asset Packages

What would actually be sold, if this brand were sold?

A package draws a boundary around the assets, rights, software, domains, accounts and agreements that together make a business — including the ones owned by a different entity in the group.

Membership is economic grouping. It never changes who legally owns a member, which is exactly why it can be trusted in a transaction.

Software provenance

Git tells you who committed. Intangible HQ helps you prove why the company owns the result.

Repositories, contributors, agreements, releases and imported SBOM data connect to the entity that is meant to own the output. Contribution periods are compared against agreement windows, and the exceptions are listed while the people involved are still reachable.

Repository metadata is evidence of contribution — never, on its own, a conclusion about legal ownership.

A software founder smiles as he signs a licence agreement at his desk
Contributor coverage
  • meridian/core-ledger1 uncovered
    7/8 contributors with agreement coverage
  • meridian/webCovered
    5/5 contributors with agreement coverage
  • meridian/mobile1 uncovered
    3/4 contributors with agreement coverage

Commit history is evidence of contribution. It is not a conclusion about who owns the result — that comes from the agreements above.

Two lawyers discuss a contract at a meeting table, one pointing at a page
Readiness — Meridian Pay4 findings
  • Uncovered contributor3 contributions in 2024 fall outside any assignment window — meridian/core-ledger.
  • Custody mismatchmeridian.com is registered to a personal account, not to Northgate IP.
  • Notice window closingReseller agreement renews automatically in 34 days unless notice is given.
  • Ownership verifiedMERIDIAN class 42 assignment recorded, evidenced and verified by M. Okonkwo.

Every finding names the rule, the objects and the missing evidence. Readiness measures completeness against your policy — it is not a legal opinion.

Find the gaps before diligence does

Turn hidden diligence problems into ordinary work.

Most chain-of-title problems are discovered when a buyer, an investor or a lawyer asks. Explainable rules run continuously, so the team fixes gaps while the people, documents and context are still easy to find.

Every finding names the rule, the objects and the missing evidence. No mystery score.

Where it sits

It does not replace the systems you already run.

Source control, CLM, IP management, entity management and SBOM tooling each answer their own question well. None of them answers the ownership question across all of them.

What adjacent systems already know, and what Intangible HQ adds on top
Digital asset managementCreative files and brand usageLegal and economic ownership, contracts, package composition and transfer context
IP managementRegistered rights and docketingSoftware, domains, operational custody, economic packages and provenance
Contract lifecycle managementContracts and their clausesThe assets and rights those clauses govern, and their position in the ownership graph
Entity managementCompanies, officers and shareholdingsThe intangible assets and rights flowing between those entities
Git and source controlCode and who committed itContributor agreements, ownership evidence and chain of title
SCA and SBOM toolingDependencies and their licencesHow a third-party component affects a brand package and a transaction

How it works

Register, connect, prove, monitor, transfer.

Five steps, in the order a real estate gets built. Nothing here requires you to finish step one before step two is useful.

01

Register what exists

Create or import entities, brands, software, IP, domains, accounts and agreements. Each object gets a stable identity that the rest of the graph can point at.

02

Connect the relationships

Model ownership, use, custody, licensing, creation, dependency and package membership as explicit, typed, effective-dated relationships.

03

Attach and verify evidence

Link assignments, agreements, registry records and contribution evidence. AI can propose facts; people verify the material ones before they are trusted.

04

Keep the graph current

Integrations, reminders and explainable rules surface changes, expirations, gaps and conflicts — without silently overwriting a verified legal fact.

05

Use the record

Answer ownership questions, generate schedules, prepare a transfer or open a scoped diligence room from the live graph instead of rebuilding the story.

Who it is for

Built for groups with more than one company in them.

Shared IP, several entities and external contributors are the normal case — and the reason the ownership picture goes implicit in the first place.

Technology groups

Every brand and entity in one ownership graph.

Venture studios

Build on shared IP, keep the packages separable.

Software companies

Contributor-to-agreement coverage, continuously.

Corporate development

Know what moves before the deal is signed.

Why trust it

Claims you can check against the product.

No customer logos and no accuracy percentages: the product has not launched, and inventing either would be the first thing a prospect catches.

One graph

Brands, software, rights, evidence and entities in the same model — not six systems joined by a spreadsheet.

Three truths, kept apart

Legal ownership, operational custody and economic grouping stay distinct, because conflating them is what produces the surprise.

Every change has history

Material relationships are effective-dated, verified and superseded — never quietly overwritten.

Transfer-aware by design

Packages and scenarios show what moves, what stays, and what needs a licence, a novation or a consent.

Security

A system this sensitive has to be inspectable.

Ownership records, executed agreements and transaction plans are among the most sensitive data a company holds. The controls below are the ones that are implemented — this page carries no compliance badges the product has not actually earned.

  • Tenant isolation

    Data is scoped per tenant, with object-level permissions applied to records, search, export and graph traversal alike.

  • Identity

    Multi-factor authentication, with enterprise SSO, SAML and SCIM as product readiness allows.

  • Evidence integrity

    Documents are versioned and content-hashed, so an exported bundle can be checked against what the platform holds.

  • Material audit events

    Ownership, rights and verification changes are appended with actor, capacity and before/after state.

  • Confidentiality labels

    Labels constrain traversal, search, export and AI retrieval — not only which page a person can open.

  • AI data boundary

    Retrieval is permission-scoped. Hidden objects do not leak through an answer, a count or a summary.

Questions

The ones buyers actually ask.

Including the two we are asked to overclaim on — what AI is allowed to decide, and whether a readiness score is a legal opinion.

It manages a broader operating model than traditional IP portfolio software. It registers trademarks, copyright, software, domains, data and other intangible assets, but its purpose is to connect ownership, provenance, rights, operational custody and transferability. It integrates with specialist patent and trademark systems rather than replacing prosecution and docketing.

Build the ownership record before somebody asks for it.

Register what exists, connect the relationships, attach the evidence. The answer you need under deadline is the one you maintained beforehand.

Evidence-backed relationships Multi-entity by design Built for transfer and diligence