Source apps
Start with the app that created the AI content.
Customers do not usually search for a brand first. They search for practical workflows like Seedance to TikTok, Kling AI to YouTube Shorts, Veo to Instagram Reels, Midjourney to Pinterest, or Canva to multiple social platforms.
Choose source
AI video, image, and design tools that need publishing handoff.
Each page explains what the source app creates, what AI PubKit needs, where the content can go, which routes are direct or assisted, and an example publishing package.
A customer can generate a strong Seedance video, but still has to rewrite the caption, title, thumbnail text, hashtags, rights notes, and review checklist for every platform.
Video · China and AsiaKling AIKling AI can create the video asset, but customers still need a clean way to move that asset into platform-specific publishing workflows.
Video · GlobalGoogle VeoA team using Google Veo still needs a practical handoff from the generated video into Shorts, Reels, TikTok, LinkedIn, and CMS workflows.
Video · GlobalRunwayRunway can create the video, but customers still need captions, video metadata, review notes, thumbnail text, and platform-specific versions.
Image and design · GlobalMidjourneyCustomers generate strong Midjourney visuals but still need alt text, Pinterest descriptions, Instagram captions, CMS image notes, rights notes, and platform-specific calls to action.
Design · GlobalCanvaA Canva user may have the finished design but still needs destination-specific captions, alt text, posting notes, CMS context, approval checks, and open app routing outside a single planning tool.
Source app vs destination app
Keep the workflow simple.
A source app creates the content. A destination app is where the content gets published. AI PubKit sits between them and creates the app-ready package.