Partner Journey
What an integration gives your customers and how it goes live, explained without code.
This page is for product, sales, and project leads. If you're deciding whether to build an integration, start here. Developers go straight to Installation.
What your customers get
Your platform shows up inside CI HUB's plugins (add-ons) for 30+ apps, such as Adobe InDesign, Photoshop, Microsoft 365, Figma, and Canva. That puts your content in front of CI HUB's 2,200+ corporate customers.
Your customers log in with their account on your platform, then browse, search, and place their assets without leaving the app they work in. Your access rules and metadata carry through, so people only see what they're allowed to see. If your integration supports upload, they can also save files back to your platform.
This works for any system that stores enterprise content: DAM, MAM, PIM, CRM, or cloud storage. More than 70 systems already use the SDK, including Sitecore, Adobe Experience Manager, Bynder, and Frontify.
You don't host the integration. CI HUB runs it on its own servers.
What you need on your side
- A free CI HUB Sales Club membership. Apply with the Sales Club Registration form.
- A CI HUB Integration SDK license. Write to sales@ci-hub.com.
- A developer who knows TypeScript or JavaScript and your platform's API.
Your developers can install the SDK and build locally before the membership and license are in place. You need both before you submit.
The journey at a glance
Stage is CI HUB's test environment. Production is the live environment your customers use.
Step by step
Build locally
- Who
- You
- Done when
- Your integration works on your developers' machines.
Your developers install the SDK and build the integration on their own machine. The SDK Workbench, a local test tool, lets them try every part the way the CI HUB plugins will use it.
Submit
- Who
- You
- Done when
- You have a submission ID and a confirmation email.
Your developers submit the integration with one command (see the CLI reference). The same tool shows the status and results of every version you've submitted.
Review
- Who
- CI HUB
- Done when
- You get an email saying the integration is approved.
CI HUB reviews the submission and emails the result: approved, or rejected with feedback. After a rejection, your developers address the feedback and submit again.
Test on stage
- Who
- You and CI HUB
- Done when
- You've confirmed the integration works on stage.
CI HUB deploys the approved integration to its stage server. You test it there before it reaches your customers.
Go live
- Who
- You and CI HUB
- Done when
- You get an email saying the integration is live.
- Contact
- integration@ci-hub.com
Email integration@ci-hub.com to request the production release. CI HUB deploys the integration to production and lets you know when it's live.
Updates
Every later version takes the same path: build, submit, review, test on stage, then request the production release.