Monoskope: Developer Self-Service Across Clusters

How can you give developers self-service across Kubernetes clusters while maintaining strict compliance? This open-source control plane makes auditability a first-class citizen.

#1about 4 minutes

The platform challenges of multi-cluster financial services

Finley Cloud's multi-level architecture for financial services highlights the compliance and operational challenges that led to creating Monoskope.

#2about 5 minutes

Introducing Monoskope's goals and core features

Monoskope aims to enable compliant DevOps workflows through features like permission management, tenant isolation, a four-eyes approval principle, and developer self-service.

#3about 3 minutes

Integrating Monoskope with OIDC and Kubernetes

Monoskope is built with Go and RabbitMQ, supports any OIDC provider for user login, and can act as an OIDC provider itself to manage Kubernetes cluster access.

#4about 5 minutes

How event sourcing provides a complete audit trail

Event sourcing is the core architectural pattern where the system's state is derived from an append-only log of events, ensuring data is never lost and enabling time travel.

#5about 5 minutes

A detailed walkthrough of the Monoskope architecture

The system uses microservices for command handlers, query handlers, and an event store, with reactors that subscribe to a message bus to perform actions.

#6about 3 minutes

Current project status and future development roadmap

The project is open source with core user, role, and cluster management implemented, with plans for SCIM 2 support, a web UI, and expanded self-service features.

#7about 5 minutes