Integrations
Native into Salesforce and Adobe. Ingest from Canva, Figma, Workfront, agencies. Bind it all.
Ingest sources
- Workfront
- Canva
- Figma
- External agency
Source hash · version · author provenance re-signed on intake.
Artefact Graph
Every output bound into one cross-vendor provenance graph · MCP-standard tool definitions.
Salesforce Marketing Cloud
Native Data Extensions · Content Builder · Journey Builder
Adobe GenStudio + C2PA
Content Credentials emission · Q1 2027
HubSpot · Meta · Google · TikTok · LinkedIn · DAMs
Bynder · Frontify · AEM Assets
What it is
We do not replace the execution stack you spent three years buying. We sit on top of it. LaunchSynapse exports natively into Salesforce Marketing Cloud at MVP and Adobe GenStudio next. We ingest from Workfront, Canva, Figma, and your external agencies, and bind every output into one cross-vendor provenance graph. Stack-neutrality is a contractual commitment, not a marketing slogan.
A library of bidirectional connectors to the systems your team already uses. Native objects on the destination side: SFMC Data Extensions, Journey Builder activities, Content Builder assets written with provenance preserved and the SFMC object IDs echoed back into the artefact graph as export-mapping edges. C2PA / Content Credentials emission keeps Adobe-originated assets in their native trust chain while joining ours.
Capabilities
What this surface does
Salesforce Marketing Cloud native
MVP exporter ships native audiences (Data Extensions), content (Content Builder), and journeys (Journey Builder activities). One-way push at MVP, bidirectional sync post-MVP. ISV listing on the Salesforce AppExchange by FY27.
Adobe GenStudio + Content Credentials (C2PA)
Post-MVP exporter via the Adobe GenStudio API. Native C2PA emission so Adobe-originated assets keep their authenticity metadata while joining the cross-vendor chain.
HubSpot · ad platforms · DAMs
Year-2 exporters for HubSpot Marketing Hub, Meta / Google / TikTok / LinkedIn ad consoles, and DAM platforms (Bynder, Frontify, Adobe AEM Assets).
Workfront Proof bidirectional
Approval flows from policy gates appear as Workfront items; approvals propagate back into the ledger. No second system-of-record for marketing ops.
Canva + Figma ingest
Source assets ingested with content-hash + version + author provenance. Re-signed into the cross-vendor chain on intake.
MCP-standard orchestration
Tool definitions are MCP-compatible. Anthropic Claude, OpenAI, and the agent runtime (CrewAI / LangGraph) all consume the same tool surface multi-model from day one through the per-tenant Model Registry.
Proof points
What this means in numbers
≥ 50/min
SFMC export throughput
Sustained journey-activity push (NFR3).
Native objects
On destination side
Data Extensions, Journey Builder, Content Builder not opaque blobs.
Stack-neutral
Contractual commitment
No exclusivity tying you to one execution cloud.
Specifications
Spec map feature requirements + non-functional bar
Mapped to PRD §7 functional requirements and §8 non-functional requirements.
Related surfaces
What this composes with
PS1 the moat primitive
Artefact Graph
Versioned, signed, cross-vendor the system of record for every campaign object.
Read
PS4 the purchase-criterion feature
Evidence Pack
The artefact you hand a regulator. Assembled in seconds, signed by default.
Read
PS2 compliance-as-code
Policy Engine
Compliance-as-code for every live jurisdiction enforced at draft time.
Read
EU AI Act Article 50
Twenty minutes. One conversation. If the outside-counsel-displacement math works, we keep talking. If it doesn't, it's honest and short.