I built a social scheduler that now posts to DEV too

PostStage schedules to 16 platforms via their official APIs. DEV.to just became one of them.

I've been building PostStage — a scheduler that
queues one post to 16 platforms and fires each through that platform's official
API.

This week I added DEV.to as a publishing target, which is why I'm posting
about it here: I can now write a draft, set a time, and have it land on DEV,
Hashnode-style, alongside the same content going to LinkedIn and X.

The current list: Instagram, Facebook Pages, LinkedIn, X, YouTube Shorts,
Threads, Pinterest, Google Business Profile, Bluesky, Mastodon, TikTok, Tumblr,
Telegram, Discord, WordPress, and DEV.

A few things I made deliberate calls on:

• Official APIs only. No browser automation, no unofficial endpoints. It costs features — Instagram won't let anyone publish to a personal account, so PostStage doesn't pretend to — but nothing breaks the week a platform ships a DOM change.
• QStash for delivery, not polling. Each post is handed to Upstash with a notBefore timestamp, so a scheduled post is a queued message rather than a row some cron has to notice.
• Tokens encrypted at rest with AES-256-GCM, because a scheduler is a pile of other people's access tokens and should be treated as one.

It's a real product with paid plans, and there's a free tier if you just want to
see whether the queue does what you need.

Happy to answer anything about the platform integrations — the API quirks across
16 of them have been the genuinely hard part, and I'll probably write that up
separately.