Choose
Select a provider inside the Forge Flow or delivery session.
INTEGRATIONS
Your tools remain the destination. Forge handles the handoff.
Forge is being built to connect the services already used to edit, publish and deliver media. Production connections will remain user-initiated and limited to the work the user asks Forge to perform.
CONNECTION MODEL
The connection model is explicit by design.
Authorize
Review the provider’s consent screen and grant the requested access.
Run
Forge uses that access for the user-selected import, transfer or delivery.
Disconnect
Remove the connection from Forge or revoke it directly with the provider.
DIRECTORY
Connection roadmap
No connection listed here should be assumed available until it is marked Ready on the product-status page.
Editing
Lightroom Classic
Create or open the correct catalog and hand off verified media without rebuilding the folder path by hand.
In developmentLocal companion integration
Publishing
DVIDS
Prepare selected media with DVIDS metadata, standardized fields and VIRIN-aware delivery from the Forge review interface.
In developmentAuthorized upload workflow
Delivery
Dropbox
Send approved files to the configured Dropbox destination without browsing back through the shoot structure.
PlannedOAuth 2.0
Video delivery
Vimeo
Upload selected video, apply delivery metadata and return the resulting destination to the Forge session.
RoadmapOAuth 2.0
Cloud delivery
Google Drive
Deliver selected files to a user-authorized Drive location using only the access required for that action.
PlannedOAuth 2.0
Video editing
DaVinci Resolve
Move organized video into the next editing stage while keeping the Forge Flow as the source of workflow truth.
RoadmapLocal workflow handoff
DATA USE
Provider access follows the task.
Forge does not sell connected-account data, use it for advertising or use it to train general-purpose AI models.