The problem it solves
A lot of what a creator does is not creative work. It is release work.
The video went out to members on Tuesday and has to reach everyone else on Friday. The stream ended and now the clip has to go to four places. The program aired at eight and the write-up should follow at nine.
None of that needs your judgement. It needs someone to remember, and to be awake.
That is the whole idea. You describe the rhythm once, and Tublish keeps it.
Three things it does
Autopilot is not one feature so much as one promise kept three ways.
First, rules.
You publish something once and say where it goes next, and how long afterwards. Members first, everyone else a week later. The stream today, the highlights tomorrow.
A rule is not a scheduled post. It is a standing instruction, and it holds for everything you make from then on - which is why it reads back to you as one plain sentence: when I publish an article, three days later, send it to Discord.
You can also give it a time of day instead of a gap. If you write at midnight, "three days later" means posting at midnight forever; "at nine in the morning" is usually the thing you actually meant.
And when one particular thing should not go anywhere, there is a Not this one switch on the screen where you publish it. It only turns off what has not started - anything already waiting stays visible, and you can still cancel that yourself.
Second, a library that keeps working.
Your back catalog is new to most of the people following you now, because they were not there when it went out.
Put things worth showing again on a shelf, set a rhythm, and Autopilot takes one each turn - always the one that has waited longest, so everything gets its turn before anything comes round a second time.
Third, live panels.
A panel on your website showing something current - a score, a total, a standing, a count - that refreshes on its own.
You give it an address to read from and point at the numbers you want, and it keeps them honest without you touching the page.
And two screens that let you check it
Handing your publishing to a machine is only reasonable if you can see what the machine is about to do, and what it already did.
So there are two more screens, and they are not extras.
What's waiting lists everything queued, when it goes, where, and which rule decided it. If a rule is quietly wrong, this is the screen where you notice - and anything on it can be called back before it leaves.
The Actions Log is the other half: what went out, where, when, and what failed and why. It carries your own changes too, so "I published and nothing was sent" always has an answer written down somewhere.
How it works
You set it up once, on the Space it belongs to.
Pick what sets it off, pick where the result goes, pick the gap in between. Then leave it.
Everything runs on Tublish's own clock, not in your browser.
That matters more than it sounds: your laptop can be shut, your phone can be off, and the thing still goes out at the minute you asked for.
For a live panel, Tublish reads your source on a schedule and remembers the answer. The page your visitors open shows the remembered one.
So their browsers never wait on somebody else's server, and never get seen by it. If that server has a bad afternoon, your site shows the last good number instead of an error.
What it deliberately does not do
It does not write anything. No generated captions, no invented titles, nothing dressed up as you.
It does not post to a platform you have not connected yourself.
And the library will not send the same thing to a place that keeps everything forever - your own blog, for instance. Sending a post to Discord again is how anyone sees it at all; publishing the same article to your blog again just puts a duplicate on it. Those places are simply not offered.
There is one more thing it will not do, and it is the important one: it will not pretend a small shelf is a big one.
Two things on a daily rhythm means each one comes back every other day, which reads as spam to anybody watching. The screen works that number out while you are choosing and tells you when it is too short. It warns you rather than stopping you - but it will not let you build that by accident.
Questions people ask
Will it look like a robot posted it?
Only if you set it up like one. Autopilot sends what you wrote, to places you chose, on a rhythm you picked. The tell for automation is not timing - it is sameness, and that is a choice you make when you fill the library.
What happens if my source goes down?
The panel keeps showing the last value it read, and quietly tries again on its next turn. Nothing breaks on your site, and no visitor sees an error message meant for you.
What can I actually put in a live panel?
Anything that answers a question your audience keeps asking. A current total, a rank, a countdown, a score, a running tally. If a number changes and people care about it, it belongs there.
The fastest it will look is every fifteen minutes, which is more than fast enough for a number on a web page.
Do I need to be technical?
For rules and for the library, no. For a live panel you need an address to read from, and some services ask you to make a key first - the same paste-it-here shape as connecting a platform, with a guide beside it.
Can I turn it off?
At any moment. A rule can be paused, the library's rhythm has an off switch, and a panel can stop refreshing - and nothing you already published is touched.
Autopilot has no memory you cannot see, and nothing it does is missing from the log.
Which plan is it on?
MAX. It is the reason MAX exists - every smaller plan is still one person at a desk deciding when to press send.