Platform Administration Console for managing Exploop Platform Agents, jobs, bootstrap tokens, and administrators.

The Admin UI provides operational management for the Rediver platform's shared agent infrastructure:

• Platform Agents - Monitor, drain, and manage shared agents
• Jobs - View, cancel, and retry platform jobs
• Bootstrap Tokens - Create and revoke agent registration tokens
• Administrators - Manage admin accounts and API keys
• Audit Logs - View all platform activity logs

• Node.js 22+
• npm 10+
• Running Platform Admin API (default: http://localhost:8080)

# Install dependencies
npm install

# Configure environment
cp .env.example .env.local
# Edit .env.local with your API URL

# Start development server
npm run dev

Access at http://localhost:3000

1. Obtain an admin API key from the platform
2. Enter the API key on the login page
3. API key is stored in memory (not persisted for security)

admin-ui/
├── src/
│   ├── app/                    # Next.js App Router
│   │   ├── layout.tsx          # Root layout
│   │   ├── page.tsx            # Dashboard (redirect)
│   │   ├── login/              # Login page
│   │   ├── (dashboard)/        # Protected routes
│   │   │   ├── layout.tsx      # Dashboard layout with sidebar
│   │   │   ├── page.tsx        # Dashboard home
│   │   │   ├── agents/         # Agent management
│   │   │   ├── jobs/           # Job management
│   │   │   ├── tokens/         # Token management
│   │   │   ├── admins/         # Admin management
│   │   │   └── audit-logs/     # Audit log viewer
│   │   └── api/health/         # Health check endpoint
│   │
│   ├── components/
│   │   └── ui/                 # shadcn/ui components
│   │
│   ├── lib/
│   │   ├── api-client.ts       # API client singleton
│   │   └── utils.ts            # Utility functions
│   │
│   ├── stores/
│   │   └── auth-store.ts       # Zustand auth state
│   │
│   └── types/
│       └── api.ts              # API type definitions
│
├── public/                     # Static assets
├── Dockerfile                  # Multi-stage Docker build
├── docker-compose.yml          # Development compose
├── docker-compose.prod.yml     # Production compose
└── package.json

NEXT_PUBLIC_API_URL=http://localhost:8080

# Start with docker-compose
docker-compose up

# Or build directly
docker build --target development -t admin-ui:dev .
docker run -p 3001:3000 -v $(pwd):/app admin-ui:dev

# Build and run
docker-compose -f docker-compose.prod.yml up --build

# Or build directly
docker build --target production \
  --build-arg NEXT_PUBLIC_API_URL=https://api.example.com \
  -t admin-ui:prod .
docker run -p 3001:3000 admin-ui:prod

The admin-ui is integrated into the main platform docker-compose files in setup/.

Staging:

cd setup

# Copy environment files
cp environments/.env.admin-ui.staging.example .env.admin-ui.staging

# Start all services including admin-ui
docker compose -f docker-compose.staging.yml up -d

# Admin UI accessible at http://localhost:3001

Production:

cd setup

# Copy and configure environment files
cp environments/.env.admin-ui.prod.example .env.admin-ui.prod
# Edit .env.admin-ui.prod with your API URL (NEXT_PUBLIC_API_URL)

# Start all services
docker compose -f docker-compose.prod.yml up -d

# Admin UI accessible via nginx reverse proxy

The app exposes /api/health for container health checks:

curl http://localhost:3000/api/health
# {"status":"ok","timestamp":"2026-01-26T12:00:00.000Z"}

Overview with platform statistics:

• Total/online/offline agents
• Pending/running/completed jobs
• Jobs per minute
• Active tenants

• List all platform agents with status
• Filter by status (online, offline, draining, unhealthy)
• Filter by region
• Actions: View details, Drain, Uncordon, Delete

• List all platform jobs
• Filter by status, agent, tenant
• Actions: View details, Cancel, Retry

• List bootstrap tokens
• Create new tokens with:
  • Description
  • Max uses
  • Expiration (hours)
  • Allowed regions
• Revoke tokens

• List admin accounts
• Create new admins with roles:
  • super_admin - Full access
  • ops_admin - Operations only
  • viewer - Read-only
• Update admin details
• Rotate API keys
• Delete admins

• View all platform activity
• Filter by:
  • Action type
  • Actor type
  • Date range
• View detailed event information

The Admin UI connects to the Platform Admin API. Key endpoints:

1. User enters API key on login page
2. API key is validated against /api/v1/admin/auth/validate
3. On success, admin info is stored in Zustand store
4. API key is attached to all requests via X-Admin-API-Key header
5. On logout, state is cleared from memory

Note: API key is stored in memory only, not in localStorage or cookies (for security).

• API keys use bcrypt hashing (SEC-C01)
• Account lockout after 10 failed attempts (SEC-H01)
• All admin actions are logged for audit
• Session is memory-only (no persistent storage)

# Install dependencies
npm install

# Run development server
npm run dev

# Run linter
npm run lint

# Build for production
npm run build

# Start production server
npm start

• Platform Agents Overview
• Platform Admin Guide
• Admin CLI Documentation
• Full Admin UI Documentation

MIT License - See LICENSE file for details.