Authentication & Security
Login, roles, permissions, access control, audit logs
How we build
The process behind the SKS ecosystem. Follow each stage from planning and modular development to testing, deployment, and maintenance.
A web application for administration, system monitoring, AI resource management, and development tracking. Accessible in modern browsers on desktop, tablet, and mobile. Each authorised user sees only the functions for their role.
Login, roles, permissions, access control, audit logs
User accounts, departments, role assignment, project access
System overview, project status, AI usage, alerts
Projects, milestones, owners, priorities, project status
Progress updates, developer notes, completion %, issues, reviews
Cloud models, local models, model routing, model access
AI usage, quotas, budgets, limits, cost tracking
System health, AI services, performance, errors, alerts
System settings, AI settings, usage policies, configuration
Project files, documents, screenshots, version history
Connect Projects A–E, APIs, webhooks, external services
| Area | This pass | Later |
|---|---|---|
| Frontend | Next.js, React, TypeScript | Vercel hosting |
| Data | Typed local store | Supabase PostgreSQL |
| Authentication | Demo roles in the browser | Supabase Auth + RLS |
| Files | Catalog and version list | Cloudflare R2 |
| AI Gateway | Routing board | Cloud and local model keys |
| Automation | In-app audit trail | n8n workflows |
Stage 01
Next.js, React, TypeScript, project structure, and core APIs. This local checkout is the foundation. Supabase, Vercel, and Cloudflare R2 stay as later environments.
Stage 02
Login, accounts, roles, permissions, and access control for the five control-center roles.
Stage 03
Main dashboard, project records, milestones, status, and team assignment across the ecosystem.
Stage 04
Developer updates, project progress, issues, and blockers.
Stage 05
Cloud and local model connection, routing, usage tracking, quotas, and budgets.
Stage 06
System monitoring, alerts, logs, configuration, and administrative controls.
Stage 07
Connect Project 0 with Projects A–E and external services. Project E is the local SKS TECH desk.
Stage 08
Integrate all modules, resolve issues, and prepare the system for testing and deployment.
Authentication, user management, permissions, project functions, usage control, AI gateway, APIs, and store functions.
Frontend and store, Project 0 to Projects A–E, local desk link for Project E, files, and notifications.
Full user workflows, security, dashboard, project tracking, AI gateway, usage control, monitoring, and overall behaviour.