yusing/godoxy
Godoxy
Godoxy is a Docker container orchestrator and reverse proxy manager. It provides a centralized system for managing the lifecycle, power states, and resource usage of virtualized containers, while routing HTTP, TCP, and UDP traffic to backend services with automatic route discovery.
The project distinguishes itself through an OIDC access control gateway that authenticates users via external identity providers and a resource optimization system that puts idle containers to sleep and wakes them automatically when network requests arrive. It also includes an automatic SSL certificate manager that handles issuance and renewal using DNS verification.
Additional capabilities cover traffic management through load balancing and container-aware routing. The system includes security primitives for attribute-based access control and observability tools for real-time log streaming and system resource tracking.
Features
- Docker Container Orchestrators - Provides a centralized management interface for controlling the lifecycle, power states, and resource usage of Docker containers.
- Reverse Proxies - Provides a high-performance reverse proxy that routes HTTP, TCP, and UDP traffic to Docker containers with automatic discovery.
- Container Lifecycle Administration - Provides a centralized interface for starting, stopping, and restarting virtualized containers with integrated health monitoring.
- Runtime State Routing - Automatically configures network routes based on the real-time presence and active state of virtualized containers.
- Traffic-Based Container Awakening - Conserves resources by putting idle containers to sleep and waking them automatically upon receiving new requests.
- Load Balancers - Distributes incoming network traffic across multiple container instances to ensure high availability and resource optimization.
- Automated Traffic Routing - Automatically discovers and binds network routes to containers using hostnames, IP addresses, or aliases.
- Traffic Routing - Forwards HTTP, TCP, and UDP traffic to backend services using configurable routing rules.
- OIDC Identity Integrations - Authenticates users via external identity providers using OIDC to restrict network traffic by IP or geography.
- Single Sign-On Integrations - Authenticates users via external identity providers using standard OIDC protocols to secure backend applications.
- SSL Certificate Managers - Automates the issuance and renewal of security certificates through DNS verification for proxied domains.
- Request-Driven Container Activation - Automatically wakes sleeping containers when network requests arrive to optimize server resource usage.
- Dynamic Power Optimization - Saves server resources by automatically sleeping idle containers and waking them on network requests.
- Dynamic Routing - Automatically maps network hostnames to active containers by detecting the current state of the container runtime.
- Attribute-Based Access Control - Implements a security layer that filters incoming network requests based on client attributes like IP range, country, or timezone.
- DNS-Based Certificate Issuers - Automates the issuance and renewal of SSL certificates using DNS-based verification challenges.
- Network Access Control - Defines and enforces security policies to regulate network traffic based on client addresses and geographic locations.
- Network Access Controls - Restricts incoming traffic based on client IP addresses, geographic locations, or specific time-based rules.
- Log Streaming - Provides real-time streaming of system and container logs via a persistent socket connection.
- Real-Time Application Log Monitoring - Allows users to view node and container logs in real-time using a persistent socket connection.
- System Health Monitors - Tracks uptime and core system metrics through a visual dashboard to ensure operational stability.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
