Skip to content

Roadmap

The platform is actively evolving. These are the main initiatives we're working towards.

New curriculum support

Our curriculum is changing: first-year students will work on at least 4 different group projects throughout the year. The platform needs to support onboarding and isolating these projects efficiently — likely requiring automation around namespace provisioning, database setup, and template repositories at a larger scale than the current single-course setup.

Additionally, this provides the opportunity to gradually introduce students to infrastructure concepts over time, starting with the fully preconfigured Tier 1 (like current PRJ2) experience in their first project, and then giving them more control and responsibility in later projects (Tier 2, see below).

Tier 2: student-managed infrastructure

Where Tier 1 (the current PRJ2 setup) gives students a fully pre-configured environment, Tier 2 is for later-stage projects where students bring their own tech stack and are exposed to setting up parts of their own infrastructure and observability.

This means giving students scoped access to:

  • Define their own delivery flows
  • Configure their own monitoring dashboards and alerts
  • Choose their own database, runtime, or framework

When we speak of 'Tier 2', it's more of a conceptual stage in the learning journey rather than a hard technical boundary. As we will gradually introduce more control to students, it goes hand in hand with the curriculum design. The aim could be for semester 7 projects to define Tier 2,leaving a lot of design space between Tier 1 (semester 1) and Tier 2 (semester 7).

Authentication and authorization

We are integrating our identity provider for the platform's internal tools — ArgoCD, Harbor, and Grafana. This enables different things:

  • Maintenance by other coaches — colleagues can access and manage platform tools without needing individual accounts on each service.
  • Self-service for advanced projects — teams with different needs (e.g., custom deployments, alternative tech stacks) can get scoped access to the tools they need.
  • Auth for projects - projects can use the platform's identity provider for their own applications, enabling features like single sign-on and role-based access control without needing to set up their own auth infrastructure. This is already in production for the SPoHF research project.