Aerod Run checks

docs

NetPeek Integration Notes

Implementation notes for mounting the separate NetPeek app into the reserved /apps/netpeek route.

By Aerod Engineering Reviewed by Aerod Editorial Published July 1, 2026 Updated July 1, 2026

Current status

The /apps/netpeek route is reserved as a placeholder. The full NetPeek app is maintained separately and will be added later.

Until the real app is mounted, the placeholder page is set to noindex so search engines do not index a temporary integration shell.

Integration target

When NetPeek is ready, the route should become a full-page app while preserving the Aerod shell where useful:

  • Page metadata.
  • Header/footer behavior if the app allows it.
  • Data-handling links.
  • App methodology links.
  • Related app and guide links where they do not interrupt the app flow.

Preferred integration approach

Use the existing app logic and mount it into the Aerod route with the least risky refactor. The goal is to avoid breaking the working app while making it feel native to Aerod.

Pre-launch checks

Before removing the placeholder state:

  • Confirm the app builds in the Cloudflare Pages environment.
  • Confirm required browser APIs work after deployment.
  • Confirm no raw fingerprint data is stored by default unless explicitly intended.
  • Update /apps/netpeek metadata and sitemap behavior.
  • Remove noindex from the NetPeek page.