trypostit/trypost

What it does

TryPost is a web application written in PHP on the Laravel framework with a browser front end, a database, a queue for the actual publishing and a websocket service for live updates. The centre of it is a calendar with month, week and day views and drag-and-drop rescheduling, plus a composer where you write a post once and then adjust the preview for each network before it goes. It publishes to thirteen distinct networks through each one's official interface, every one with its own code and its own rules for media sizes, text length, hashtags and alternative text. It exposes a proper programmable interface of about fifty endpoints, and a machine-readable interface for assistants at a fixed address, both protected by a token scoped to one workspace — and both are in the free code rather than held back. Workspaces separate brands or clients, with owner, administrator and member roles, comments and mentions on drafts, reusable signature and label blocks, an asset library with stock image and animation search, and a browser interface translated into sixteen languages. Measurements are per-account reach and engagement shown on the post screen, with two more networks' post figures added in the newest release. The machine-learning features are present but need keys you supply yourself, so they cost nothing unless you turn them on. It does not have an inbox for replies, no social listening, no link shortener and no approval workflow. Its automation module was removed in the newest release and replaced with something narrower, although the old code is still sitting in the tree.

Why it matters

Who it suits. One person or a small team posting to several networks who wants the scheduling to run on hardware they control, with no monthly fee, no per-post cap and no account limit. It suits anyone who wants to drive publishing from a script or an assistant particularly well, because the programmable interface is in the free code rather than behind a paywall. Skip it if you need an approval workflow or an inbox for replies, and skip it if you are not willing to change several default passwords before it goes anywhere near a public address.

What people say. Nothing credible exists outside the repository, and that is the honest finding. Three searches turned up only mirror copies of the repository itself, the project's own marketing and pricing pages, and undated directory listings — one of which is published by a company selling managed hosting for exactly these tools. We used none of them. For a repository created on 17 January 2026 that absence is what you would expect, and it is the main reason to be careful: there is nobody outside the project who has run it in anger and written down what broke. A discussion thread about it does exist on one large forum, but that forum's pages cannot be read from where this report is built, so we are not characterising it. What can be checked is the code itself, and we did: the networks, the programmable interface and the assistant interface were all read from the source files rather than from the marketing copy.

Verdict. The best thing about it is what is not there. The licence is plain AGPL-3.0 with no added conditions, and there is no paid edition holding features back — the pricing page says in its own words "No feature gating", the two hosted plans differ only in how many workspaces they allow, there is no licence-key setting anywhere in the configuration, and the organisation has no private paid repository. That is worth saying because the closest comparable, inovector/mixpost from Edition 4, is the exact counter-example: its own README calls the public repository "the Lite version of Mixpost Pro, a commercial product", its shipped configuration supports four account types against twelve advertised on its website, and its paid edition is a private package on a separate major version. So if the choice is between the two, this is the one without the catch. Two things to fix before it is reachable from the internet, though, because the shipped defaults are genuinely bad: the install seeds an administrator account of admin@trypost.it with the password password and prints it to the console, and the production container file ships a database password of trypost-password and binds plain unencrypted ports on every network interface. Change both, and turn on the optional encryption profile. If you want something older and far larger, gitroomhq/postiz-app was Edition 1's entry.