Features
Everything below is part of the working tool. It is deliberately narrow: produce a post, review it, publish it on time, and keep a record of what went out.
Production
Script to video
Takes a written script and renders a vertical 1080×1920 video with scene transitions and background music. Rendering happens on the operator's own machine.
Voice-over
Narration is generated from the script, then aligned to the timeline so scene changes land on sentence boundaries instead of mid-word.
Burned-in captions
Speech is transcribed with word-level timing and rendered as on-screen captions, which is what short-form feeds reward when watched muted.
Image cards
For text-first surfaces the same idea is composed into a set of image cards with matching post copy, so one concept ships in more than one format.
Review before anything goes out
Nothing publishes straight off the render. Each finished item lands in the panel as a draft with a preview, the caption text, and the destination account. It only enters the publish queue after the operator approves it. Anything still in draft simply never posts.
Scheduling
Time-of-day slots
Posts are assigned to morning / afternoon / evening / night slots and matched to whichever slot suits the content, rather than all firing at once.
Server-side queue
The queue runs on a small always-on server in the KST timezone, so scheduled posts still go out when the workstation that rendered them is switched off.
Pacing limits
Caps on how many posts of each kind may go out per day, so an account is never flooded and the mix stays mostly ordinary content.
Per-account separation
Each connected account keeps its own credentials, queue and history. Content prepared for one account can never publish to another.
Publishing & record-keeping
- Each platform is connected once through its official OAuth screen; access tokens are stored on the operator's server and refreshed automatically. Account passwords are never requested or stored.
- Uploads use each platform's documented content API. There is no headless browser, no scraping and no simulated user input anywhere in the publishing path.
- Every attempt is logged with its timestamp, destination, resulting post id and any API error, so a failed publish is visible rather than silent.
- Failures stop that item instead of retrying blindly, which keeps a transient API error from turning into duplicate posts.
What it deliberately does not do
- No public sign-up, no accounts for other people, no handling of anyone else's social data.
- No follow/unfollow, bulk commenting, view inflation or other engagement automation.
- No reposting of other creators' content — everything published is produced by the operator.