Solutions

Large enterprises

Multi-entity groups: one shared proof policy, applied across every subsidiary, auditable at group level.

Group master agreementSpaces by subsidiaryGroup-level consolidationDedicated point of contactService commitmentsContractual reversibility

One policy, dozens of entities

What sets a group-wide deployment apart from a team-level one.

In a group, the difficulty isn't technical: it's getting the same rule applied in an eight-hundred-person industrial subsidiary and in a twelve-person product team. Legal departments write IP policies that the field applies unevenly, for lack of a common tool.

A single master agreement, broken down into spaces by entity, resolves this asymmetry: each subsidiary keeps its own users, projects and audit trails, but inherits the group's policy — retention periods, access scopes, certification requirements.

The group level retains what it needs: a consolidation of deposits by entity and by asset type, and the ability to produce a complete record during an audit, a disposal, or a dispute.

Deployment

What the master agreement covers

What your legal, procurement and security teams expect from a group-level agreement.

Space hierarchy

Group, divisions, subsidiaries, projects: the scopes mirror your actual org chart, including joint ventures and minority holdings.

Bulk deposits and per-subsidiary metadata

Each subsidiary can define its own deposit categories and metadata fields, and certifies at volume — dozens of files in a single operation, with real-time processing status.

Consolidation and reporting

A consolidated view of certified assets by entity, type and period, exportable for a committee, an audit, or an M&A transaction.

API keys by entity

Each subsidiary manages its own access keys to connect Ipocamp to its tools (ERP, document management, CI/CD), without depending on a central team for every integration.

Service commitments

Availability, response times, named points of contact, quarterly reviews. The standard terms of a critical vendor.

Contractual reversibility

Certificates can be verified without us, using open standards. The end of the contract affects neither the validity nor the verifiability of proofs already established.

Operations

Useful beyond disputes

The same document base serves the moments when the group's intangible value comes under close scrutiny.

Acquisitions: dated inventory of the target's intangible assets
Disposals and carve-outs: IP scope established entity by entity
Joint ventures: respective contributions documented from formation
Controls and audits: protective measures demonstrable on the record

Group-wide insurance

Coverage is subscribed at the level of the consolidated portfolio rather than asset by asset, with negotiated caps and a scope reviewed each fiscal year.

Use cases

The most common situations

The same deposit serves different needs depending on what you're protecting, and against what. Three cases that come up most often for this profile — see all seven.

Trade secrets

Processes, methods and unpatentable know-how: document your protective measures.

Open →

Proof of trademark use

Document actual exploitation, year by year, against revocation.

Open →

Defensive publication

Prevent a third party from patenting and preserve your freedom to operate.

Open →

Structure proof at group scale.

For an answer tailored to your case, talk to an expert: this page describes a typical situation, yours has its own specifics.

Contact us

Related solutions

Other profiles, in case this one isn't quite the right fit.

For companies

Open →

White label edition

Open →

R&D tax credit firms

Open →