01
PRESERVE
Sign the incident record before changing production.
WEBSITE INTEGRITY // WITNESS MESH
Your website should only change when you change it.
Connect GitHub once. Deploy normally. Witness Mesh correlates source, provider, live site, and an independent GhostHue ledger. If production stops matching, Autopilot preserves the evidence, restores the trusted release, and contains the site when the origin cannot remain trustworthy.
$9.99 per protected website / month · Connect once · Deploy normally
State sequence: verified, watching, ready.
WITNESS MESH
No single observation authorizes a release.
GhostHue correlates GitHub, the hosting control plane, the live site, and an independent ledger. Agreement between two compromised systems is never enough.
01
Source
GitHub
Repository, branch, commit, workflow identity, and production environment.
02
Build
GitHub OIDC + GhostHue Action
OIDC claims, artifact digest, and seal digest from the approved workflow.
03
Provider
Hosting control plane
Immutable deployment, revision, or version bound to the selected host target.
04
Live
Public production
Decoded PNG seal, protected bytes, headers, DNS, and TLS from independent fetches.
05
Ledger
GhostHue
Append-only signed event chain stored outside GitHub and the customer host.
Witness Mesh has five classes: GitHub source, GitHub OIDC build, hosting provider, live production, and an independent GhostHue ledger. No single witness authorizes a release or recovery action.
Five witness classes. One authorized release.
CERTIFIED COMBINATIONS
GitHub is required. Eight hosting profiles can be certified.
Every protected site uses one GitHub repository, one production branch, and one hosting profile. A combination is advertised as available only after production certification. AWS means Amplify Hosting or S3 + CloudFront. Google Cloud means Firebase Hosting or Cloud Run. Azure means Static Web Apps.
GitHub
Vercel
Coming
GitHub
Firebase Hosting
Coming
GitHub
Cloudflare Pages
Coming
GitHub
AWS Amplify Hosting
Coming
GitHub
AWS S3 + CloudFront
Coming
GitHub
Netlify
Coming
GitHub
Google Cloud Run
Coming
GitHub
Azure Static Web Apps
Coming
Unsupported configurations cannot start billing.
02 // The problem
A successful deployment does not prove production stayed that way.
Hosting dashboards show what was deployed, not necessarily what every visitor is receiving now.
Compromised credentials, altered files, third-party scripts, or provider drift can change production after deployment.
Small teams often discover defacement or injected code only after a customer reports it.
GhostHue maintains an independent definition of the last authorized public release.
| Authorized pipeline | Signed release |
|---|---|
| Public production | Independent observation |
| Result | Match / mismatch |
03 // GhostHue Autopilot
Everything works together automatically.
There is no security-mode menu to manage. Every eligible GhostHue site uses Autopilot. GhostHue determines which verified protection should act and when.
01Witness MeshCorrelates GitHub, build, provider, live site, and GhostHue ledger observations
02SealBinds each authorized release to a signed manifest and invisible PNG marker
03MonitorChecks the live public site independently from the hosting dashboard
04SentinelWatches supported runtime behavior inside real browser sessions
05PreserveCreates a signed incident evidence bundle before recovery actions
06ReflexRestores the exact last verified provider release
07MirageServes a pre-approved static 503 containment page if restoration cannot remain trustworthy
04 // How it works
No routine GhostHue step after setup
01
CONNECT ONCE
Connect GitHub and one certified hosting profile.
02
DEPLOY NORMALLY
GhostHue automatically signs the authorized build, embeds its seal, and prepares the shadow.
03
VERIFY CONTINUOUSLY
Witness Mesh compares GitHub, provider, live site, and ledger observations with the authorized release.
04
RESPOND AUTOMATICALLY
Confirmed mismatches are preserved before Reflex restores the trusted release.
05
ISOLATE WHEN NECESSARY
If tampering returns, Mirage serves the verified read-only shadow.
06
RETURN SAFELY
GhostHue tests the origin and gradually restores traffic after it proves trustworthy.
05 // Incident
What visitors and the developer experience
| Stage | Visitor | Developer |
|---|---|---|
| Normal | Uses the normal verified site | Deploys normally |
| Change detected | Continues using the site while GhostHue confirms | Receives no premature alarm |
| Reflex | Usually sees no interruption | Receives a clear confirmed-incident notice |
| Repeated alteration | Receives the verified read-only Mirage release | Secures credentials while evidence remains preserved |
| Recovery | Traffic returns gradually | Receives one recovery summary |
06 // Seal + Sentinel
The seal identifies what belongs. Sentinel watches what happens.
The PNG carries a non-secret release binding in nearly identical pixel values.
The private key is never placed in the image or browser.
The PNG does not execute code.
Sentinel is a separate, small, versioned, integrity-pinned browser agent.
Copying, deleting, or replacing an old seal does not authorize a fraudulent release.
Security remains valid even if the seal format becomes public.
Decorative pixel-grid visualization of a seal sample point.
07 // Automatic response
02
REFLEX
Restore an exact verified provider release.
03
MIRAGE
Keep a verified read-only version available when the origin remains unstable.
Protected by GhostHue Reflex. Unauthorized changes don’t stay—and the evidence doesn’t disappear.
GhostHue confirms production mismatches; it does not identify who caused them or replace account security, backups, a WAF, vulnerability management, or incident investigation.
Designed to help with
- Unauthorized changes to protected public assets
- Unknown or replayed production releases
- Runtime script and form-policy anomalies supported by Sentinel
- Rapid exact-release restoration
- Repeated public defacement continuity
- Signed incident metadata
Not designed to replace
- MFA and provider account protection
- WAF/DDoS services
- Malware or vulnerability scanning
- Database and private API security
- Secure source-code review
- Backups and business disaster recovery
- Human investigation of the original access path
GhostHue verifies configured public assets and supported browser behavior. It does not replace account security, secure development, a WAF, vulnerability management, backups, or incident investigation.
09 // Who it is for
- Independent developers
- Small SaaS teams
- Agencies protecting client sites
- Small online businesses with developer-managed hosting
- Public information and documentation sites
Source requirement
GitHub is required for every protected site.
10 // Pricing
GHOSTHUE
$9.99
per protected website / month
14 days free
Cancel anytime
- Always-on Autopilot for certified sites
- Witness Mesh across GitHub, host, live site, and GhostHue ledger
- Automatic signed releases and invisible PNG seal
- Independent production monitoring
- Sentinel runtime protection as compatibility permits
- Signed Preserve incident records
- Reflex exact-release recovery
- Verified Mirage standby and automatic re-entry as compatibility permits
- Email incident and recovery alerts
- 30-day detailed history
Mirage and active response require a certified GitHub-to-host configuration, supported provider permissions, and successful readiness checks. GhostHue reports unavailable capabilities instead of pretending they are armed.
START 14-DAY TRIALThe trial begins only after the site is certified and the first release becomes current.
11 // FAQ
Does GhostHue prevent every hack?
No. GhostHue verifies configured public assets and supported browser behavior. It does not replace account security, a WAF, vulnerability management, or incident investigation.
Is the PNG itself executable?
No. The seal is a non-secret release binding in nearly identical pixel values. The private key is never placed in the image or browser. The PNG does not execute code.
What happens when I deploy a normal update?
GhostHue automatically signs the authorized build, embeds its seal, and prepares the shadow. A matching deployment is not treated as an incident.
Can GhostHue restore a site automatically?
When readiness checks pass, Autopilot can restore an exact previously verified provider release. This is not a general database backup or disaster-recovery platform.
What does Mirage show visitors?
A verified read-only shadow of the last trusted static release. Forms and state-changing requests do not run. Mirage stays in standby until the origin cannot remain trustworthy.
Does GhostHue store malicious files?
No. Preserve writes a signed, metadata-only incident record of expected-versus-observed fingerprints. Altered website files are never stored.
Can I pause automatic actions during an incident?
Yes. Authorized users can pause new Reflex, Mirage, and automatic return actions for up to 24 hours. Monitoring and alerts continue. This is an emergency control, not a permanent manual plan.
Does GhostHue replace Cloudflare or another WAF?
No. GhostHue is complementary. It does not replace a WAF, DDoS service, MFA, or provider account protection.
What is Witness Mesh?
Five correlated observations of one release: GitHub source, GitHub OIDC build, hosting provider, live production, and an independent GhostHue ledger. No single witness can authorize a release or recovery action.
Which websites can GhostHue protect?
GitHub is required. GhostHue certifies eight GitHub-to-host combinations. A profile is shown as available only after production certification. Unsupported configurations cannot start billing.
When does the 14-day trial start?
The trial begins only after the site is certified and the first release becomes current, not when the account is created.
Deploy normally. Let GhostHue watch what production becomes.
One site. One plan. Always-on Autopilot. $9.99 per month after the 14-day trial.