The everyday flow

1. Sign in to the dashboard. The operator opens https://postiz.banto-works.com and signs in. The dashboard is restricted to our staff because it holds the access tokens for our accounts.
2. Connect the accounts once. “Add channel” sends the operator to the platform's own authorisation screen — TikTok's, Instagram's, X's — where the operator approves the requested permissions while signed in to that platform. The platform hands MyPostiz an access token. MyPostiz never sees a password.
3. Write the post. The operator writes the caption, attaches the image or video, and ticks the channels that should receive it. Where a platform has its own post settings — TikTok's audience, comment, duet and stitch options, for example — the operator sets them here.
4. Choose the moment. The operator picks a publish date and time on the calendar. The post is stored locally and nothing is sent to any platform yet. It can still be rewritten, rescheduled or deleted.
5. MyPostiz publishes it. When the scheduled time arrives, a background worker uploads the media and publishes the post through the platform's official API, once per selected channel.
6. The result is checked, not assumed. MyPostiz asks the platform whether the post now exists on the account and records the outcome. A post is only shown as published once the platform confirms it; otherwise the platform's error message is stored and shown so it can be fixed.

What runs where

Dashboard (web)	The interface the operator uses: channels, composer, calendar and results. Runs on our own server at postiz.banto-works.com, behind a login and served over HTTPS.
Background worker	Wakes at each scheduled time, performs the upload and publish calls to each platform, then writes the result back. Retries a failed publish a limited number of times before marking it as an error.
Database	Stores the connected channels, their access tokens, the posts we wrote and their publish results. It runs on the same private server and is not exposed to the internet.
Media storage	Holds the images and videos attached to posts until they have been uploaded to the platforms.

Design decisions worth stating plainly

• Nothing publishes without a scheduled time set by a person. There is no “auto-post” mode that invents content or picks its own timing.
• Tokens are per account and revocable. Disconnecting a channel in the dashboard deletes its token; revoking access on the platform side stops MyPostiz just as effectively, and the next publish attempt reports the failure instead of retrying silently.
• Failures are loud. An accepted API request is not treated as a published post; the post list is read back before anything is marked as published.
• Self-hosted on purpose. The tokens for our own accounts stay on infrastructure we control rather than a third-party service.