Unified PIM + DAM
Product data and the assets that go with it. One system.
Most teams keep the specification in a PIM, the artwork in a DAM and the approvals in email. Scrivino keeps all three in one record — versioned, attributed, and never overwritten.
- Version 1 · createda4f1c9e2genesis
- Version 2 · spec revised7b02de55↰ a4f1c9e2
- Version 3 · artwork linked1e8a06bd↰ 7b02de55
- Version 4 · approved & signedc30f4a17↰ 1e8a06bd
Product data in one tool. Files in another. Approvals in email.
The weakest part of most PIM suites is the DAM bolted onto them. So teams buy a second system, and an integration between the two — every year, for as long as they both exist.
The record of what was approved ends up in neither. It lives in an email thread, a shared drive, and the version of the datasheet somebody sent on Tuesday.
That holds until a regulator, a marketplace or an auditor asks which version was approved, by whom, and when. Then it takes a week to answer.
One catalogue, one asset library, one history
Not two products with an integration between them. One write path, one permission model and one version history, covering the specification and the artwork together.
Product information
Families and variants with inherited values. Language fallbacks that show where a value came from and never count a fallback as translated. Readiness per channel and language.
Assets
Files stored once, with previews and renditions generated for you, rights and licence expiry tracked per asset, and every file linked to the products it belongs to.
A record, not a log
Every change is a versioned, attributed changeset. History is append-only, enforced by the database itself for every role, the owner included.
AI didn’t arrive late here.
Every PIM you can buy today was designed before large language models existed. Their audit logs were built for people making dozens of edits a day, not agents making thousands — so bolting AI on means either trusting it completely or switching it off.
Scrivino starts from the other end. Every change, human or machine, is a versioned, attributed changeset on an append-only record. So an agent is just another author. It can be granted rights, never more than the person who invoked it. It can propose changes, and structurally cannot approve its own. Every edit it makes is reversible and attributed to the person who authorised it.
You don’t have to trust our AI. You have to be able to check it.
What runs today, what comes next
Every feature on this site carries one of three labels, and each means exactly one thing.
- Live
- 37 features running today. You will see them in a demo.
- Next
- 8 features in build, each with the quarter we will be held to.
- On the roadmap
- 13 features specified, not yet scheduled. Early adopters decide the order.
Measured, not projected
Two million products on one mid-range machine
- Catalogue held
- 2 M entities
9.6 M versions - Write latency, p95
- 12–16 ms
- Permission-filtered search, p95
- 6.3 ms
- Full history re-verified
- 19.3 min
0 failures
One node, single tenant, 24 fields per content type. We publish the conditions with the numbers, and the numbers do not transfer to wide schemas. Method and full table.
Product data has deadlines now
Each of these asks the same question a shared drive cannot answer: which version of a record was approved, by whom, and when.
- In force EUDAMED The first four modules became mandatory for medical devices: actor and device registration, notified bodies and certificates, market surveillance. Commission Decision (EU) 2025/2371
- Applies from EUDAMED, legacy devices The end of the transition for registering devices that were already on the market before mandatory use began. Commission Decision (EU) 2025/2371
- Applies from Battery passport A digital passport for each EV, light-means-of-transport and industrial battery above 2 kWh placed on the EU market. Regulation (EU) 2023/1542, Art. 77
- Applies from Revised CLP labelling New label-formatting rules for hazardous chemicals, postponed from 2026 by the 2025 “stop-the-clock” amendment. Regulation (EU) 2024/2865, as amended by (EU) 2025/2439
Scrivino does not file to EUDAMED or generate a battery passport. It keeps the approved record those filings are made from.
What Scrivino cannot do yet
You would find these in the first demo anyway. Here they are first, so you can decide whether they matter to you before either of us spends an afternoon.
- ProductYou cannot yet filter or sort by an arbitrary attribute value. Search is full text with fixed facets.
- ProductNo marketplace feeds or native connectors. If your deadline is a marketplace listing requirement, we are not your answer today.
- AssuranceNo SOC 2, no ISO 27001, no validation package. Not started, not hidden.
- CompanyTwo people and no customers yet. That is why the early-adopter programme exists.
Early adopters — apply now
We are looking for design partners: manufacturers and brands with a real catalogue and a real deadline. You get the system, our time, partner terms, and a say in what we build next.