Respect the product’s complexity
Give teams the tools to express their own product structure. Strong types, relationships, and shared base types make that structure useful.
ManyRows gives teams that build physical products a single source of truth for their product. Our configurable workspace connects product definitions, reviewed changes, and handoff evidence so the next person can understand what was decided and why.

One product. Many connections.
Building a clearer way to work with product data.
A product connects to its parts. Parts connect to revisions and suppliers. One change can affect many records and decisions. We started ManyRows in 2025 to give those connections a dependable home that teams can keep working from.
The name ManyRows refers to the rows in a database or a bill of materials. It’s also a nod to our founder, Row Forsyth: there’s one Row, but he does many things.
ManyRows is an Australian company. We’re building a connected product platform that brings PLM, PIM, and product data change management together around clear product models, meaningful relationships, and the people and AI agents who work with them.
Get in touch
Director & Founder
Click to enlarge A change request brings proposed edits, review, and the decision together. The product record carries the image, specification, supporting evidence and approved revision forward, so the next team has the context it needs.
See more real screensGive teams the tools to express their own product structure. Strong types, relationships, and shared base types make that structure useful.
Keep the proposal, the review, and the approved change together. Teams need to understand how the current product came to be.
Build around APIs, project export, and agent access. Product information should remain useful as teams and their tools evolve.
Have a question about your product model, a workflow to discuss, or feedback to share? Get in touch with the ManyRows team.
ManyRows connects specifications, parts and BOMs with change requests, approved revisions and release evidence. Quality, sourcing and purchasing use those product records; channel workflows prepare reviewed copy, images, prices and CSV handoffs for sales tools.
Engineering and product teams managing parts, specifications and revisions; quality teams reviewing samples and release evidence; and procurement or operations teams coordinating suppliers and handoffs. Industry examples show how the same model supports different physical products.
Agents can help create product types, fields, and relationships, trace change impacts, and prepare updates for review. Connect them through MCP or the REST API. Your team can also work directly in the web workspace without agents.
Yes. Portable project bundles include model definitions and supported record data. Asset files, approval history and workflow evidence have separate exports. The REST API also provides direct access to product data.
Explore the product tour, compare plans, or create a workspace for your team.