Blog/Private AI for press release drafting
Communications

Private AI for press release drafting

By Samuel Seidel · Updated September 9, 2026

A self-hosted drafting model lets a communications team tighten a press release and match house style without pre-announcement drafts sitting with an AI vendor. A release is written to become public, but only at a moment the company chooses: earnings before the market close, a layoff before employees hear it secondhand, an acquisition before the target's stock moves. Where the draft sits until then decides whether the timing stays the company's.

Why the drafts matter as much as the final release

The final press release is designed to be read by anyone. The five or six drafts before it usually aren't: they carry numbers before they're final, phrasing choices about a layoff that hasn't been communicated internally, or the existence of a deal before either party has confirmed it. Pasting a draft into a general-purpose AI tool to polish the language sends that pre-announcement material to a third party's infrastructure, and a leak from that copy, however unlikely, is a leak the company can't trace or control the way it can with its own systems.

For material announcements, the stakes go beyond embarrassment. A release tied to earnings, an acquisition, or another market-moving event can carry securities law consequences if it leaks or gets misattributed before the scheduled release time, the same category of risk covered in the post on board meeting prep.

What changes when the drafting model is self-hosted

Running the drafting assistant on a dedicated DGX Spark sends every draft revision to the team's own model on a machine assigned only to it, not to an AI vendor's API. The team still gets a model that turns talking points into release copy, checks it against AP style, or generates headline variations before final sign-off.

A rented Spark is still GPUwerk's hardware, operated under its published DPA, so check that your disclosure policy allows a hosting provider before live drafts of market-moving announcements go on it.

Open WebUI restricted to the communications and legal review team is a practical way to run this, with past releases kept as reference so new drafts match the company's voice and disclosure conventions, using the retrieval approach in the guide to on-premise RAG.

What the model is useful for, and what stays with the team

A drafting model helps with tightening language, generating headline and boilerplate variations, and checking a release against a style guide. It has no role in deciding when a release goes out, who reviews it for legal accuracy, or whether the underlying announcement is ready to be made public at all. Those calls stay with communications, legal and the executives who own the announcement.

What this doesn't solve

Self-hosting the drafting model doesn't replace legal review of a release before distribution, and it doesn't manage the embargo, wire service submission or journalist outreach that happens once the release is final. What it removes is one specific exposure: draft language about an announcement the company hasn't made yet sitting with an AI vendor. See pricing for what a dedicated Spark costs for a communications team.

Related pages

First top-up: pay $20, get $30 in credit

Polish press releases without an AI vendor seeing them early.

A dedicated Spark for communications, starting at $0.79/hour, deployed in minutes from EU-Central. Read the Open WebUI setup →

Your data stays on a machine assigned only to you. GPUwerk processes it under its published DPA.

Create account See private LLM hosting