TryPost

Manage publishing to 12 networks from one calendar and composer

The README lists native publishing for Instagram, Facebook, LinkedIn, X, TikTok, YouTube, Pinterest, Threads, Bluesky, Mastodon, Telegram, and Discord. Month, week, and day calendar views support drag-and-drop rescheduling and per-network previews.

Workspaces separate brands or clients, with Owner/Admin/Member roles, draft comments, mentions, and approval flows for agency and multi-brand workflows.

Sources: [2]

Put the AI copilot, REST API, and MCP into the same publishing workflow

Brand profiles feed tone, voice, language, and colors into caption, draft, and carousel generation. The REST API and MCP server expose draft, schedule, and publish workflows to scripts and compatible agents.

v1.0.9 also exposed workspace webhooks through the API and MCP, continuing the project's agent- and automation-oriented direction.

Sources: [2][3]

Self-host the app with Postgres, Redis, queues, scheduling, and WebSockets

The production Compose file pulls the published GHCR image and starts TryPost together with Postgres, Redis, queue workers, the scheduler, and Laravel Reverb for WebSockets. Storage can remain local or be configured for R2 or S3.

Self-hosting still uses each social network's official APIs, so client IDs, secrets, and redirect URLs must be configured for the networks you connect.

Sources: [4][2]

For teams that want one social publishing workflow and also need automation or AI-agent access

It fits creators, small teams, and agencies that want to replace separate network dashboards and spreadsheets with one calendar, asset, approval, and analytics workflow. MCP and API access are especially relevant when publishing needs to connect to existing agents or internal automation.

A self-hosted deployment still requires deliberate secret and OAuth management

The production Compose file contains values that must be replaced for APP_KEY, database passwords, and Reverb secrets. Durable API/MCP deployments should also pin Passport private and public keys in the environment so container recreation does not invalidate tokens.

Public deployments also need correct APP_URL, WebSocket host, HTTPS or reverse-proxy settings, and callback URLs for each social provider.

Sources: [4]

The AI data path depends on the provider you configure

The Compose configuration supports optional API keys for OpenAI, Anthropic, Gemini, and OpenRouter. Self-hosting the application does not make AI generation local by itself, so review what prompts and brand content are sent to the selected provider.

Sources: [4]

AGPL-3.0 adds source-availability obligations for modified network services

The README explicitly says that modified versions run as a network service must make their changes available to users under AGPL Section 13. Review this before offering a modified SaaS or exposing an internally modified deployment outside the organization.

Sources: [2][1]