DevPost BETA Back home
About

Built for people who ship.

DevPost is a social publishing control room for people and the agents working alongside them. Here is what it does, who runs it, and what it deliberately is not.

What DevPost is

DevPost is an operational layer for social publishing. You connect your accounts, write once in a composer that adapts to each platform's native fields, then schedule, publish, and watch what actually happened — drafts, approvals, delivery status, and failures all stay visible in the same workspace.

It covers X, Reddit, Instagram, LinkedIn, TikTok, and YouTube today. Each platform gets its own fields — Reddit's subreddit and title, TikTok's privacy settings, YouTube's Shorts handling — instead of one lowest-common-denominator text box copied six times.

Why it exists

Most publishing tools were designed for a person clicking buttons, and most AI writing tools stop at the draft. Neither shape fits how a lot of builders now work: an agent researches, drafts, and queues, and a human decides what ships. DevPost is built for that split. The promise is short — agents do the work, you stay in control — and everything in the product is arranged around keeping the second half true.

Web and MCP are the same product

The web app and the MCP server are two transports over one system. They share the same schemas, the same platform descriptors, and the same service contracts, so anything you can do by clicking, an MCP-compatible agent can do by calling — 40+ tools against the exact contracts the UI uses. There is no agent-only sidecar and no UI-only backend that quietly drifts from it.

What stays under your control

  • Drafts and scheduled posts wait for an explicit action before anything goes out.
  • Every post shows which account it belongs to, before and after publishing.
  • Generated copy arrives as an editable suggestion, never as an automatic send.
  • Failures surface with a reason you can act on instead of disappearing into a log.

Who operates it

DevPost is an independent product operated by Emanuele Pavanello, Via Giuseppe Garibaldi 8, 10040 San Gillio (TO), Italy. It is not venture-funded and there is no sales team to get past: the same person who writes the code answers the email. Formal operator details, jurisdiction, and data-handling commitments are in the Terms of Service and the Privacy Policy.

What it is not

It is not an enterprise social suite, an analytics warehouse, or an autopilot that posts on your behalf while you are not looking. Features that are not built yet are not advertised as if they were, and controls that would imply behaviour the product cannot deliver do not ship.

Try it

Every account starts with 7 days of the full product — no card, no invite queue. Plans and the metered credit basket are laid out on the pricing page, the agent setup is documented under MCP, and anything still unclear is worth an email: see contact.