Self-hosted social media scheduler: run it from your own NAS

If you already own an always-on machine, you own most of a social media scheduler. Here is what self-hosting actually replaces, what it does not, and the storage trick that makes it work at library scale.

"Self-hosted social media scheduler" usually turns up two kinds of answer: full open-source suites you have to run and maintain, or people telling you to just pay for Buffer. There is a more practical middle option, and it is the one worth understanding first.

What you can and cannot self-host

You cannot self-host the connection to the platforms. Instagram, TikTok, YouTube, Facebook, Threads and Pinterest each require an approved app with reviewed permissions to publish on your behalf. Getting your own approved — particularly for Instagram Reels and TikTok — is a review process measured in weeks, and it can be refused.

What you can self-host is everything around it: the file storage, the schedule, the timing, the retry logic, and the queue. That is the expensive part at scale, and it is the part that has nothing to do with the platforms.

Why storage is the real constraint

Cloud posting tools cap their media libraries — commonly around 20 GB. That is generous for images and almost nothing for video. A hundred sixty-second clips is roughly 6 GB. A year of daily posting is well past the cap, and when you hit it, uploads simply start failing.

Your NAS, meanwhile, has terabytes sitting idle. So the job is to keep the library at home and let only a sliver of it visit the cloud.

The rolling window

A small daily job on your own machine does four things:

1. Reads a schedule — a CSV of what posts when, with captions and per-platform titles.
2. Uploads only the next few days' videos from local disk to the posting tool.
3. Schedules each one as a real native post to every platform you've listed.
4. Deletes each file from the cloud once it has published.

Cloud storage never grows. The library on your NAS can be any size. Nothing needs attention.

What hardware you need

Running it on a schedule

The job itself is small. On a NAS the cleanest route is a container with the video folder and the schedule mounted in, triggered once a day:

services:
  publisher:
    image: python:3.12-slim
    volumes:
      - /volume1/videos:/videos:ro
      - /volume1/docker/publisher:/work
    working_dir: /work
    command: python publisher.py

Then point your NAS's task scheduler at it once a day. That is the whole operational footprint — no web UI to maintain, no database, nothing exposed to the internet.

Things that will bite you

• Media ids must be integers when you create the post — as strings the API returns success and the post silently fails.
• Instagram has to be connected as a Business account or Reels posting fails outright.
• Bulk media deletion is usually a different endpoint shape than per-item deletion, and the per-item route often frees nothing.
• Clock and timezone — containers default to UTC. Schedule everything in one explicit timezone or your 9am posts arrive at 2am.

Is it worth it?

Against a $15/month plan, self-hosting the storage and scheduling saves around $180 a year and removes the per-post ceiling entirely. If you post weekly, that is not worth a weekend of setup. If you have a library you want going out daily for years, it pays for itself almost immediately and keeps paying.