EXA26
— Send data to a third party —
Customer-to-Customer Sharing
Two of your SaaS customers want to share data — today's API integrations grant full read access. Polymonial gives field-level partnerships.
The problem to solve
Two SaaS customers want to share data — CRM to marketing-automation, ITSM to project-tracker, ERP to CRM. Today each integration grants the other full read access on the agreed objects. Customers want field-level 'share these 4 fields, not these 6'; the platforms force coarser permissions. The platform that adds true field-level partnerships first becomes the default integration hub.
The solution it enables
Polymonial schema-wraps the inter-customer API. Each side defines what it'll share via a schema; the other side queries against the schema. Records sealed; only matching/agreed fields decrypt at the other end. Lets your platform offer 'tenant-to-tenant data partnerships' as a feature that customers control field-by-field — not a coarse OAuth scope they have to over-grant.
What it looks like
A B2B SaaS hub has 14,000 tenants, 2,300 of which have inter-tenant data-sharing enabled. Today: data-sharing is per-object scope; customers complain about over-sharing risk. After Polymonial: the hub ships schema-wrapped sharing. A retailer-tenant defines its 'shared inventory' schema with brand-tenants — quantity available, lead time, stock location. The brand-tenant defines its schema — order volume, forecast, NPI launches. Each side sees only what their schema permits at the other end.
“Your tenants share data. Your tenants' privacy survives the share.”
Who’s this for you?
We have this problem.
Your organisation needs this for its own data, product or programme of work.
We deliver this for clients.
A consultancy, integrator, service provider, industry programme or technology vendor.