What is Postream
A central CMS for many blogs. AI writes, you approve, and each site fetches its own posts through the API.
Postream keeps the blogs of many sites in a single panel. For each site you set up the brand (tone of voice, audience, keywords, internal links) and the languages. From a topic, the AI researches, writes and reviews the post; you read and approve it; Postream translates it and prepares the SEO; and the site fetches the published post through the public API.
Postream does not host the blog. The blog stays on your site, with your design, and only reads the posts.
How a post is made
- Topic. You write a short brief or pick one of the topics Postream suggests based on the site's brand.
- Research. If you ask for it, the AI researches the web before writing.
- Draft. Structure and text in the site's tone of voice, with the brand's keywords and internal links.
- Edit. A second pass reviews clarity, length and consistency.
- Your approval. The run stops and waits for you to read the text in the source language. Nothing is translated or published before that.
- Translation, SEO and review. Each language of the site gets its version, with its own title, search engine description and slug, and a final check.
- Publishing. You publish right away or schedule it. From then on the post appears in the site's API.
What lives where
| In Postream | On your site |
|---|---|
| Brand and languages of each site | The design and pages of the blog |
| Posts, versions per language, generation history | Fetching posts through the API and rendering them |
| AI keys (yours, encrypted) and the site's API keys | The site's API key, on the server |
Where to go next
- Getting started: from sign-in to the first published post.
- Public API: how the site fetches the posts.
- Guardrails: the limits that keep the site from turning into a content factory.