I offer businesses social media post creation and scheduled publishing through Postiz. You can combine both services or give me existing posts to schedule. We agree on topics, tone, channels and dates, and only approved content is scheduled for publication.
My service: creating content and scheduling publication
Have social media posts created: I turn your topics, offers and existing materials into posts for the agreed channels. This includes the post copy, a suitable opening and a clear call to action. We establish which images or videos are needed and who supplies them before work starts. You receive drafts to review and approve.
Schedule existing posts: If your content is ready, I handle scheduling through Postiz. We agree on which post should appear on which channel and when. You do not need to run your own Postiz installation.
Combine both: I create the posts, we review them together, and I schedule the approved versions. This gives you a manageable editorial calendar.
How we work together
- Clarify goals and materials: Who do you want to reach, which topics matter and what copy, images or videos are already available?
- Agree on scope and channels: We set the number of posts, platforms and publishing frequency. Before starting, we check the required account access and available connections.
- Review the posts: You check the drafts for factual accuracy, tone and how they represent your business. Changes happen before approval.
- Schedule publication: I add the approved content to Postiz and schedule the agreed dates. We also agree on how to handle later changes and failed publications.
The channels and automations described below belong to my own projects. We check which connections are available for your business individually: an editorial calendar cannot replace a pending platform approval.
Discuss social media content and publishing support.
My own setup: Postiz on my server
For my own projects, I no longer use a SaaS service for my social media channels. Instead, I run the open-source software Postiz on my own server. It runs without Docker next to my websites, schedules posts for YouTube, LinkedIn, Facebook, Instagram, Bluesky and other networks, and can be driven via API from my automations. The installation was manageable. The real effort is the platforms' app approvals.
Why self-host?
I used to schedule with a SaaS service. Over time, more and more channels and projects were added: my freelance presence, the EU quiz InsightEUQuiz in three languages, plus automatically generated videos. I wanted:
- all channels in one place, with no extra cost per channel or brand
- an open API that my own scripts and my Hermes agent can use
- full control over settings a ready-made service doesn't offer
Postiz is open source (AGPL-3.0) and built for exactly this purpose. The source code is on GitHub, and the self-hosting guides are in the official documentation.
The starting point: one server that runs everything
Postiz had to run on my existing web server, a VPS with Plesk and 8 GB of RAM. All my websites run there. A crash or data loss would be costly. So strict rules applied from the start: Postiz runs only in my own user directory, the server configuration stays untouched, and memory is always kept in view.
Installing without Docker
The usual route is Docker Compose. But I didn't want Docker on this server. Postiz also runs directly from source; you just have to provide the building blocks yourself:
- PostgreSQL: Plesk didn't offer PostgreSQL databases on this server. So a small private PostgreSQL instance runs in the user directory, reachable only locally.
- Redis: was already available.
- Temporal: handles Postiz's scheduled workflows. Instead of a full Temporal cluster, the lightweight Temporal CLI server runs with an SQLite database, at low priority and with about 150 MB of memory. A cron entry starts it after a reboot and checks every five minutes that it is still running.
This Temporal variant describes my own setup, not a recommended customer deployment. The Temporal development server is explicitly not intended for production. Customer publishing needs an appropriate operational environment; a cron restart does not replace monitoring or tested recovery.
I restrict access through login and disabled open registration. I also prevent search engine indexing, which is not an access control. My NAS regularly pulls the server backups.
Connected channels
Currently connected in Postiz:
- YouTube: two channels, for Shopware and for the quiz
- LinkedIn: profile and company pages
- Facebook: pages for my projects
- Instagram: three accounts for the quiz, one per language
- Bluesky and Google Business Profile
- Pinterest and TikTok: connected, but still waiting for approval of the respective app
Automation via API
The biggest gain is the API. My workflows deliver their results directly to Postiz:
- The quiz shorts are uploaded and scheduled two weeks ahead.
- The Shopware news videos arrive as drafts that I approve.
- After approval, the matching posts go out on LinkedIn and Facebook automatically.
My own adjustments
For YouTube, Postiz lacked three settings I needed: video language, category and playlist. A small patch now sets them automatically. LinkedIn needed additional permissions. I have to reapply both patches after every Postiz update; the original files are kept for that.
The pitfalls
- The server couldn't find itself. The hosting provider's DNS servers didn't resolve the server's own subdomain, so Postiz couldn't fetch its own uploads. A fixed address mapping at startup solves it.
- Reconnecting YouTube. After reconnecting a channel, the new token ended up in a temporary record while the actual channel kept the expired one. I had to fix that by hand.
- Misleading error messages. In the version I used, setting a YouTube thumbnail produced an "account not verified" message that did not explain the underlying problem.
- Platform approvals. Meta wants an app in live mode, LinkedIn requires a verified company association for some APIs, Pinterest an application for standard access, and TikTok rejected my app twice: once for personal use, once because of the website address on a subdomain.
That last point takes more time than the whole installation. If you self-host, many networks require your own app and their review process. A SaaS service takes exactly that off your hands.
Self-host or SaaS?
Self-hosting pays off if:
- you schedule for many channels or several brands
- you generate posts automatically from your own systems
- you already run a server and can handle updates
A SaaS service is better if:
- you only have a few channels and just want to post
- you have no time for updates, patches and platform approvals
- support matters more to you than full control
I have used both. Before Postiz I used Nuelink*, and there are two things a SaaS service like Nuelink clearly does better:
- Connect networks with one click. Nuelink brings its own already approved apps. You don't have to fight Meta, LinkedIn, TikTok or Pinterest for every approval.
- Posts straight from the AI chat. Through MCP and connectors you can have an AI assistant such as Claude create and schedule posts for you, without writing your own scripts.
So for a solo business with a few channels, a service like this is often the better choice. For my setup with many channels and lots of custom automation, Postiz fits better.
* Affiliate link: if you sign up through this link, I receive a commission. The price stays the same for you.
Frequently asked questions
Does Postiz need Docker?
No. Docker is the recommended route, but Postiz also runs directly from source. Then you have to provide PostgreSQL, Redis and Temporal yourself.
How much memory does Postiz need?
According to the documentation, 2 GB is only enough for a simple install with light use. The documentation recommends 8 GB as a starting point. My shared server is not a general sizing recommendation. Allow for load, services and headroom; a development server is not a substitute for production capacity.
Is Postiz free?
The software is open source. Costs come from the server and your time for setup and maintenance.
Do I need to operate Postiz when I hire you?
No. You can provide finished posts or ask me to write them. We agree on channels, scope and approval, and I handle the agreed scheduling. Comment replies, advertising management and additional media production are included only when explicitly agreed.