SSL Teams
SSL Teams gives engineering and platform teams one controlled way to run development PKI without spreading CA private keys across laptops, scripts, and ad hoc tooling. It combines a Quarkus service, a browser dashboard, and the sslteam CLI to manage CA lifecycle, leaf issuance, trust distribution, and audit history from a single system of record.
For teams searching for HTTPS certificate management in development and private infrastructure, SSL Teams provides a policy-driven control plane for internal TLS identity, trust, and lifecycle operations.
SSL Teams in one line
At a glance
One control plane for development PKI: trust bootstrap, certificate issuance, lifecycle control, and full audit evidence.
SSL Teams is the control plane for internal HTTPS identity: create trust, issue certificates, enforce policy, and prove who did what.
Use this page for
- Product orientation, value, and common use cases.
- Fast navigation to deployment, operator, and integration documentation.
- Deciding which workflow document to open next.
If you need architecture and trust model details, use Product overview. If you need browser-first operational steps, use the Operator Guide. If you need CLI-first production operations, use the DevOps playbook.
Where SSL Teams helps most
Use cases that deliver immediate value:
- Standardize team TLS: run one approved issuance workflow across local and private environments.
- Replace fragile scripts: move from ad hoc certificate scripts to policy-backed DNS and IP SAN issuance.
- Protect CA custody: keep key-sensitive actions explicit, authorized, and auditable on the server.
- Support fast ephemeral environments: issue and retire short-lived certificates without manual PKI handling.
- Give security and DevOps shared visibility: track issuance, download, activation, retirement, and revocation in one history.
- Enable safe self-service automation: let teams use the CLI and API without distributing CA private keys.
Why teams choose SSL Teams
Three reasons teams adopt it quickly
Teams that treat internal TLS as an afterthought eventually pay for it in delays, risk, and audit friction. High-performing teams do not leave certificate lifecycle to tribal knowledge; they run it as an operational capability.
Professional teams operationalize certificate lifecycle early so trust, issuance, and revocation stay fast, consistent, and provable.
- Move faster with less friction: issue trusted certificates without manual bottlenecks.
- Operate with stronger control: keep CA-sensitive actions authorized, explicit, and auditable.
- Run with shared confidence: give engineering, platform, and security one traceable system of record.
Start here
- Deploy SSL Teams with Docker.
- Follow the Operator Guide for the browser-based administration and certificate lifecycle workflow.
- Follow the DevOps playbook for the complete operator workflow.
- Read Certificates and trust before installing a Root certificate or issuing a leaf.
- Use the CLI quick reference for daily work, or the CLI command reference for every option.
- Use the API reference when connecting HTTP or Java integrations.
Keep the certificate layers separate
The startup TLS certificate protects the HTTPS connection to SSL Teams. The application Root and Intermediate issue development leaf certificates. Trusting one layer does not automatically trust or authorize another.
What SSL Teams provides
- A browser dashboard for authentication, CA setup, certificate inventory, issuance, downloads, and revocation.
- An HTTPS Quarkus service with PostgreSQL persistence, authorization, audit records, health checks, and OpenAPI.
- A standalone
sslteamCLI for explicit TLS enrollment, authentication, CA operations, leaf issuance, trust-store management, and selected offline Root-signing workflows. - Typed Java contracts and a framework-neutral Java client for integrations.
The normal operator journey
- Deploy the service with protected PostgreSQL and JWT configuration.
- Establish transport trust for the service origin.
- Authenticate with the dashboard-approved device flow or a protected password file.
- Complete application Root and Intermediate setup.
- Issue a leaf certificate for explicitly validated DNS names or IP addresses.
- Distribute public certificate material and retain private artifacts securely.
- Rotate, retire, or revoke certificates through the service when lifecycle state changes.