Diffuz

Publishing infrastructure

One request.
The post goes out
where and when they asked.

Diffuz is a publishing and scheduling API for social networks. The people using your product connect the accounts they own, you send a request, and Diffuz handles the tokens, the queue, the retries and the platform quirks.

In development · early access

Channels

Available at launch — no platform review required
BlueskyPosts and threads, via AT Protocol.
MastodonAny instance. The app registers itself on connection.
LinkedInPersonal profiles.
DiscordAny channel, through an incoming webhook. No token to keep alive.
Pending platform review
InstagramImages, carousels, reels and stories.
TikTokVideo, first to the account holder’s drafts.
YouTubeShorts and long-form uploads.

Every platform decides who may publish through it, and on what terms. We say what is granted today rather than what we hope for. Facebook, Threads and Pinterest come after these three, one review at a time.

How it works

  • 1
    They connect their account. Each person authorises Diffuz through the platform’s own login flow, from your product or from our console. They can revoke it at any time, from either side.
  • 2
    You send a request. One endpoint, the same shape for every channel. Media stays on your servers — you pass a URL, we never store the file.
  • 3
    We take it from there. Refreshing tokens, holding the queue, retrying what is worth retrying, and never publishing the same thing twice.
# schedule a post to a connected account
POST https://api.diffuz.app/v1/posts
Authorization: Bearer dfz_live_…

{
  "account":    "acc_8f2c1d",
  "text":       "Ships tomorrow.",
  "media":      ["https://cdn.example.com/clip.mp4"],
  "publish_at": "2026-09-14T18:00:00+02:00"
}

A web console comes with it: connect accounts, watch the queue, see what failed and why, reconnect what expired.

Who it’s for

Teams that already produce content by machine and have nowhere to send it. Studios shipping a product whose users want their own accounts fed. Developers who would rather not learn what an Instagram media container is, or why a video upload can succeed and fail at the same time.

We are not building an alternative to Buffer or Metricool. There is no editorial calendar and no composer here. The content comes from you.

What it doesn’t do

Worth stating plainly, because it is what we will be held to:

  • No content is generated or altered. Diffuz sends what you send it.
  • No media is stored. Files are passed through, never kept.
  • Nothing is published without an explicit instruction from the account holder.
  • No feed, no messages, no followers are read. We do not ask for those permissions.
  • No data is sold, rented, or used to train anything.
  • No analytics, no tracking pixels, no cookie banner — because there is nothing to consent to.

Early access

Diffuz is being built now, in the open, by one person. The channels that need no platform approval work first; the rest follow their reviews.

If you are building something that needs to publish, write and say what you are working on — early users shape what gets built and pay nothing.

contact@diffuz.app