Clipping Publisher is the internal tool Reku Media uses to run its own social media channels. It takes long-form source video, selects the moments worth keeping, renders them as vertical clips, and — after a person approves each one — publishes them to Reku Media's own connected accounts through the platforms' official APIs.
Every clip travels the same path. Nothing reaches a platform without a person approving it first.
A long-form source video is added to the local library.
Speech is transcribed locally to give the selection step something to read.
Self-contained moments are proposed, each with a start, an end and a reason.
The clip is cut to vertical format with captions and levelled audio.
Automatic checks catch clipped audio, cut-off sentences and framing faults.
A person reviews every clip and either approves it or sends it back with a reason.
Approved clips are uploaded to the chosen account at the scheduled time.
Each platform is connected through its official API. Authorization is granted by the account owner via the platform's own consent screen; access can be revoked there at any time.
The operator signs in to their own TikTok account through Login Kit. Approved clips are then sent to that account with Direct Post, one clip per request, at the time chosen during review. No third-party accounts are involved.
Approved clips are published as Reels to Reku Media's own professional accounts. The tool creates a media container, waits for processing to finish, then publishes it.
Approved clips are uploaded as Shorts to Reku Media's own channels using a resumable upload, with title and description set from the reviewed clip.
Constraints the tool is built around, not features bolted on afterwards.
The tool publishes exclusively to social accounts operated by Reku Media. It is not offered to third parties and manages no one else's accounts or data.
Clips are never published automatically off the back of the editing step. Each one is reviewed and approved by hand before a publish job can even be created.
Video, transcripts and the review database stay on the operator's own machine. Nothing is uploaded except the finished clip that goes to the chosen platform.
Access tokens are held in the operating system's keychain, never in the project database or in source control, and are used only to publish to the account that issued them.
Publish jobs carry an idempotency key, so an interrupted upload resumes instead of producing a second post.
Source video comes from material Reku Media is licensed to clip, under the terms set by whoever supplied it.