Web-based remote monitoring & management that integrates with OpenFrame — remote desktop, terminal access, file transfer, and device control across Windows, macOS, and Linux.
- Remote desktop, terminal, and file management via web interface
- Cross-platform agent support (Windows, macOS, Linux)
- Intel AMT support for out-of-band management
- WebRTC-based peer-to-peer connectivity
- Multi-user collaboration and session sharing
- Device grouping and access control policies
- Extensible with plugins and automation scripts
- Integrations: OpenFrame Gateway, Stream (Kafka), Analytics (Pinot), Auth (OIDC/JWT)
- API-first (REST/WebSocket), web console (operator UI)
For OpenFrame Integration:
- Kubernetes cluster with kubectl
- Telepresence (for local access to services)
MeshCentral is integrated into OpenFrame for remote device access and management.
MeshCentral runs as a service in OpenFrame and connects to endpoint agents via Gateway. Session events flow into Stream and Analytics for monitoring and audit.
flowchart LR
A[Agent] <--commands/sessions--> G[OpenFrame Gateway]
subgraph OpenFrame
G --> API[(MeshCentral Service API)]
API --> DB[(DB: devices, users, sessions)]
DB --> S[Stream]
S --> K[(Kafka)]
K --> C[(Cassandra)]
K --> P[(Pinot Analytics)]
end
style A fill:#FFC109,stroke:#1A1A1A,color:#FAFAFA
style G fill:#666666,stroke:#1A1A1A,color:#FAFAFA
style API fill:#212121,stroke:#1A1A1A,color:#FAFAFA
MeshCentral is deployed automatically as part of OpenFrame via ArgoCD app-of-apps pattern:
# manifests/apps/values.yaml
apps:
meshcentral:
enabled: true
project: integrated-tools
namespace: integrated-tools
syncWave: "3" # Deployed after microservicesAccess MeshCentral UI:
# Connect to integrated-tools namespace
telepresence connect --namespace integrated-tools
# MeshCentral UI will be available at:
# https://meshcentral.integrated-tools.svc.cluster.local:8383For standalone MeshCentral deployment (not recommended - registration job will fail):
helm install meshcentral ./manifests/integrated-tools/meshcentralAuto-initialization:
- Creates default admin user
- Sets up device groups and policies
- Generates API keys for integration
- Persists credentials at
/opt/meshcentral/data/credentials.json - Registers as integrated tool in OpenFrame
Configuration is managed via Helm chart at manifests/integrated-tools/meshcentral/.
Check deployment status:
kubectl get pods -n integrated-tools -l app=meshcentral
kubectl logs -f meshcentral-0 -n integrated-toolsAccess MeshCentral services via Telepresence:
# Connect to cluster
telepresence connect --namespace integrated-tools
# Access MeshCentral UI directly
open https://meshcentral.integrated-tools.svc.cluster.local:8383
# Access MongoDB for debugging
mongo meshcentral-mongodb.integrated-tools.svc.cluster.local/meshcentralGet API credentials manually:
kubectl exec -it meshcentral-0 -n integrated-tools -- \
cat /opt/meshcentral/data/credentials.jsonFor complete documentation:
- TLS 1.2 enforced for all communication
- JWT authentication via OpenFrame Gateway
- Role-based access control (RBAC) for users and devices
- Database encryption for secrets
- Support for enrollment secrets or pre-shared keys
Found a vulnerability? Email security@flamingo.run instead of opening a public issue.
We welcome PRs! Please follow these guidelines:
- Use branching strategy:
feature/...,bugfix/... - Add descriptions to the CHANGELOG
- Follow consistent Go code style (
go fmt, linters) - Keep documentation updated in
docs/
This project is licensed under the Flamingo Unified License v1.0 (LICENSE.md).
| Built with 💛 by the Flamingo team | Website • Knowledge Base • LinkedIn • Community |