Full Guide
Postiz Review: How We Use It for GrowthPilot Social Publishing
This experience-led guide explains how GrowthPilot uses Postiz Hosted across LinkedIn, Facebook, Instagram and X. It separates official capabilities from our operational evidence, including 63 scheduled placements, draft behaviour, provider settings, support experience and the confirmed Hosted limitation for URLs in X posts.
Main Guide
Where Postiz fits in a social workflow
Postiz sits between approved content and social networks. It can hold connected integrations, media and post objects, then expose them through a calendar and API. That makes it useful as a distribution system. It does not decide the brand strategy, verify every claim, grant image rights or replace final approval.
GrowthPilot generates and approves content in its governed system, then uses Postiz for provider delivery. That separation lets us bind one immutable candidate to one destination, upload approved media, inspect the remote object and stop on a mismatch.
Our current GrowthPilot setup
We connected separate GrowthPilot channels for LinkedIn, Facebook, Instagram Standalone and X. Our system discovered each integration read-only, verified its public identity and required explicit brand binding before delivery. A display name alone was insufficient.
The same governed path has created text and image drafts, uploaded approved deterministic media, published one controlled LinkedIn proof after separate authority, scheduled approved multi-platform batches, inspected the Postiz calendar and reconciled provider objects through the API. This is current live operational evidence, not a simulated review.
Our overall experience has been positive. Connecting the channels was relatively easy, the calendar made multi-platform work straightforward to inspect, and relatively few issues emerged for the scale we used. That is GrowthPilot’s experience with its own account and workflow, not a guarantee that every integration, account or team will behave the same way.
What the calendar gives us
The visual calendar is useful for seeing the rhythm of a campaign across channels and dates. It makes an overloaded day or missing slot easier to notice than a list of API records. We still rely on immutable internal approvals and API reconciliation for exact identity, because visual presence alone does not prove that copy, link, media, account and timestamp match the approved candidate.
For a small business using the Hosted interface, the calendar can be the primary operating surface. Start with one week, use recognisable naming, check timezone behaviour and decide who has authority to alter a scheduled item. Custom engineering is optional, not a prerequisite for useful scheduling.
What we learned from 63 scheduled placements
GrowthPilot’s 24–30 August 2026 batch contains 21 placements each for LinkedIn, Facebook and Instagram: three per day per platform across weekdays and the weekend. Nine master creatives were reused by exact bytes across suitable placements. We used zero Postiz AI images and zero Postiz AI videos for the batch.
That proves we could organise and schedule the approved inventory at meaningful volume. It does not prove engagement, audience growth, conversion or revenue. Those outcomes must be measured after publication and should not be attributed to the scheduler without evidence.
Drafts, review anchors and visibility
During API testing, one draft tied to an elapsed review anchor became difficult to find in the expected Draft calendar view. The provider object still existed. We switched to a suitable future review anchor, then verified it through read and list operations.
This is an advanced workflow detail, not a claim that every Postiz draft disappears. Interface filters and date ranges can affect what an operator sees. A team using the normal interface should still confirm where drafts live and how review dates behave before relying on a process.
Platform-specific settings matter
Social networks do not share one payload. Postiz documents platform-specific settings. Our X integration required who_can_reply_post, with values including everyone, following, mentioned users, subscribers and verified accounts. We now validate it before approval.
Instagram likewise needs the correct post type and suitable media. Treat each channel as a separate delivery contract even when the editorial idea is shared. The content and design tools guide can help define a repeatable asset workflow before scheduling.
The confirmed Hosted limitation for X links
One API-scheduled X object was accepted and read back without the owned GrowthPilot /go/ URL in the immutable approved post. Our system failed closed, cancelled it before release and quarantined the remaining linked X candidates.
Postiz support confirmed to us that its Hosted SaaS can no longer support posts containing URLs on X because of a substantial X Developer Portal pricing increase. Postiz told us that including a link increases its X API cost by approximately 13 times, or 1,233% per post. This is operator-supplied support evidence about our Hosted path, not an independent claim about every X API contract.
The two practical options Postiz gave us were to create linked posts directly on X, or to self-host Postiz and configure our own X integration while accepting the associated X API costs. Postiz said it would restore SaaS URL support if X changes or lowers its pricing in future. We received the response within 24 hours; the team understood the issue, explained the reason clearly and gave us practical options. We considered that an excellent support experience, while recognising that one interaction cannot establish a universal support standard.
Our current X decision
GrowthPilot is staying on Postiz Hosted. We are not self-hosting solely to restore X links at this stage. Through Postiz, X is therefore mainly suitable for useful no-link observations, tips, questions and brand-awareness content. If traffic is the purpose, direct posting on X is currently the clearer route; a separately governed owned-profile link strategy may be considered later.
Our governed capability record classifies Hosted Postiz plus X plus a URL as unsupported by provider policy, not as a pending software bug. Linked X delivery remains blocked until a read-only capability review finds new official or support evidence. The scheduled review is every 90 days, or earlier if Postiz announces that Hosted URL support has returned.
Why reconciliation matters
After scheduling, reopen the final post and check the account, time, copy, media and link. If the provider state is uncertain, verify it before retrying so that a second draft or schedule is not created.
In GrowthPilot’s advanced API workflow, we reserve a deterministic operation identity, bind the approved content hash, read the provider object back and retain immutable receipts. A mismatch fails closed. A small team working entirely in the UI can apply the same underlying lesson by checking the target account and reopening the scheduled item after saving.
Current plans and allowances
On 16 August 2026, Postiz’s pricing page listed a seven-day trial. Standard was shown at $29 per month with five social channels, Team at $39 with ten channels and Pro at $49 with thirty, subject to the billing selection and current terms. The page also showed AI image and video allowances on relevant plans.
Our current account displays 100 AI images and 10 AI videos per month. Treat the account screen and public plan page as current evidence only for the reviewed date and intended plan. Our campaign demonstrates that a team with an external deterministic creative pipeline may not need those generation allowances for every batch.
What to test in a seven-day trial
- Connect one brand account and verify it is not a personal or similarly named page.
- Create a text draft and locate it in the expected review view.
- Upload one owned image and inspect its crop and accessibility text where supported.
- Schedule one reversible test using the intended timezone.
- Check the remote copy, link and media after saving.
- Review calendar filters on desktop and mobile.
- Test cancellation before the release time.
- Record roles, approval responsibility and account recovery.
- Compare the channel allowance with the real number of connected identities.
- Keep linked X delivery blocked while Hosted URL posts remain unsupported by provider policy.
Who Postiz may suit — and who should think twice
Based on our experience, Postiz is a strong fit for an owner, agency or small content team managing several networks through a calendar-led workflow. It is particularly relevant when content is prepared elsewhere, human approval remains explicit, and one distribution layer or API-assisted workflow should serve LinkedIn, Facebook and Instagram.
Think twice if you use only X and need clickable URLs, have one account already served by a native scheduler, or do not want to maintain another connected service. For full linked-post functionality on X, direct X posting is currently the better fit unless you are prepared to self-host Postiz and take on the associated X API cost.
If the workflow itself is unclear, map it before selecting software. The Make decision covers visual automation, while Responsible AI covers ownership, permitted inputs and review boundaries.
Conclusion
Postiz has worked very well for GrowthPilot’s real LinkedIn, Facebook and Instagram scheduling workflow. The calendar, connected integrations and API supported approved work at meaningful volume, and the support response to our X issue was strong. The Hosted restriction on URLs in X posts is still a meaningful limitation for that use case. Postiz remains a strong multi-platform fit for us, not an unqualified recommendation for every social workflow.
Sources reviewed
- Postiz public API introduction, create-post and upload documentation reviewed 17 August 2026.
- Postiz pricing page reviewed 17 August 2026.
- Immutable operational evidence for account discovery, drafts, uploads, controlled publication, scheduling, cancellation and reconciliation.
- GrowthPilot high-cadence campaign evidence for 63 scheduled LinkedIn, Facebook and Instagram placements.
- Operator-supplied Postiz support response confirming the Hosted SaaS X URL policy, approximate API cost effect, alternatives and possible future restoration.
GrowthPilot has an active affiliate relationship with Postiz. Governed commercial links are disclosed and do not determine the editorial assessment, including the X limitation.
GrowthPilot may earn a commission from qualifying purchases through commercial links, at no additional cost to you. Commercial availability does not determine inclusion or assessment.