One CMS for all your blogs.
Postream is a central CMS for blogs: it writes posts with AI from a brief, keeps everything in one place and delivers each post to the right site through an API.
GET /public/v1/posts?locale=pt-BR&tag=deliveryFrom brief to published post
The Postream workflow is a fixed sequence of seven steps, from brief to published post. You follow along in the panel and step in when the text is ready to read.
- 1
Brief
Write a short brief or pick one of the topics Postream suggests for the site.
- 2
Research
When you ask for it, the AI searches the web before writing.
- 3
Writing
Outline and draft in the site's tone of voice, with the brand's keywords and internal links.
- 4
Editing
A second pass checks clarity, length and consistency.
- 5
Your approvalNeeds you
Nothing is translated or published until you read and approve the original text.
- 6
Translation
Each of the site's languages gets its own version, with its own title and address.
- 7
SEO and review
Search title and description, plus a final check in every language.
Then the site fetches the post through the API, in whatever language it needs.
Many sites, one panel
In Postream, each site is a space of its own, with its brand, languages and API keys. Switch sites at the top of the panel and see only that site's posts.
| Site | Languages | Published |
|---|---|---|
| cafedobairro.com.br | pt-BRen | 48 |
| oficina12.dev | pt-BRenes | 112 |
| rotasdosul.blog | es | 23 |
- Brand and tone per site
- Tone of voice, keywords, call to action and internal links are saved on the site and go into every post.
- Languages per site
- One blog in Portuguese and English, another only in Spanish. Postream translates into the languages each site uses.
- One key per site
- Each key only opens that site's published posts, and you can revoke it at any time.
Your sites fetch posts through an API
The Postream public API is a read-only REST API, with caching and a rate limit per key, that serves a site's published posts. Call it from your site's server, for example in a Next.js server component.
const API = process.env.POSTREAM_API_URL;
const KEY = process.env.POSTREAM_API_KEY;
const res = await fetch(`${API}/posts/${slug}?locale=pt-BR`, {
headers: { Authorization: `Bearer ${KEY}` },
next: { revalidate: 300 },
});
const { data: post } = await res.json();What each post returns
Title, excerpt, body in HTML and Markdown, SEO and Open Graph fields, tags, author, dates and the addresses of its translations.
Frequently asked questions
The frequently asked questions give short answers about what Postream does, who it is for and how posts reach your sites.
What is Postream?
Postream is a central CMS for blogs. It writes posts with AI from a brief, keeps the posts of many sites in one panel and delivers each post to the right site through a public API.
Does the AI publish anything without me seeing it?
No. Every post stops at the approval step: nothing is translated or published until you read and approve the original text.
Which languages does Postream write in?
Each site picks its own languages. Once you approve the original text, Postream creates one version per language, each with its own title, description and address.
How does my site get the posts?
Through the Postream read-only REST API. Your site fetches its published posts with a key of its own, ideally on the server, so the text arrives ready in the HTML and search engines can read it.
Does Postream help my blog show up on Google and in AI answers?
Yes. Every post ships with a search title and description, Open Graph fields, the addresses of its translations, 301 redirects from old addresses and an IndexNow ping when it goes live.