# Your Newsroom, Your Data

> Portable S3-backed sources, open code, and an installation you control—so the publication's memory stays yours.

By Papyrus Editorial Team · Published 2026-05-22

Canonical: https://read.p.apyr.us/papyrus/papyrus-data-ownership/

A publication's sources, curation record, and policies are institutional memory. Papyrus stores source material through ordinary S3-backed corpus patterns, with metadata that describes provenance and how the newsroom should treat each reference.

That memory should stay portable. References, attachments, extracted text, catalogs, relationships, and curation decisions can be inspected, backed up, processed, or moved without negotiating with a proprietary format.

S3 is a durable, boring boundary. You can run enrichment next to it, export manifests, audit material, or connect another analysis system without asking permission to reach your own files.

The application code is open. A publication can host its own installation, adapt workflows, customize layouts, and add policies that match its mission.

Operators can trace what happens, replace pieces, or extend them. Newsroom procedures, the content CLI, layout plans, and data models are code and configuration—not hidden product magic.

Self-hosting remains an option when an organization wants full operational leverage. Managed deployment can be convenient; ownership of the memory should not be forfeited.

The practical test is simple: if you leave, you should still have your sources, your catalog, your curation record, your policies, and the means to understand how the system worked. Papyrus should help you build a newsroom you control.