Judemy Control Center

Operations dashboard

Deploy on its own host. Use separate DB config files per area under admin/config/ (db.judemy.php, db.judemind.php, db.ide.php, db.judemind-api.php). Ecosystem links use JUDEMY_ECOSYSTEM_* env vars.

— Modules wired

4 Dashboard pillars

RBAC Next: roles

Judemy

Public platform, auth, learn, library, tools.

Ecosystem URL: https://www.judemy.com

Open site Users

Judemind

Judemy AI / JudeMind product & API usage.

Ecosystem URL: https://www.judemy.com/products/ai

Open site Users

APIs

JudeMind HTTP API, keys, quotas, integrations.

Ecosystem URL: https://api.judemind.com

Open site

IDE

Judemy IDE web/desktop and releases.

Ecosystem URL: https://www.judemy.com/products/ide

Open site

Judemy platform

Site · auth · tools · library

Future controls: user management, content flags, builder tools health, migrations, and feature toggles for the main Judemy tree. Super Admin sees all; Staff access will be granular per resource.

Judemind (Judemy AI)

Models · usage · safety

Future controls: model routing, JudeMind product settings, prompt/safety policies, and alignment with api.judemind.com operations.

APIs

Keys · quotas · gateways

Future controls: API key lifecycle, rate limits, webhook endpoints, and integration with Judemy services and external partners. Scoped API secrets stay server-side only.

Judemy IDE

Builds · releases · flags

Future controls: IDE distribution channels, version rollouts, experimental features, and telemetry summaries (privacy-preserving).