Shipped means merged and running
Not demoed, not branched. On the local runtime against synthetic data, which is what “built” means everywhere on this site.
In development · founding partners onboarding from Q4 2026
Roadmap & changelog
What shipped, what is being built, and what is only planned.
This is the whole list. It is read from the same content the site is edited from, so it moves when the product moves rather than when someone remembers to update a page.
Most recent shipped entry:PIM backbone direction adopted
The list
Three states, one source.
Shipped3
Merged and running. Dated, because a shipped thing has a date.
PIM backbone direction adopted
Typed attribute storage, versioned attribute definitions, append-only identifier history and an event envelope, adopted as the direction for the product-data core.
Product foundation merged
Product master with variants and identifiers, channel listing readiness, inventory availability and reservations, and the operations workbench — running on the local runtime against synthetic data.
Public website foundation
This site: static Astro on Cloudflare Pages, editable through Keystatic Cloud, with the resource budgets, the link check and the canonical assertions enforced in CI.
In development5
Being built now. No dates: a date here would be a promise.
AI review queue
Suggestion-only. Nothing writes to a catalogue without a person approving it, and every approval is logged.
Documented import contract with staging and preview
Five entities, a published contract, and a staging step so nothing lands in a catalogue unchecked.
EU compliance attributes as readiness rules
EPR registration per market, GPSR responsible person, CN code per variant — as blocking readiness checks rather than free-text attributes.
PIM backbone foundation
Typed attribute storage and versioned definitions, built out from the adopted direction.
Security page controls
The controls listed on the security page, implemented and evidenced one by one.
Planned7
Decided and sequenced, not started. Order can change; founding partners change it.
Billing
Billing is not live. Founding partners are invoiced manually until it is.
Order and inventory sync
Two-way sync, after the read-only path has been proven on real catalogues.
Read-only connectors
First the platforms founding partners actually run on, read-only, before anything writes back.
Reconciliation across shop, marketplaces and ads
When the three disagree, show by how much, line by line, with an audit trail.
Self-serve signup
There is no self-serve trial today; founding partners are onboarded by hand, deliberately.
SOC 2 / ISO 27001
Targeted after the first paying customers. TOVIA holds no certification today and says so on the security page.
Webhook inbox and reconciliation
Inbound events land in an inbox and are reconciled before anything is written back.
How this list is kept
Three rules, enforced by the build.
Planned work carries no date
A date on something that has not started is a promise, and this is a pre-launch company with no right to make one. Order can change; founding partners change it.
The list includes what has not moved
Removing a stalled item would make the roadmap look better and mean less. Items are re-stated, not quietly deleted.
The first two are not conventions: a shipped entry without a date fails the build, a planned entry with one fails the build, and continuous integration warns when the newest shipped entry is more than a fortnight old.
Change the order.
Founding partners decide which connectors and which compliance cases come first. That is the most concrete thing founding access buys.