Record-keeping infrastructure for your business

One ID. One history. Shared by everyone involved.

ioxTrace gives every product, shipment, machine and document your software handles one permanent ID and one history, shared with the companies you choose. Finding an affected batch takes minutes, not days. A dispute becomes a lookup. An audit needs no phone calls.

Book a demo See it work

Built for software teams · REST API · Python SDK · MCP

Everything in your business has a history. ioxTrace keeps it in one record. The people you choose can check it. No one can quietly change it.

What changes when you have it.

Start from the problem you have.

Not building it yourself? A software provider can build on ioxTrace for you. Ask for your own account, and your records stay yours whoever builds the application. Or send us your scenario.

It sits under what you already run.

A database shows how things are today. An audit log lists what changed. ioxTrace does both, and adds an ID that works across companies, proof that nothing was edited, and sharing you control. Your application keeps the screens, the workflows and the decisions.

WHAT YOU ALREADY RUNTHE PEOPLE YOU ALLOW Your applicationYour databasePartner systemsAI agents PartnersAuthoritiesCustomersAuditors IDs · history · proof · access WHAT YOU ALREADY RUNTHE PEOPLE YOU ALLOW Your applicationYour databasePartner systemsAI agents PartnersAuthoritiesCustomersAuditors IDs · history · proof · access

Standard ways inA REST API, a Python SDK and MCP tools for AI agents.

Built to be checkedReceipts and exports that the people you allow can check on their own.

No migrationKeep your database. Store the ioxTrace ID next to your own.

Start small. Add as you go.

  1. HoursIdentifyOne ID across your systems.
  2. DaysRememberEvery change kept from that day on.
  3. 1–2 weeksIdentify, with linksWhat is connected to what.
  4. 2–4 weeksProve and ShareSealed documents and access you control.
  5. From thereShare, in syncOther systems told of every change, and AI-agent approvals on record.

One example

A bad ingredient turns up. Which shelves is it on?

Today

  • The supplier has one list. The factory has another. The stores have a third.
  • The lists don’t match, so nobody can say for sure.
  • Everything gets pulled, just in case.

With ioxTrace

  • The ingredient, every batch made from it and every delivery share one record.
  • You follow it forward in minutes and pull only what is affected.
  • Later, you can show exactly what you knew, and when.

If a supplier keeps part of the chain private, the answer says so. A recall never looks complete when it is not.

Here the record was an ingredient. It could as easily be a machine, a shipment or a certificate.

See it work.

Pick a story. Each has four small cases to solve, using nothing but the record.

Identify

What did we know, and when?

Your move

    The stories, names and figures here are made up to show the product.

    Bring your own scenario. We run it the same way.Book a demo

    Any record that matters gets asked four questions.

    A regulator asks them. So does a customer, a partner, and anyone checking what an AI agent did.

    1. What is this?

      One ID that stays the same in every system and every company.

      Answered by Identify
    2. What happened to it?

      Every change is kept, so you can see it as it was on any past day.

      Answered by Remember
    3. Who says so?

      Every entry names who made it, whether a person or an AI agent.

      Answered by Prove
    4. Can we still verify it later?

      Every document is sealed when it is stored. Edit it later, and it shows.

      Answered by Prove

    It does four jobs.

    Identify, Remember and Prove answer the four questions. Share decides who else may ask. Everything else stays in your application.

    1 Identify

    One permanent ID per item.

    So two companies never argue about which item they mean.

    • Never reused
    • Your own product codes and serial numbers still point to it
    • Two records for one thing? Merge them. Old IDs still work
    • Records link to each other: what it was made from, what it went into

    2 Remember

    Every change is kept.

    So “what did we know in March?” has one answer.

    • Nothing is overwritten
    • Rewind any record to any past date
    • Each event and reading carries who, when and where
    • A change across several records is saved whole, or not at all

    3 Prove

    Anyone you allow can check it.

    So nobody has to take your word for it.

    • Every document is sealed with a digital fingerprint
    • Edit it later and the fingerprint no longer matches
    • The people you allow can check a record without calling you
    • AI agents propose and people approve. Both go on the record

    4 Share

    Only what you allow.

    So each partner gets what they need and nothing else.

    • Each company’s records are kept apart
    • You choose who sees what, down to a single field
    • Every view is logged
    • Your other systems are told as soon as a record changes

    Context and evidence for every AI agent.

    Picture a company that designs, makes and sells motion-control devices. Its AI agents work in support, quality, production, purchasing and sales. Its systems write to ioxTrace once, so every agent reads one record and none holds the keys to a system.

    Today

    5 agents8 systems

    40 connections, 40 sets of keys

    With ioxTrace
    ioxTrace

    5 agents8 systems

    13 connections, one record

    1. Support inbox

      Customer email: “It stalls in the cold.”

    2. Support agent

      Reads: Order · Factory test · Firmware version

      Likely cause: driver board lot D-118.

      Kept as its conclusion, with the three records it read.

    3. Quality agent

      Reads: Every unit built with lot D-118 · Test results · Support’s conclusion

      212 units carry this lot. 38 went to cold regions.

    4. Production agent

      Reads: Quality’s finding · Line 2 schedule

      Proposes holding 60 units on line 2.

      Production lead approves, 10:20

    5. Purchasing agent

      Reads: Supplier certificate, sealed

      The certificate rates the board to 0 °C. Our specification says −10 °C.

    6. Sales agent

      Reads: Orders · Dealers · Shipments

      Proposes replacement boards for 38 customers.

      Head of support approves, 08:35

    Chief executive

    “Why did we replace 38 units?”

    The record answers in one view: who said what, based on what, and when.

    • Connect once.Each system writes its events once. Each agent reads one record.
    • No keys to hand out.Agents do not log in to your systems. Each acts under its own identity and sees only what you grant, and every read is logged.
    • Agent work becomes record.What an agent concludes is kept with what it read, so the next agent builds on it and you can replay any decision.

    Stays in your application: the agent, its tools, its prompts and its memory. This story is made up to show the product.

    See it in your industry.

    The same four jobs, applied to different problems.

    The lift outlives three maintenance contracts. Its history should too.

    A contractor maintains the lifts in an office tower. When the contract changes hands, the service history usually doesn’t.

    A complete history at handover, and a clear answer when a failure is disputed.

    • IdentifyEvery lift gets one permanent ID that survives a change of contractor, system or owner.
    • RememberEach inspection, repair and reading is kept with who did it, when and where.
    • ProveInspection reports and photos are sealed, so nobody can quietly edit them later.
    • ShareThe building owner, the insurer and the next contractor each see what they are granted.

    Stays in your application: work orders, scheduling, service levels and technician assignment.

    Six more things to build on it.

    • Registries and permitsWho issued it, and whether it still holds.
    • Product passportsOne record under every passport. See the jacket
    • Cold-chain monitoringEvery reading kept with the batch it belongs to.
    • Inspection disputesWhat the inspector saw, sealed on the day.
    • Loyalty balancesOne balance every branch reads, spent once.
    • Digital goodsWho owns it now, and who owned it before.

    Under every product passport, one record.

    Picture a fashion brand that makes 12,000 pieces of one jacket. Each piece needs a Digital Product Passport that still answers in seven years, to shoppers, authorities, repairers and recyclers. The passport page is the part people see. ioxTrace keeps the record under it.

    Padded jacket

    Style 4410 · Size M
    Piece 8,417 of 12,000

    ioxTrace IDJ4C7W-2MX9E

    Sewn in at the factory

    1. One code for every reader.The label is the same for all. What each reader sees is set on the record.
    2. One ID per piece.Not one per style. It stays with the jacket after the price tag is cut off.
    3. Nothing to reprint.New facts are added to the record. The label never changes.

    One jacket, seven years

    1. Before the sale

      Made

      Each supplier adds its own step, once.

      • Fibre supplier, adds

        Recycled polyester, lot R-2291, with its certificate.

      • Mill, adds

        Woven and dyed. The chemical test report is sealed.

      • Factory, adds

        Cut and sewn: 12,000 pieces, one ID each.

    2. On sale

      Sold

      You publish. Others check.

      • You, the brand, adds

        Publish 12,000 passports from the record in one step.

      • Authority, reads

        Asks what “recycled” rests on. Reads the certificate, sealed on the day it arrived.

      • Shopper, reads

        Scans the label in the shop. Reads fibre, care and where it was made.

    3. Years 1 to 7

      Worn

      The record keeps growing.

      • Repair partner , adds

        Replaces the zip and adds the repair.

      • Resale partner , adds

        Checks the piece and its repairs, then adds the resale.

      • Recycler , reads

        Reads fibres and trims, and sorts the jacket for recycling.

    Same code. Different answers.

    An example of what each reader is granted.

    ShopperAuthorityRepairerResellerRecycler
    Fibre and careYesYesYesYesYes
    Where it was madeYesYesNoYesNo
    Parts and trimsNoYesYesNoYes
    Repairs and resaleYesNoYesYesNo
    Certificates and test reportsNoYesNoNoNo
    Suppliers at every tierNoYesNoNoNo

    You see everything a supplier writes on your record, with their name on it. You see their own records and documents only when they share them, and you are told when an answer is partial. Each supplier sees only its own step. You set each grant, and you can change it when the rules change.

    • Suppliers write once.Each supplier adds its own step and its own evidence. You stop collecting spreadsheets every season.
    • Claims come with their evidence.Each claim is kept with who made it, when, and the document behind it.
    • Rules change. The record stays.When a passport rule adds a field, you change what the page shows. The history under it stays as written.

    Who builds the passport page? Your own team or your passport provider. Either way it reads from ioxTrace. Stays with you: design, sourcing, your shop and the page itself. This story is made up to show the product.

    From the supplier’s side

    A supplier with its own account keeps one record and decides who reads it.

    One certificate. Three customers.

    An example of what each customer is granted, and what it then sees.

    • Brand AThe whole certificateEverything, and each renewal
    • Brand BNumber and expiry, until JuneThose two fields, until June
    • Brand CNothingNot found

    Customers cannot see each other. A hidden record answers like one that does not exist.

    • Enter it once.Register a facility, a certificate or a batch once. Share that same record with each customer.
    • Renew it once.Renew or withdraw a certificate, and every customer you shared it with sees the change and is told.
    • The rest stays yours.Your other records, your documents and your other customers stay hidden unless you share them.

    Written per customer: a step you add to a customer’s own product. It carries your name. They can dispute it, but not edit it. This example is made up to show the product.

    Built for the teams that build.

    ioxTrace is infrastructure. You build the application on top.

    Not building it yourself? A software provider can build on ioxTrace for you. Ask for your own account, and your records stay yours whoever builds the application. Or send us your scenario.

    Who builds on it

    • Software companiesTraceability, compliance, inspection and asset applications that several companies share.
    • Enterprise platform teamsOne shared record across business units and partners, so you stop wiring every system to every other.
    • Labs, certifiers and inspectorsResults that the people you allow can check on their own.
    • Teams deploying AI agentsOne record their agents read for context and evidence, with every proposal, approval and action kept.
    • Platforms and marketplacesPartners stay in sync and see only what you grant.
    • Registries and public bodiesLong-lived records that authorities can audit.

    We ran four industries on it, from first record to final audit.

    269 checks. All passed.

    By industry

    • Fashion: supply chain and resale75 passed
    • Food and grocery: supply chain and recall93 passed
    • Logistics: mobility and delivery62 passed
    • Professional services39 passed

    Each check is a step a real team would take: trace a batch to its source, catch an edited certificate, stop an agent approving itself. Each run plays out a whole scenario on ioxTrace and checks every step on the way. Also validated for personal finance, industrial assets and digital goods.

    Book a demo

    What was checked

    • A batch traced to its source
    • Recall, forwards and backwards
    • Supplier evidence
    • Tampered certificates caught
    • Handover between companies
    • Access for a stated purpose
    • Exports a recipient can check
    • AI-agent approvals
    • Self-approval blocked
    • Rewind to a past date
    • Duplicates merged
    • Other systems kept in sync

    Straight answers.

    What counts as a record?

    Anything you need to keep track of: a product, a machine, a shipment, a batch, a certificate. ioxTrace gives each one an ID and a history.

    Who is it for?

    Teams that build software used by more than one company: traceability, inspection, compliance, asset and AI-agent applications. You build the application. ioxTrace keeps the record underneath.

    Do we use it ourselves or through a software provider?

    Either. ioxTrace is infrastructure, so someone builds the application on top: your own developers or a provider. Hold your own account: your provider works with keys you issue, and you can change provider without moving your records.

    Is it a blockchain?

    No. There is no chain, no token and no consortium to join. You get a standard API and signed receipts that the people you allow can check.

    Is it a product passport or traceability service?

    No. It is the layer those services are built on. Passport, recall, inspection and asset applications all use the same building blocks.

    Does it replace our database or our application?

    No. You keep both. ioxTrace sits underneath and keeps the identity, the history and the proof. You store its ID next to your own data.

    How is it different from a database or an audit log?

    A database shows how things are today. An audit log lists what changed. ioxTrace does both and adds three things: an ID that works across companies, proof that nothing was edited, and sharing you control.

    How is it different from a data warehouse?

    A warehouse copies data so you can analyse it. ioxTrace keeps what happened to each item: who recorded what, when, with the document sealed and the people allowed to see it. One is for reports. The other is for showing someone else what is on record.

    Who can see our data?

    Only the people you allow. Each company’s records are kept apart. You grant access by partner, by purpose and by field, and every view is logged.

    What do we see of a supplier’s data?

    Everything a supplier writes on your record, with their name on it. Their own records and documents only when they share them. When part of an answer is withheld, you are told it is partial.

    What exactly does ioxTrace prove?

    Who recorded what, when, and that nothing has changed since. It does not decide whether a claim is true. That judgement, like your policies and decisions, stays with you.

    Can our AI agents use it?

    Yes. An agent reads records for context and evidence, follows changes and submits actions for a person to approve. It sees only what you grant. The agent itself, its tools and its memory stay in your application.

    Why not give our AI agents access to our systems directly?

    Then each agent holds a key to each system, and what it read is hard to reconstruct later. With ioxTrace each agent has one identity and one place to read, sees only what you grant, and its reads and conclusions go on the record.

    How long does integration take?

    You can issue your first IDs within hours, then add history, links and proof over the following weeks. Your existing systems stay in place throughout.

    How is it priced?

    Plans are sized by capacity: request rate, keys, team size, workspaces and evidence storage. We don’t charge per product or per scan. Send us your scenario and we size a plan with you.

    Bring your hardest scenario.

    Send us the question your current systems cannot answer. We run it on ioxTrace and walk you through the result, record by record.

    1. Tell us what you need to trace
    2. We model it on ioxTrace with you
    3. You see it answered, live

    Tell us your scenario

    What do you need it for?

    Pick the closest one. We go into detail on the call.

    Tell us about your team.

    Industry

    Who will build on it? Optional

    Who should we talk to?
    Add a note

    We only use these details to arrange your demo.

    1. People forget. Systems change.

      With ioxTrace, your business always remembers.

    2. Every product you make, every shipment you send, every decision you take is written down as it happens, with who did it.

    3. Every action is recorded. You never have to ask anyone what happened.

    4. Records are never overwritten. Go back to any day and see how things stood.

    5. Nothing can change without a trace. You know who changed what, and when.

    6. Your team, your partners and your AI agents read from the same memory every day, and only what you allow.

    7. the permanent memory of your business.