How it works
Six steps from an idea to a post that goes out on Thursday morning. Steps 1–4 happen in the operating panel; steps 5–6 happen on the server without anyone present.
- Connect an account The operator clicks “Connect” for a platform and is sent to that platform's own authorisation page. After granting access, the platform redirects back with an authorisation code, which is exchanged for an access token. The token is stored on the operator's server; the account password is never seen by this tool.
- Write the script A post starts as plain text — the narration for a video, or the copy for a text post. The panel keeps drafts per project so several ideas can be in flight at once.
- Render For video, the script is turned into narration, transcribed for word-level caption timing, and rendered as a 1080×1920 MP4 with captions, transitions and music. For text-first platforms it is composed into image cards plus post copy instead.
- Review and approve The finished item appears in the panel with a preview, the exact caption that will be posted, and the destination account. Nothing moves forward until the operator approves it — an unapproved item stays a draft indefinitely.
- Queue for a time slot Approved items get a target slot — morning, afternoon, evening or night — and join the queue. Daily caps keep the volume reasonable and the mix natural.
- Publish automatically A scheduler on the always-on server wakes up at the slot time, uploads the file through the platform's content API using the stored token, and records the resulting post id. Failures are logged and stop that item rather than retrying into duplicates.
What the panel looks like
The operating panel is password-protected because it spends real render time and posts to live accounts. This is the shape of it:
1 · ScriptDraft text for the next postDone
2 · RenderVoice-over, captions, transitionsDone
3 · ReviewPreview + caption + destinationWaiting for approval
4 · ScheduleSlot: Thursday, morningQueued
5 · PublishContent API uploadPending
HistoryPast posts, ids and errors18 records
Where things run
| Stage | Runs on | Why |
|---|---|---|
| Rendering | Operator's own workstation | Video rendering is CPU-heavy and does not need to be online |
| Queue & scheduler | Small always-on server (KST) | Scheduled posts must fire even when the workstation is off |
| Access tokens | Same server, private volume | Needed at publish time; never leaves that machine |