.pr roadmap files
Roadmap files contain the production roadmap data needed to open, share, and review a plan.
Security / IT validation
Designed for studio IT approval.
ProdRoads is a local-first desktop application designed to be easy to inspect, deploy, and approve in production environments.
Local-firstNo cloud requiredNo telemetryNo background servicePer-user installationNo administrator privileges requiredStandard Windows applicationSHA-256 hashesRead-only Reader available
Security philosophy
Security starts with keeping your data under your control.
ProdRoads stores roadmap files where your studio decides, works without cloud infrastructure, and only performs actions explicitly requested by the user.
Application behavior
What ProdRoads does, and what it does not do.
| Behavior | Does | Does not |
|---|---|---|
| Store roadmap files locally | ✓ | |
| Open .pr and .prw files | ✓ | |
| Open approved external links | ✓ | |
| Save user workspace settings | ✓ | |
| Associate roadmap files with the desktop app | ✓ | |
| Upload project data | × | |
| Require cloud services | × | |
| Run background processes | × | |
| Modify files without user action | × | |
| Collect usage analytics | × |
Data and files
Roadmap data stays in files your studio controls.
.prw workspace files
Workspace files contain reusable setup data such as teams, key dates, and developer lists.
Studio-controlled storage
Files can live where your studio already stores production data: local disks, shared drives, NAS, SharePoint, OneDrive, Git, or other managed storage.
No ProdRoads server
ProdRoads does not require a ProdRoads-hosted cloud service to open or edit roadmap files.
External links
Roadmap editors can attach links to roadmap blocks. Links open only after explicit user action and unsafe URL schemes are blocked.
Installation and deployment
Standard Windows application.
- Standard Windows desktop application
- Per-user installation path
- Editor can associate .pr and .prw files
- Reader can associate .pr files for read-only opening
- No administrator privileges required for standard installation
- Editor and Reader can coexist on the same machine
Release verification
Every release can be verified.
ProdRoads release packages are prepared with practical validation material so studios can verify what they install.
Available now
- Version history
- Release notes
- SHA-256 hashes
- Local antivirus scan
Planned
- VirusTotal report
- Code signing
Validation resources
Documents for
deeper IT review.
IT validation guide Download the current deployment, data handling, network behavior, and release verification summary. Download PDF Release notes Version history, installer names, SHA-256 hashes, scan notes, and known issues. Installation guide Install path, file associations, uninstall behavior, and Reader / Editor coexistence. File format What .pr and .prw files contain, including roadmap data and workspace information. Privacy policy Telemetry, local data, account requirements, and user-controlled storage.
Need help with a studio security or IT review? Contact support@prodroads.com.
IT FAQ
Common validation questions.
Can ProdRoads be used completely offline?
Yes. The desktop application is designed around local files and does not require a cloud service to open roadmap data.
Does ProdRoads require an account?
No account is required for the current local desktop workflow.
Does ProdRoads collect analytics?
No. The current desktop application does not send usage analytics or product telemetry.
Where is project data stored?
Project data is stored in files controlled by the user or the studio, such as .pr roadmap files and .prw workspace files.
Can Reader open files without editing them?
Yes. Reader is read-only and is intended for broad distribution to people who need visibility without edit access.
Can files be stored on SharePoint or OneDrive?
Yes. ProdRoads files can be stored in company-managed locations. Sync behavior is controlled by the storage provider.
Does standard installation require administrator privileges?
No. The standard Windows installer uses a per-user installation path.
Is the installer signed?
Code signing is planned for a later release. Current test packages include validation material such as release notes and hashes.