Scope. waypost is the console Back Road Creative runs its own publishing operation on. The source is not yet public and there is no installer here; waypost is available through a studio engagement.
Open the read-only demo → — a fixed fictional console for a made-up brand, frozen at 2026-09-01.
One console over the pipelines you already run
A working creator operation is not one tool. It is a video pipeline that turns a drive of footage into scheduled uploads, a set of photo tools, the SEO and comment work that follows every publish, and the jobs that keep all of it moving on a calendar. Each piece can run headless on its own; what goes missing is the one place to see and steer them together.
waypost is that place: a web console you run on your own machine, in front of the pipelines you already operate. It does not replace them and it holds no second copy of their state — it starts their runs, watches their progress, and surfaces the follow-up work they generate.
What it replaces
The hosted social schedulers. Each of them holds your calendar, your captions and your platform credentials on somebody else’s server, charges per seat and per channel, and stops at the upload — the cutting, grading, redaction and metadata that come before it are still your problem. waypost owns the whole chain from drive to published post and posts to YouTube, TikTok, Instagram and Facebook from the same queue, on a machine you control.
Mechanism
- Video: drive → review gate → publish queue. Point it at a drive of footage and it runs the pipeline that cuts, encodes and titles long-form videos and shorts. Every run stops at a review gate — the same gate the command line offers — and nothing reaches a platform until an operator passes it. Approved output lands in a publish queue with scheduled slots, one calendar per brand.
- Photo: ingest → develop. Card or folder in, developed and graded stills out, run from the same surface as the video work.
- SEO and comments. The titles, descriptions and comment follow-up each publish generates, managed where the publishes happen.
- Jobs and schedules. Recurring work runs on a calendar the console owns, so nothing depends on somebody remembering to start it.
- A console that fits a phone browser. The review gate and the queue are usable from a phone, so an operator can pass a run or move a slot without sitting at the machine that runs it.
- A failure webhook. A failed run or a missed slot posts to a webhook the operator configures, so the console never has to be watched to be trusted.
Each brand gets its own tab, so one console serves every channel an operator runs without mixing their queues, credentials or schedules.
The tools underneath
waypost fronts four of the studio’s open tools, each of which stands on its own: keycut makes the cuts, redactcam blurs faces and plates before an encode, pycube-lut applies the grade, and sun-track tells the photo side when the light was golden. The console adds the queue, the gate and the calendar; it does not add a second copy of any of them.
driftless is not one of them. It is a different product — the scheduling and status console for delivery work: portfolios, programs and projects. waypost schedules posts; driftless schedules projects. The two share a studio and a design habit, not a codebase or a queue.
Built to be rebuilt
waypost runs as a container on the operator’s own machine, with its state on a volume outside the container, so tearing the container down and rebuilding it — the normal life of a self-hosted tool — loses nothing. Backup and restore scripts ship with it and are verified against a real restore; putting the backup on a nightly cron is a step the operator takes at setup. Nothing about the operation lives only inside a running process.
Who it is for
A creator or small studio already running its own publishing pipeline — comfortable operating real tools, tired of steering them from six terminals — who wants one interface over the work without handing the operation to a hosted platform.
Where it stands
waypost fronts Back Road Creative’s live publishing operation. The source is not yet public, there is no packaged release, and nothing about one is promised or dated here. To run your own operation through it, get in touch and ask.
Documentation
waypost’s documentation is not yet public: it travels with the console itself, which is delivered and set up through a studio engagement, and this page is the public reference until the source and its README are published. What ships with the console:
- Operator runbook — first run, adding a brand tab, connecting each platform’s credentials, and the review-gate workflow from a phone.
- Backup and restore — the scripts, the restore drill that verifies them, and the cron line for a nightly backup.
- Webhook setup — the failure payload and where to point it.
- Tool manuals — the four open tools above document themselves in their own repositories; the console’s docs cover only what it adds over them.