Multi-party data, governed by design.
ContainerGrid coordinates OEMs, contractors, recyclers, and offtakers in one workflow. That only works if every party trusts what the others can see. Neutrality isn't just our market position — it's our data architecture.
Three commitments every participant gets.
We don't trade against you
ContainerGrid is an infrastructure layer, not a market participant. We never buy, sell, or broker material — so your commercial data is never our trading advantage.
Each party sees only its role
Role-based access across the chain: program owners see program state, operators see their orders, offtakers see allocated lots. No party sees another's economics.
Program data belongs to the program owner
Operator profile data belongs to the operator. Exports are always available. Leaving the platform means taking your data with you.
The permission model, plainly.
| Program rules & state | Order execution detail | Operator pricing | Lot provenance | Network profiles | |
|---|---|---|---|---|---|
| Program owner (OEM) | ✓ full | ✓ their programs | — (aggregated only) | ✓ | ✓ matched operators |
| Operator / recycler | — (their obligations only) | ✓ their orders | ✓ their own | ✓ their handoffs | ✓ own profile |
| Offtaker / refiner | — | — | — | ✓ allocated lots | — |
| ContainerGrid | ✓ operate & audit | ✓ operate & audit | — no trading use, ever | ✓ | ✓ |
Enterprise questions, answered up front.
Final specifications (hosting regions, auth provider, backup RPO/RTO, encryption detail) are being documented for publication — available today under NDA as part of any security review.
Where is our data hosted?
Is ContainerGrid GDPR-compliant?
How is data encrypted?
How do you handle multi-tenant isolation?
Do you support Catena-X / data-space integration?
Can we run a security assessment?
Diligence welcome.
Request the security review pack — or put your questionnaire straight in front of our engineering team.