Hosted platforms
Compare Zernio and Post for Me as hosted execution routes, including supported operations, platform coverage, webhooks, and pricing.
A hosted platform is an optional managed backend: instead of calling a social platform’s API with credentials you control, the SDK calls Zernio or Post for Me using your own provider account. The provider owns the platform apps, account connections, and upstream API relationships; your application keeps tenant authorization and outcome handling.
Direct integrations remain the other route: your platform app, your tokens, your review processes, no provider charges. Each platform page documents that route. Nothing routes through a maintainer-operated service in either mode, and an application can use one provider, both, or neither.
Compare providers
| Zernio | Post for Me | |
|---|---|---|
| Platforms | X, Threads, Bluesky, YouTube, TikTok, Instagram, LinkedIn, Facebook | X, Threads, Bluesky, YouTube, TikTok, Instagram, LinkedIn, Facebook |
| Publish | Text, images, video, carousels | Text, images, video, carousels |
| Scheduling | Schedule and cancel | Schedule and cancel |
| Post reads and status | All platforms | All platforms |
| Media upload | All platforms | All platforms |
| Post analytics | All platforms | Feed-based, all platforms |
| Account analytics | All platforms | — |
| Comments | X, Threads, Bluesky, YouTube, Instagram, LinkedIn, Facebook | — |
| Messages | X, Bluesky, Instagram, Facebook | — |
| Native post removal | X, Threads, Bluesky, YouTube, LinkedIn, Facebook | — |
| Webhook verification | X-Zernio-Signature HMAC over raw bytes |
Post-For-Me-Webhook-Secret shared secret |
| Pricing | zernio.com | postforme.dev |
| Setup guide | Zernio setup | Post for Me setup |
A dash means the adapter does not expose that operation for the provider’s documented API. Rows describe the normalized surface implemented in Social SDK, generated from the same manifests as the capability matrix; they do not certify a provider account, plan tier, platform permission, or a live request.
You pay the selected provider directly and remain responsible for its plan, platform permissions, add-ons, and connected-account terms.
What every hosted route shares
- The provider API key stays on your server and is passed to the adapter. Connected accounts are provider records that your application must map to tenants before any operation.
- Provider acceptance is not platform publication. Preserve the provider record, inspect every destination result, and reconcile pending or uncertain deliveries.
- Webhooks are verified with the provider’s real signature or shared-secret mechanism before an event is durably accepted. See events.
- Social SDK does not pool keys, resell provider usage, transfer authorizations between providers, or imply a sponsorship relationship.