Nest Backend Platform

Introduction

The Nest Backend Platform is Phenom’s comprehensive backend infrastructure hosted at https://nest.thephenom.app/. It consists of two primary applications:

1. Nhost Backend Service - Authentication, storage, and GraphQL API
2. Admin Dashboard - Command center for UAP data management and monitoring

Access & Authentication

Authentication Flow

Reference URLs:

• OAuth 2.0 Authorization Framework
• GitHub OAuth Applications
• Cloudflare Access - Authorization Policies

Cloudflare Zero Trust OAuth

The Nest platform is secured using Cloudflare Zero Trust with OAuth-based authentication through GitHub.

Access Requirements:

• GitHub Account: Must be a member of the phenom-earth organization
• Team Membership: Must belong to the INT (Internal) team
• Authorized Users: Including smsmatt and other internal team members

Access URL: When navigating to nest.thephenom.app, users will be redirected through Cloudflare Access login and authenticated via their GitHub account.

OAuth Providers

The platform supports multiple authentication methods:

• GitHub OAuth (primary for team access)
• Google OAuth
• Apple OAuth
• LinkedIn OAuth
• Email/Password authentication
• Magic link authentication
• Security key (WebAuthn) authentication

Platform Architecture

Technology Stack

Frontend:

• React 18/19
• Vite (build tool)
• TanStack Router
• Apollo Client (GraphQL)
• Shadcn UI + Tailwind CSS

Backend:

• Nhost - Open-source Firebase alternative
• Hasura - GraphQL engine
• PostgreSQL - Primary database
• Firebase - Admin dashboard authentication
• AWS Cognito - User authentication with JWT tokens (migration from Nhost auth)

Deployment:

• Hosting: Cloudflare Pages / Netlify
• Functions: Cloudflare Workers
• Access Control: Cloudflare Zero Trust
• Infrastructure: AWS EC2 (development/staging)

System Architecture

Reference URLs:

• Cloudflare Zero Trust - Access
• GitHub OAuth

Key Services

1. Authentication Service (http://localhost:9000/v1/auth)

   • User registration and login
   • OAuth provider integration
   • Session management
   • Token refresh

2. GraphQL API (http://localhost:8080/v1/graphql)

   • Hasura-powered GraphQL endpoint
   • Real-time subscriptions
   • Role-based access control

3. Storage Service (http://localhost:9500/v1/storage)

   • File upload and management
   • Image processing
   • Secure file access

4. Serverless Functions (http://localhost:9999/v1/functions)

   • OpenSky API proxy (aircraft tracking)
   • Custom business logic

Primary Use Cases

1. Global Phenomenon Monitoring

Track and manage UAP (Unidentified Anomalous Phenomena) events globally with:

• Real-time aircraft tracking via OpenSky Network API
• 3D globe visualization
• Interactive map views
• Location-based event data

2. User & Team Management

• Role-based access control
• Team member administration
• Permission management
• Activity logging

3. Data Collection & Organization

• Phenomenon event tracking
• Associated “shoots” (recording sessions)
• Geospatial data management
• Timestamp-based organization

4. Administrative Operations

• Dashboard analytics
• System settings
• Task management
• Notification system

Repository

GitHub: Phenom-earth/phenom-backend

Directory Structure:

phenom-backend/
├── server/phenom/              # Nhost React Apollo backend
├── admin_sandbox/phenom/       # Admin dashboard application
├── adsb/                       # ADSB aircraft tracking service
│   ├── airnav/                 # AirNav RadarBox API CLI
│   └── run-phenoms/            # Phenom-to-aircraft correlation
├── db/
│   ├── schema/                 # Database schemas
│   └── hasura-auth/            # Authentication submodule
└── utils/                      # Deployment utilities

External Integrations

OpenSky Network API

• Purpose: Real-time aircraft tracking data
• Integration: Proxied through Cloudflare Functions
• API Client: jonathan_at_phenom-api-client
• Features:
  • Token caching (Cloudflare Workers KV)
  • CORS handling
  • Automatic token refresh

AirNav RadarBox API

• Purpose: Real-time and historical aircraft tracking data for phenom correlation
• Integration: Direct API calls from ADSB service module
• Features:
  • Query flights by geographic area
  • Correlate aircraft positions with phenom sighting locations
  • Automatic phenom record updates with nearby aircraft data

Google Maps API

• Purpose: Map visualization and geocoding
• Usage: Admin dashboard map views

Firebase

• Project: phenom-7ee1a
• Purpose: Admin dashboard authentication and data storage
• Database: Firestore for phenomenon data

Security & Compliance

Authentication Security

• Multi-factor Authentication: WebAuthn/Security keys supported
• Session Management: Secure token-based sessions
• OAuth 2.0: Industry-standard OAuth flows
• Zero Trust Architecture: Cloudflare Access integration

Access Control

• Organization-level: phenom-earth GitHub organization
• Team-level: INT team membership required
• Role-based: Granular permission system
• Audit Logging: User activity tracking

Data Protection

• Encryption: TLS/SSL in transit
• Authentication: Required for all API access
• Authorization: Role-based data access
• Compliance: OAuth in development for enhanced security

Development Status

Current Status: Active development ongoing as of February 2026, with ADSB integration and Cognito authentication as primary work streams.

In Development:

• ADSB aircraft tracking integration with AirNav RadarBox API
• AWS Cognito authentication integration with Hasura
• Aircraft visualization with interactive rays and metadata overlays
• Enhanced admin dashboard with expanded display lists
• User Content Curation Lists (#55) — Named curated lists with D1 storage, list/item sharing between CF Access team members, profile hub as personal command center
• Mobile Responsive Map (#56) — Draggable bottom sheet replaces sidebar overlay on mobile (<768px), Google/Apple Maps-style UX

Known Limitations:

• Phenomenon deletion disabled until OAuth completion
• Local development configured for localhost URLs
• Map sidebar blocks content on mobile devices (fix in progress — #56)

Related Documentation

• Admin Dashboard Details
• Nhost Backend Service
• ADSB Aircraft Tracking

Support

For access issues or technical support, contact the internal development team or reference the GitHub repository.