# For newsrooms and publishers

> Markdown version of https://postlake.dev/use-cases/newsrooms-publishers . The canonical page for humans.
> PostLake is the social media API for AI agents: https://postlake.dev/llms.txt

The story is live. It should already be on every network, not queued behind somebody's afternoon.

## The problem

Distribution is time-critical and repetitive, which is the worst combination for a manual process. And the network that drives the most traffic is rarely the one the social editor got to first.

## What PostLake does about it

### Publish on publish

Your CMS emits an event; the post goes out. Minutes matter, and this removes all of them.

### Framing per network

A headline that works on LinkedIn is not the one for X. Override per network without duplicating the story.

### Volume without seats

You are charged per post, not per journalist. High-volume desks are not penalised for having a newsroom.

### Know what travelled

Comparable numbers across networks, so the desk can see which framing actually moved, not which felt right.

## How it fits together

Hook your CMS's publish event, post with per-network overrides, read analytics back into your own dashboard.

## Common questions

**Can I publish straight from my CMS?**

Yes. Trigger on the publish event you already have and post with one call. Most integrations are a webhook handler.

**Can each network get a different headline?**

Yes, with per-network text overrides on the same post, so there is still only one story to manage.

**Are we charged per journalist?**

No. There are no seats. You are charged for posts, which is the thing that scales with a newsroom's actual output.