Platform

Everything it does, and when

The page that answers “does it do X?”. Every feature carries a label, and the labels mean exactly one thing each.

Live
Running today in build wp62.2. You will see it in a demo.
Next
Specified, scheduled and in build, dated because we will be held to the date.
On the roadmap
Specified, not yet scheduled. Early adopters decide the order.

Status checked against the product on 19 October 2026.

The record

The record

One write path, one permission model, one history — for the specification and the artwork together.

  • One record for products and assets

    Live

    Specification and artwork in one versioned record, under one permission model, with one history.

  • Complete change history

    Live

    Every version kept: who changed what, when, and through which door — a person, an import, an API key or an agent. Compare any two versions and restore what you need.

  • Tamper-evident history

    Live

    Each version is hash-chained to the one before. “Verify this workspace” rehashes the full history and reports what it found.

  • E-signatures on approvals

    Live

    Approvals re-authenticate the signer and bind the exact content versions that were signed.

  • Scheduled changes

    Live

    Schedule a change — or a whole product family — to go live at a set time.

  • Deleted records, restorable

    Live

    Deletion is a version too. Find what was removed, by whom, and bring it back.

  • Legal holds and retention

    Live

    Hold records against deletion and set retention. Available through the API.

  • Effective dating

    On the roadmap

    Record when a value is true, not only when it changed — for rate cards, tariffs and “as of” questions.

The history of one product: eight versions listed with author, timestamp, status change and source, and a side panel comparing the price in version 7 and version 8.
History: a price change that arrived through the ERP’s API key, next to the human approval before it. Screens from the running product, with Maison Tête, a fictional hat house, as sample data. Product imagery is AI-generated.
Product information

Product information

The catalogue: families, variants, languages and readiness, edited the way product teams already work.

  • Families and variants

    Live

    Masters and variants with inherited values, per-member provenance and shared-value locking.

  • Languages that tell the truth

    Live

    Fallback chains show which language a value actually came from, and never count a fallback as translated.

  • Readiness per channel and language

    Live

    Completeness scored for each channel and language, with exactly what is still missing.

  • Spreadsheet-style editing

    Live

    Edit many records in a grid. Changes land in drafts; nobody sees them until you publish.

  • Bulk edits that explain themselves

    Live

    Bulk changes refuse live records and say why, row by row. Undo runs as its own job.

  • Imports that dry-run exactly

    Live

    Round-trip a spreadsheet out and back in. The dry run is the same code path as the import, so what you preview is what happens.

  • Your own fields and content types

    Live

    Add a field or a whole content type from the interface, without code.

  • Taxonomies in every language

    Live

    Categories and vocabularies translated alongside the content they classify.

  • Filter and sort by any attribute value

    On the roadmap

    The gap we name openly. Search today is full text with fixed facets: type, status, channel, completeness and access.

  • Units, quantities and currencies

    On the roadmap

    Typed measurements with precision and cross-field validation rules.

  • Changing field types on live data

    On the roadmap

    Creating content types works today. Changing a populated field’s type safely needs a migration engine we have not built yet.

A product record: identity fields in English, German, French and Dutch, a readiness panel showing seven of seven required fields filled, and recent status changes.
A record in review: every language side by side, readiness per channel, and who moved it where. Screens from the running product, with Maison Tête, a fictional hat house, as sample data. Product imagery is AI-generated.
Assets

Assets

Files linked to the products they belong to, not filed beside them.

  • Files stored once

    Live

    Content-addressed storage with de-duplication, for files up to 1 GiB.

  • Previews and renditions

    Live

    Thumbnails, previews, video posters and scrub strips, PDF previews and 720p proxies. A file we cannot render is kept and flagged, never dropped.

  • Collections and boards

    Live

    Personal, shared and rule-based collections that fill themselves. Any collection can be a board, live across browsers.

  • Rights and licences

    Live

    Licence terms, territories and expiry per asset. Publishing warns you when rights have ended.

  • Where is this used?

    Live

    Find every record that links to an asset before you change or remove it.

  • Migration kit

    On the roadmap

    A folder or another DAM’s export, plus a sidecar sheet, imported with its history.

  • Meaning-based and near-duplicate search

    On the roadmap

    Find by what something is, not what it is called.

  • Video publishing

    On the roadmap

    Publish approved video to YouTube and Vimeo from the record.

A campaign collection shown as cards: beach photography of straw hats, each marked Published, with a note that two shots are on a short licence ending in ten days.
A campaign collection. The licence note travels with the shots. Screens from the running product, with Maison Tête, a fictional hat house, as sample data. Product imagery is AI-generated.
Review and approval

Review and approval

Lifecycles and workflows where automation holds no special powers.

  • Lifecycles you design

    Live

    Draft, review, approved, published — or your own states, in a designer that validates them before they go live.

  • Workflows

    Live

    User and automated tasks, timers, branches and escalation. Automation holds no special powers.

  • Annotations on artwork, PDFs and video

    Live

    Mark up images, PDF pages and video time ranges, compare versions side by side, and carry open threads forward.

  • My work

    Live

    One queue for tasks, approvals and the records waiting on you.

  • Access rules as sentences

    Live

    Rules read as plain sentences, and an access checker answers “can this person see that?”

Distribution

Distribution

Only approved, published content leaves the building.

  • Delivery that serves only what is published

    Live

    Shoppers keep seeing the published version while you work on the next draft. Signed file URLs for the CDN.

  • Channels and syndication

    Live

    Publish to channels over SFTP or HTTP, preview exactly what would go out, and handle rejections as events rather than silent failures.

  • Share links and branded portals

    Live

    Guests review and comment without an account, on a phone if they like.

  • Reports and scheduled exports

    Live

    Scheduled deliveries to the people who need them, without a BI project.

  • Marketplace and GS1 mappings

    On the roadmap

    Spreadsheet and filename mappings in; GS1 and marketplace structures out.

A guest line sheet for a retail partner showing five hats, published versions only, with a Download all button.
What a retailer sees from a share link: published versions only, no account needed. Screens from the running product, with Maison Tête, a fictional hat house, as sample data. Product imagery is AI-generated.
AI and agents

AI and agents

Agents work under the rules people already have, and every action is attributed to a person.

  • Governed agent access

    Live

    Connect Claude or any MCP client with per-agent consent, revocable within 30 seconds. Every action is attributed to the person behind it.

  • Proposals

    Live

    An agent proposes a change; a person applies it. Agents cannot apply their own.

  • Vera, the in-app assistant

    Live

    Answers questions about your catalogue within your own permissions. Any change it suggests is a card a person approves. Bring your own model.

  • Claims library

    On the roadmap

    Approved claims as records, matched to the assets that use them.

  • AI actions on assets

    On the roadmap

    Background removal, crops, subtitles and translation, with a cost preview before each run.

  • Governed autonomous agents

    On the roadmap

    Agents with their own triggers that move from dry-run to propose to act as they earn it, with the whole run revertible.

Integration and administration

Integration and administration

An API for everything the interface does, and the controls an administrator expects.

  • A complete API

    Live

    Full OpenAPI description and API keys. Everything the interface does, the API does.

  • Signed webhooks

    Live

    About forty event types, and a workflow step that calls your endpoint.

  • ERP sync with locked fields

    Live

    Idempotent bulk upserts. Fields owned by the ERP are read-only here: “Price comes from ERP — change it there.”

  • Change feed

    Live

    The delivery API tells downstream systems what changed since they last asked.

  • Access reviews

    Live

    Export who can see and do what, as CSV, for the auditor.

  • TypeScript and C# SDKs

    On the roadmap

    With sandbox workspaces and a developer portal.

  • Native ERP connectors and GDSN

    On the roadmap

    Pre-built connectors instead of an API integration.

Limits

Every limit we know about

In a regulated RFP, a website claim becomes a representation. So here is the other half.

  • SearchNo filtering, faceting or sorting by attribute value. Configurable grid columns are display-only.
  • Data modelNo units, quantities or currencies, no cross-field validation rules, and no effective dating. You can create content types, but not yet change a populated field’s type.
  • ScaleOur scale figures were measured at 24 fields per content type and do not transfer to very wide schemas.
  • ChannelsNo marketplace feeds or native ERP connectors; integration runs through the API, webhooks and SFTP/HTTP syndication.
  • IdentityLocal accounts only until Entra ID sign-in ships.
  • ProvenanceThe record proves which file was approved. It does not yet re-read stored files to prove the bytes are unchanged.
  • OperationsNo production customer workspace yet. The first one will be a design partner’s.
  • AssuranceNo SOC 2, no ISO 27001, no CSV/GAMP 5 validation package.
  • AccessNo self-service sign-up. Every workspace is set up by hand.
Questions

Questions buyers ask first

Can I filter and sort by any attribute value?

Not yet. Search is full text with fixed facets — type, status, channel, completeness and access. Attribute-level filtering is on the roadmap and it is the first gap a PIM buyer will notice, so we say it first.

Does Scrivino replace both our PIM and our DAM?

That is what it is built for: products and the files that go with them live in one versioned record, under one permission model. Whether it can replace yours today depends on the limits listed on this page.

Can it connect to our ERP?

Yes, through the API. Idempotent bulk upserts keep products in step, and fields the ERP owns are read-only in Scrivino. There are no pre-built ERP connectors yet.

Does it publish to marketplaces?

It syndicates to channels over SFTP or HTTP and handles rejections as events. Marketplace-specific mappings, such as GS1 or Amazon structures, are on the roadmap.

Which languages does it support?

Content can be in any language, with fallback chains between them. The interface itself is in English.

Can AI agents change our data?

Agents can propose changes; a person applies them. Agents connect with per-agent consent that can be revoked within 30 seconds, and every action is attributed to the person behind it.

Is there single sign-on?

Local accounts work today. Microsoft Entra ID sign-in is in build.

Can we try it ourselves?

There is no self-service sign-up yet: every workspace is set up by hand. Apply as an early adopter and we will walk you through the running product.

Next step

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.