Keryx¶
Turn a written post into a short narrated video and proclaim it across social platforms — on demand and on a schedule.
“KEH-riks” · /ˈkɛrɪks/ · from Greek κῆρυξ, “herald” · the content-marketing automation for phpboyscout.uk
Status — generation pipeline works; posting + studio landing
The CLI runs the full reel pipeline (storyboard → VO + music → cards/cover →
assembled mp4, or one-pass with reel make) and
composes per-platform social copy; the platform publishers and the web studio
are in active development. What is deliberately absent, and what looks configurable
but is not, is on What Keryx does not do.
What Keryx does¶
It builds a 9:16 reel from a storyboard — text cards over generated or uploaded imagery, voice-clone narration, and a tone-matched music bed — then publishes it to Instagram, YouTube, TikTok and LinkedIn. It runs interactively from the CLI or the local web studio, and unattended from GitLab scheduled pipelines. It's built on go-tool-base, ships as a single Go binary, and keeps no state of its own — your project's git repo owns the reels, config, and schedule.
-
Never used Keryx? Render a real reel from nothing in about fifteen minutes, with no API keys and nothing to pay for.
-
Make a reel, compose social copy, post on demand, schedule unattended runs.
-
Every command, flag, configuration key and environment variable — what it defaults to, and what happens when it is wrong.
-
Why it works this way — the authoring loop, themes, pluggable providers, and what Keryx deliberately does not do.
-
Why Keryx, the name, status and roadmap.
-
Ways of working, the UI mockup, and how the pieces fit.
Further reading¶
Everything written about the estate, including the curated guides, is on the blog.
Ask phpbotscout
He answers questions about the projects over on the Discord, citing the docs where they already cover it, and offering to raise an issue where they don't. Bring a bug, an idea, or a questionable engineering decision.