Publishing infrastructure
One request.
The post goes out
where and when they asked.
Diffuz is a publishing suite for social networks, and the same thing as an API. People connect the accounts they own, compose once, see what each network will accept before anything is sent, publish, then follow the figures and the replies that come back. Diffuz handles the tokens, the queue, the retries and the platform quirks.
Open to new accounts
Channels
| Professional or creator accounts: image, video, Reel, story or carousel. | |
| Pages you manage: text, link, photo or video. | |
| TikTok | Video, published directly to your account. Until TikTok completes its review of Diffuz, its rules allow posting from a private account only: your videos are visible to you alone. |
| Personal profiles: text, link preview, image or video. | |
| YouTube | Video uploads and Shorts, public, unlisted or private. |
| Google Business Profile | Updates on your listing: text, one optional photo and a button. |
| Pins on the board you choose. |
Every platform decides who may publish through it, and on what terms. We say what is granted today rather than what we hope for. Pinterest opens when its review does.
How it works
- 1They 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.
- 2You 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.
- 3We 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://console.diffuz.app/v1/posts Authorization: Bearer dfz_… { "targets": [{ "account_id": "8f2c1d…" }, { "external_ref": "client-42" }], "content": { "texte": "Ships tomorrow.", "medias": [{ "url": "https://cdn.example.com/clip.mp4", "type": "video" }] }, "scheduled_at": "2026-09-20T18:00:00+02:00" }
The web console does all of it without a line of code: connect accounts, compose a post and see how each network will adapt it, watch the queue, read the day's figures with their variation, and answer the comments the accounts receive. Comments are read when the screen is displayed and never stored.
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.
And people who simply want to write once and publish everywhere: the console has a composer with per-network previews, a calendar, and the queue — no code needed.
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.
- Media sent through the API is never stored: we pass its URL on. A file uploaded in the console is kept only until it is published, then deleted, unless you save it to your media library.
- Nothing is published without an explicit instruction from the account holder.
- No feed and no followers are read. Comments are shown only when you open them in the console, and never stored.
- 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.
Getting started
Create an account, connect the accounts you own, and publish from the console or the API.
Early users pay nothing and shape what gets built. Create an account, or write and say what you are working on.