Solutions
Companies and large groups: a governed IP evidence record
A governed system of record for your IP and R&D teams, and a common policy applied in every subsidiary.
The IP you produce every day
High-value assets, uneven documentation.
Innovation moves faster than the formal intellectual property system. Long before any filing, your teams produce code, designs, experimental data, specifications and know-how, continuously, across departments and sites. These assets have value, but their documentation often remains inconsistent.
The day a dispute, an audit, or a competitor's patent raises the question "what did we have, and since when?", shared drives and email threads make the case hard to demonstrate. Trade secret protection requires proof that reasonable measures were taken. The prior user right (the right to keep using an invention later patented by a third party) rests on verifiable dates.
Ipocamp gives your IP and R&D teams a single, governed platform to timestamp this evidence the moment it's created. The fingerprint is published and the file is transferred, encrypted, to the storage set by your plan.
Governance
Built to be deployed
The controls your security, legal and IT teams expect, before approving one more tool.
Roles and access policies
Permissions define who can timestamp, review and retrieve evidence. They are structured by team, by project and by business unit.
Single sign-on
Log in through your identity provider via SAML or OIDC (two standard protocols), with provisioning and deprovisioning through the systems you already run.
Categories and custom fields
Each type of deposit has its own fields (project, reference, batch, date…), which you can show on the certificate. Authors, individuals or legal entities, are set up in advance, and a French legal entity can be looked up from its SIREN or SIRET number.
Controlled data residency
Encrypted files stay in the storage and jurisdiction you designate. The fingerprint is published to allow verification.
Quotas per team
Timestamping credits allocated per user or per division keep the budget predictable and usage transparent.
Multi-entity groups
What the group framework agreement covers
A single master agreement, broken down into spaces by entity, closes this gap: each subsidiary keeps its own users, projects and deposit history, but inherits the group's policy (retention periods, access scopes, timestamping requirements).
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 defines its own deposit categories and metadata fields. It timestamps in bulk (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. Integrations are thus managed locally.
Service commitments
Availability, data return times, named points of contact, quarterly review. The usual terms for a critical vendor.
Program
Managing trade secrets at scale
Protecting a secret relies on consistent discipline. The judge checks that you took reasonable measures and that you can prove what the secret was, and since when.
Defend through prior existence
The same evidence supports a prior user right and enables defensive publication: submitting your work as prior art to prevent a third party from patenting what your teams have already invented.
Operations
Useful beyond disputes
The same document base serves the moments when the group's intangible value comes under close scrutiny.
Group-wide insurance
Coverage is taken out at the level of the consolidated portfolio rather than asset by asset, with negotiated caps and a scope reviewed each fiscal year.
Procurement, security, legal
Your evaluators' questions
What comes up in tool review, addressed upfront.
Confidentiality
What do you see of our files?
The SHA-256 fingerprint is computed at the time of deposit. The file is transferred, encrypted, to the storage set by your plan and its content stays confidential.
Access
How do people log in?
Through your identity provider, via SAML or OIDC (two standard protocols), with optional two-factor authentication.
Audit
Can activity be audited?
Yes: an unalterable chained log, viewable and exportable by your security and compliance teams.
Reversibility
How does reversibility work?
Certificates are verified using open standards, independently of Ipocamp. Your evidence stays verifiable after the contract ends.
Deployment
Multiple subsidiaries?
Yes: one space per entity, separate policies and deposit histories, shared group-level governance.
Costs
How do we control the budget?
Credit quotas per user and per team, with real-time visibility into consumption.
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.
Deploy governed evidence across your teams.
For an answer tailored to your case, talk to an expert: this page describes a typical situation, and yours has its own specifics.
Contact usNot sure which profile matches yours?
Describe your situation and we'll point you to the right solution.