The Agile Network — Platform Overview

What Is The Agile Network?

The Agile Network (theagilenetwork.com) is a platform connecting sports fans with professional athletes, coaches, and sports personalities (“Experts”) for live experiences, video content, and professional development. Originally built under the name “Peeq” by VelocityZ Labs (vzlabs), it has evolved into a multi-brand platform supporting several verticals.

Brand Portfolio

The platform operates under multiple brands, each targeting a different market:

Each production brand shares the same backend infrastructure (same Docker images, same Helm charts) with config-only differentiation via values-globals.yaml. Frontend theming is distinct per brand (CSS, assets, logos, web manifests).

Core User Types

Core Features

Live Broadcasting

• Mux-powered livestreams — one-to-many live video broadcasts from experts
• Jitsi interactive video — two-way video for meet-and-greets, Q&A sessions
• Conference/webinar — multi-participant video events
• Recording and replay — recorded sessions available as on-demand content

Shoutouts

Personalized video messages from experts to fans. Fans request, experts record, fans receive. Similar to Cameo’s business model.

Content & Media

• Video content (uploaded + livestream recordings)
• Articles and written content
• Resources and educational materials
• SEU/PDU tracking (continuing education credits)
• Photo processing (thumbnails, blur variants, multiple sizes)

Subscriptions & Payments

• Stripe — subscription billing, one-time purchases, payment processing
• Dwolla — ACH disbursements to experts (wallet/payout system)
• Tixr — event ticketing integration for in-person events
• Wallet — internal wallet system for expert earnings

Events

• In-person events with ticketing (Tixr integration)
• Virtual events (broadcasts, webinars, meet-and-greets)
• Class catalog for scheduled sessions
• Inventory management for event capacity

Identity & Authentication

• Keycloak — OAuth2/OIDC identity provider
• Custom Keycloak themes per user type (celebrity, fan, handler)
• SSO across all brand frontends
• CIB Seven Keycloak integration

Communication

• In-app messaging (message board, direct messages)
• Email notifications (transactional)
• SMS notifications
• Push notifications
• WebSocket real-time updates
• Server-Sent Events (SSE) for live updates

Search & Discovery

• Elasticsearch for content and expert search
• Tags and categorization system
• Recommendation engine
• Group profiles and organization pages

Business Model

1. Subscription revenue — Fans subscribe to expert channels (recurring via Stripe)
2. One-time purchases — Shoutouts, event tickets, premium content
3. Platform fee — Percentage of transactions between fans and experts
4. Event revenue — Ticketed events (in-person and virtual)
5. Organization partnerships — Organizations sponsor expert groups

Data Pipeline & Analytics

• Airbyte — ETL data integration
• DLT pipelines — Data loading/transformation
• Superset — Business intelligence dashboards
• Reporting service — Custom reports
• Node tracking — User behavior analytics

Infrastructure

• Google Kubernetes Engine (GKE) — Container orchestration
• ArgoCD — GitOps continuous deployment
• Terraform — Infrastructure as code
• Helm charts — Kubernetes package management
• Jenkins X — Legacy CI/CD (being replaced)
• GitHub Actions — Current CI/CD
• PgBouncer — PostgreSQL connection pooling
• RabbitMQ — Message queue
• Elasticsearch/Kibana — Search and logging

Platform Evolution

Generation 1: “Peeq” (Legacy)

• 107 peeq-* prefixed repositories
• Java 11, Spring Boot 2.6.8
• Fine-grained microservice decomposition (separate repos for service, DB, BPM)
• Jenkins X CI/CD
• Package group: com.peeq

Generation 2: “VelocityZ” (Current)

• Non-prefixed repos (celebrity, fan, content, broadcast, etc.)
• Java 21, Spring Boot 3.5.4
• Package group: com.velocityz
• Shared core libraries (core-lib, messages)
• GitHub Actions CI/CD
• Consolidating some microservices

Generation 3: “NexGen” (Planned)

• nexgen repository (currently empty scaffold)
• Target: modern architecture, reduced service count
• This knowledge base documents the path from Gen 1/2 to Gen 3

Key Technical Patterns

Service Decomposition (Gen 1)

Each domain concept has up to 4 repos: - peeq-{domain} — Business logic service (Java/Spring Boot) - peeq-{domain}-db — Database migrations (Flyway SQL) - peeq-{domain}-bpm — Business process definitions (Camunda/CIB Seven) - peeq-{domain}-query — Read-optimized query service (CQRS pattern)

Frontend Architecture

• peeq-mono — Angular 18 / Nx / Ionic monorepo (web + mobile)
• frontends — Angular 14 / Nx monorepo (admin, celeb, org-dashboard)
• landing-page — Marketing/landing page
• Multi-brand theming with dynamic CSS loading
• Component library: @vzlabs/ui (peeq-mono) and @vzlabs/peeq-ui (frontends)

Database Strategy

• PostgreSQL as primary database
• Per-service database isolation (each service has its own DB)
• Flyway for schema versioning
• PgBouncer for connection pooling
• H2 for local development/testing

BPM (Business Process Management)

• Camunda / CIB Seven process engine
• Process definitions in *-bpm repos
• Key workflows: broadcast lifecycle, shoutout fulfillment, meet-and-greet, purchase requests, recording management

Last updated: 2026-01-30 Source: Codebase analysis of 191 repos from favedom-dev GitHub org + theagilenetwork.com