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 on the SDT Engine. Cloud Maven brought the Salesforce expertise and the customer relationships. Botdoc supplied the SDT Engine and the patented transport architecture underneath. The result is a product that runs as a Cloud Maven product, lists on the Salesforce AppExchange under Cloud Maven, and ships outcomes Cloud Maven publishes under their own name, with the third-party-curated "Powered by Botdoc" attribution making the underlying technology visible without diluting the partner brand.
Before SDT, a Salesforce ISV that wanted to ship a secure file transport feature inside their AppExchange listing had to pick between two equally unappealing paths. Embed a third-party portal product and inherit the registration drop-off that comes with every customer-facing portal experience. Or build secure transport in-house and inherit the compliance maintenance forever, including the patching, the SOC 2 attestation work, and the never-ending email-gateway integrations every regulated customer asks about during procurement.
The SDT Engine API let Cloud Maven ship the feature without becoming a transport company. They kept their identity as a Salesforce specialist. The transport layer became a dependency consumed through one API surface rather than a second product line that would have required a separate engineering team and a separate compliance posture to operate in parallel with the Salesforce-focused work.
Building Secure File Transport for Salesforce on the SDT Engine API produced five outcomes for Cloud Maven and their customers. Each maps to a specific capability the SDT Engine exposes natively. The same pattern repeats across the other TPI builds (Edward Jones SDX, VedaPointe.Send for EPIC) and is the structural reason TPI partners can ship enterprise-grade transport without becoming enterprise-grade transport companies.
Cloud Maven publishes four customer-outcome metrics for Salesforce organizations running Secure File Transport for Salesforce in production. The four metrics together describe what removing the secure-file-transfer friction does to a typical document-heavy Salesforce workflow: fewer documents go missing in the email-attachment workflow that gets replaced, customer-facing turnaround speeds up because there is no portal registration drop-off in the recipient path, manual follow-ups drop because the audit trail is automatic and recipient-visible, and the compliance-exception rate falls because the transport layer is the compliance layer rather than a separate control bolted on top of an unencrypted file-share or email path.