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 challenge is applying the same rule in an eight-hundred-person industrial subsidiary and in a twelve-person product team. Legal departments write IP policies that local teams apply unevenly with different tools.

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, timestamping 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 timestamps at volume, dozens of files in a single operation, with real-time processing status.

Consolidation and reporting

A consolidated view of timestamped 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 management (ERP), document management and continuous integration (CI/CD) tools. Each integration is thus managed locally.

Service commitments

Availability, data return times, named points of contact, quarterly review. The usual terms for a critical vendor.

Contractual reversibility

Certificates are verified using open standards, independently of Ipocamp. The end of the contract preserves the validity and 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 meets different needs depending on what you protect and the risk you face. Here are three common cases 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 to explore next.

For companies

Open →

White label edition

Open →

R&D tax credit firms

Open →

Not sure which profile matches yours?

Describe your situation and we'll point you to the right solution.

Describe my situation →