About and editorial policy

Who publishes this site

The Streampixel Blog is published by Streampixel, the company behind the Streampixel managed pixel streaming platform (streampixel.io). It is written by people who build and operate pixel streaming infrastructure. That is a strength and a conflict of interest, so we state it plainly: the publisher benefits commercially if readers choose Streampixel. The editorial standards below exist to keep the technical content useful whether or not you do.

What we cover

Two kinds of content, always labelled. Engineering articles cover pixel streaming for Unreal Engine as a whole: the engine's Pixel Streaming and Pixel Streaming 2 plugins, Epic's reference infrastructure, WebRTC and networking, deployment on infrastructure you control, performance, scaling, operations and security. Most are platform-independent and are meant to be correct for a self-hosted deployment. Company content covers customer stories and product updates about the Streampixel platform.

How product-specific content is labelled

• Engineering articles that apply only to the Streampixel platform carry the label "Streampixel platform guide" on the page, in every listing and in search results, and open with a banner that links to the platform documentation.
• Inside a platform-independent article, a paragraph that applies only to Streampixel is set in a "Streampixel-specific" callout.
• Customer stories and product updates live in their own hubs, carry their own type labels, and are never mixed into the platform-independent topic hubs.
• Product links are used where they help the reader complete the task at hand. We do not attach calls to action to every section.
• Articles on this site are canonical here. They are not republished on the main website, and earlier posts on the main website are not republished here.

Verification standards for engineering articles

• Every published article states the Unreal Engine versions it was written against, the plugin variant, and the infrastructure branch or commit where relevant.
• Tutorials and benchmarks record the environment they were tested in, the date, and whether the steps were reproduced end to end. The build refuses to publish a tutorial or benchmark without this record.
• Every published article cites at least one primary source. Version-specific claims are checked against Epic's current documentation before publication, and the date of the check is shown.
• Code and configuration are labelled either as tested examples, run in the stated environment, or as illustrative snippets that show a shape but were not run as written.
• Benchmarks publish hardware, software, network conditions, methodology, units and limitations, with raw data where possible.
• We do not publish invented benchmarks, test results or credentials. Outlines are never published as finished articles.
• Drafting tools, including AI assistants, may be used for research and editing. A person verifies every technical claim against primary sources before publication and is accountable for the article.

Standards for customer stories and product updates

• A customer story is published only with the customer's written approval; the approver and date are recorded with the article.
• Every quoted figure states how it was measured (platform analytics for a stated period, the customer's own report, a survey). A figure the customer does not want to share is stated as not shared, never estimated.
• Quotes are attributed by name and role and approved with the rest of the story.
• Product updates say what changed, who is affected and what to do; they link to the documentation instead of restating it.

Authors

Author profiles show only information supplied by the author: name, role, relevant experience and links they chose to share. When no author is named, the article is published under the Streampixel name and the publisher is accountable for it.

Corrections and revisions

• Report a mistake by email to support@streampixel.io with the article address and, if possible, a source for the correct information. Each article also has a "Report a correction" link.
• Typos and wording fixes are made silently. Substantive corrections are recorded in the article's revision history with a date and a note, and the article's "revised" date is updated only for substantive changes.
• When an engine release changes the steps, the article is either updated with a revision note or marked "Needs update" with an explanation. A replaced article is marked "Superseded" and links to its replacement; it is not deleted or silently rewritten.

How the site is produced

Articles are written in Markdown, reviewed against a checklist (source verification, engine-version applicability, reproduction status, security-sensitive defaults, link validity, remaining uncertainty) and published from version control. Drafts are not reachable on the public site. There is no user tracking beyond optional, privacy-conscious page analytics, which is described on this page if enabled.

Contact

Editorial and technical questions: support@streampixel.io. Product questions belong in the Streampixel documentation or the community Discord.