Built on the SDT Engine.
by Cloud Maven
The AppExchange-listed Salesforce plugin built on the SDT Engine. The strongest TPI proof point in the ecosystem.
Cloud Maven built Secure File Transport for Salesforce on the Botdoc SDT Engine. The product is listed on the Salesforce AppExchange and is curated there as Powered by Botdoc, a third-party attribution we did not pick for ourselves.
Salesforce customers use it to move sensitive customer documents in and out of Salesforce without standing up a separate file-transfer vendor, without asking their customers to log into another portal, and without writing the secure transport layer themselves.
This is the cleanest example of the TPI model. Cloud Maven brought the Salesforce expertise and the customer relationships. Botdoc supplied the SDT Engine. The result is a product that runs as a Cloud Maven product, lists on AppExchange under Cloud Maven, and ships outcomes Cloud Maven publishes under their own name.
Before SDT, a Salesforce ISV that wanted to ship a secure file transport feature had to either embed a third-party portal (and inherit the registration drop-off) or build secure transport in-house (and inherit the compliance maintenance forever). Neither option lets a Salesforce-focused partner stay focused on Salesforce.
The SDT Engine API let Cloud Maven ship the feature without becoming a transport company. They kept their identity. The transport layer became a dependency, not a second product line.
Cloud Maven-published outcomes for customers running Secure File Transport for Salesforce.