Domain and Namespace List

This document provides a comprehensive overview of HungryHub’s domains and namespaces, categorizing them by their purpose and scope.

Architecture Classification

We categorize our servers into three main scopes to manage access and traffic flow:

Category	Description	Examples
Legacy	Current namespace for consolidated services	`hungryhub` namespace
Private	Internal services not exposed to the public	Sidekiq workers, background jobs
Public	Services with a public-facing URL	Web/Mobile APIs, Partner Portal API, Admin Dashboard

Our infrastructure is organized into the following Kubernetes namespaces:

Namespace	Purpose	Description
`hh-cosmos-private`	Sidekiq (Admin Dashboard)	Background job processing for admin dashboard
`hh-cosmos-public`	API (Admin Dashboard)	Public API endpoints for admin dashboard
`hh-end-user-private`	Sidekiq (Web/Mobile)	Background job processing for web and mobile applications
`hh-end-user-public`	API (Web/Mobile Production)	Production API endpoints for web and mobile applications
`hh-felidae`	Felidae Project	Dedicated namespace for the Felidae project
`hh-syn-private`	Sidekiq (Partner Portal)	Background job processing for partner portal
`hh-syn-public`	API (Partner Portal)	Public API endpoints for partner portal
`hh-vendor-public`	API (Vendor)	Public API endpoints for vendor services
`hungryhub`	Legacy (Main Namespace)	Note: Will be removed soon

Domain	Purpose	Namespace
`https://partners-api.hungryhub.com`	Partner Portal API	`hh-syn-public`
`https://cosmos.hungryhub.com`	Admin Dashboard	`hh-cosmos-public`
`https://internal-api.hungryhub.com`	Web/Mobile API	`hh-end-user-public`
`https://hungryhub.com`	Web/Mobile UI	`hh-end-user-public`
`https://api.hungryhub.com`	Vendor API	`hh-vendor-public`

The following domains are currently being configured for vendor integration API:

Status: Vendor integration API is still in progress

Public namespaces (*-public) contain services accessible via public URLs
Private namespaces (*-private) contain internal services like Sidekiq workers for background processing
Each public-private pair (e.g., hh-cosmos-public and hh-cosmos-private) represents a complete service stack

⚠️ Important: The hungryhub namespace is scheduled for deprecation. All services should be migrated to the appropriate namespaced environments: