Metadata can be stripped
File-level context can disappear during export, compression, reposting, and platform processing.
Official Public Preview
Invisible authenticity infrastructure for digital media.
Roadscript embeds invisible authenticity signals directly into media content. Cyphra helps users verify whether media still carries a valid Roadscript authenticity signal.
Public preview note: packaged downloads are still on the roadmap. Today's public surface
focuses on the landing experience, interactive demo, and local-first verification direction.
GIF / WebM Placeholder
Product preview / verification animation placeholder
Reserve this area for a future Roadscript verification walkthrough showing media entering Cyphra, authenticity being checked, and the verification result surfaced in a clear product flow.
Future screenshot, product animation, or short verification clip for the official public landing page.
Roadscript trust signals
Content-layer signal
Designed to travel with the media rather than depend only on surrounding metadata.
Local-first verification
The roadmap prioritizes verification workflows that do not require unnecessary uploads.
Honest roadmap
This site and demo are public previews of a larger engineering and product direction.
Why this matters
Why metadata-only provenance breaks down.
Roadscript focuses on content-layer authenticity because screenshots, reposts, edits, and normal platform handling do not preserve fragile file-level provenance by default.
Screenshots break provenance
Screen-captured or transformed copies make it harder to rely on external provenance alone.
AI-generated and edited media is harder to verify
Audiences increasingly need clearer ways to evaluate authenticity beyond source claims or visual intuition.
Media needs authenticity at the content layer
Creators, platforms, and users need signals designed to travel with the media itself.
Roadscript + Cyphra
From invisible authenticity signals to readable verification.
Roadscript is the content-layer system. Cyphra is the user-facing verification experience designed to make authenticity checks easier to interpret and eventually easier to integrate.
Embed and verify authenticity signals inside the media layer.
The core system is being built around robust embedding, decode, and verification workflows.
Translate verification results into a product experience people can actually use.
Cyphra is the user-facing layer for checking whether media still carries a valid Roadscript signal.
Visual Demo
See Roadscript in action.
These tiles are placeholders for future GIF or WebM loops that will show Roadscript and Cyphra behavior more directly.
Verify watermark
Coming soonShow Cyphra checking whether media still carries a valid Roadscript authenticity signal.
GIF/WebM placeholder: verifying media in Cyphra
Screenshot survival
Coming soonDemonstrate robustness goals around screenshot-style transformations and downstream sharing.
GIF/WebM placeholder: verification after screenshot-style transformation
Tamper detection
Coming soonPreview how edited media could fail verification or return a changed authenticity result.
GIF/WebM placeholder: edited media fails or changes verification result
Engineering credibility
Engineering signals for a real system.
The deeper technical detail belongs in the whitepaper and solution pages. The homepage only keeps the signals that help visitors understand Roadscript as a real engineering effort.
128-bit payload
Structured payload design for authenticity-oriented workflows.
CRC-protected verification
Integrity-aware verification rather than loose visual checking alone.
Modern C++ engine
Performance-oriented native core with decode and verification ambitions.
Local-first processing
Verification direction centered on minimizing unnecessary media uploads.
Sub-second verification target
A product goal for responsive checks as benchmarks and packaging mature.
Roadscript ecosystem
The product family around Roadscript.
The homepage should invite people deeper into the ecosystem, not try to explain every surface in full on first load.
Roadscript Engine
Core watermarking and verification engine.
Cyphra App
User-facing authenticity verification experience.
Roadscript CLI
Developer and power-user command-line workflow.
SDKs
Future integration layer for apps, services, and creator tools.
Docs
Technical documentation, architecture notes, and usage guides.
Read docsWebsite Demo
Public interactive demo and product explanation.
Open demo
FAQ
Key questions, answered briefly.
What is Cyphra?
Cyphra is the user-facing app for verifying Roadscript-authenticated media. It is designed to make authenticity checks simple for creators, users, and developers.
How is Roadscript different from metadata?
Metadata lives beside the file and can often be stripped, edited, or lost. Roadscript focuses on content-layer authenticity signals that are embedded directly into the media itself.
Does it survive screenshots?
Screenshot survival is one of the key robustness goals. The Roadscript engine is being designed and tested around transformations such as screenshots, recompression, and resizing.
Are images uploaded to a server?
The roadmap prioritizes local-first processing where possible. Verification should not require unnecessary media uploads unless a future cloud feature explicitly needs it.
Next step
Try the verification workflow, then keep exploring.
The current demo is a guided public preview built to communicate the Roadscript direction with sample media and verification-oriented product states. Use it as the main interactive entry point, then continue into docs, roadmap, or GitHub.