A cluster you can actually see.
This is a visual overview of the infrastructure behind NemesisCluster - a real Kubernetes environment built for testing, experimentation, and running selected open-source services.
From request to response.
Every request passes through multiple infrastructure layers - from networking and orchestration to storage and monitoring - working together as part of the test environment.
Orchestration
Kubernetes
A real Kubernetes cluster runs and manages the workloads behind NemesisCluster, handling scheduling, deployments, and automated recovery during infrastructure testing.
- Nodes
- 6
- Namespaces
- 12
- Auto-healing
- Enabled
Isolation & portability
Containers
Services run as containerized workloads using open-source images and reproducible deployments, making testing, updates, and maintenance easier.
- Running pods
- 60+
- Images
- Open-source focused
- Rollouts
- Automated
Persistent & resilient
Storage
Persistent storage provides data continuity for running services. Backups and snapshots are used where applicable, but this remains a test environment without data retention guarantees.
- Redundancy
- 3x replicated
- Snapshots
- Scheduled
- Storage type
- Persistent volumes
Connected & controlled
Networking
Ingress, routing, TLS, and network controls connect services while keeping the underlying infrastructure isolated and manageable.
- TLS
- Enabled
- Ingress
- Load balanced
- Network policies
- Enabled
Visibility & improvement
Monitoring
Monitoring helps track service health, performance, and infrastructure issues. Operational data is used to troubleshoot and improve the platform.
- Checks / min
- 120+
- Dashboard
- Available
- Alerting
- Automated
This is a public test cluster.
NemesisCluster provides public access to services running on our test infrastructure so the community can use them while we evaluate, develop, and improve the platform. This environment is experimental: availability, uptime, performance, and data persistence are not guaranteed. Services may be modified, restarted, or removed at any time without notice. We assume no responsibility for data loss, downtime, or any issues resulting from the use of this test cluster.