Team Server
Team Server
Team Server is Endura’s management plane. It receives Sensor telemetry, distributes policies, discovers CI/CD pipelines, records violations, and controls user access.
Capabilities
| Area | What Team Server provides |
|---|---|
| Sensors | Enrollment, status, logs, and policy distribution |
| Pipelines | Bamboo, GitHub, GitLab, Jenkins, and TeamCity discovery |
| Deployments | Runtime workload and violation visibility |
| Policies | Editing, assignment, ownership, history, and proposals |
| Notifications | Scoped Slack alerts for policy violations |
| Access | OIDC authentication, roles, resource scope, and personal access tokens |
Access Control
New users receive the Viewer role. An Administrator can promote users and grant resource access.
| Role | Summary |
|---|---|
| Administrator | Full system access, including users and roles |
| Operator | Manage authorized resources, integrations, and policies |
| Viewer | Read authorized resources and manage personal access tokens |
See Access Control for role permissions, resource scope, and policy ownership.
Deployment Options
| Option | Choose it when |
|---|---|
| Managed | Endura should operate the service and database |
| Docker | You want a self-hosted container deployment on Docker |
| Podman | You prefer Podman or rootless container management |
| Kubernetes | You operate Team Server on an existing cluster |
Compare operational requirements in Deployment.
Self-Hosted Requirements
A self-hosted Team Server needs:
- PostgreSQL and credentials that can run migrations and read and write application data
- At least 2 GB of memory for the Team Server container
- A public URL for browser, Sensor, OIDC callback, and notification links
- HTTPS for production access
- One configured authentication provider