The section your link pointed to isn't on spire's page any more, so we've brought you to the top.
SPIRE is a production-ready implementation of the SPIFFESPIFFEAn open standard, maintained by the CNCF, for assigning cryptographic identities to workloads in dynamic infrastructure so services can authenticate each other without passwords or static credentials. APIs that performs node and workload attestation to securely issue and verify SVIDs.
spire is an open-source system for issuing and rotating cryptographic identities to workloads, implementing the SPIFFE standard so services can authenticate each other without shared secrets or long-lived credentials. It runs as a server and agent pair deployed on the infrastructure it protects, typically alongside Kubernetes clusters or on VMs, with node and workload attestor plugins covering AWS, Azure, GCP, Docker, and Windows environments. It is aimed at platform and infrastructure security teams building service-to-service authentication rather than at end-user-facing identity work, and it fits the workload identityworkload identityAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials. and mTLSmTLSMutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with.-bootstrapping niche within identity-access infrastructure, alongside plugins for HashiCorp Vault and cloud KMSKMSA managed service that creates, stores, rotates and controls access to encryption keys, usually backed by HSMs. Applications ask it to encrypt or decrypt rather than holding keys themselves. services for key storage. First committed in 2017, it now has 303 contributors and 666 commits in the past year, with its most recent release 43 days ago, indicating active, ongoing maintenance.
SPIRE is a production-ready implementation of the SPIFFE APIs that performs node and workload attestation to securely issue and verify SVIDs.
Which of my services can prove their identity to each other without me managing shared secrets or API keys?
issues short-lived X.509 or JWT credentials to each workload following the SPIFFE standard, verified through mutual TLS rather than a stored secret
How do I know a workload calling my service is the one I think it is, and not something an attacker planted on the node?
node and workload attestor plugins check platform-level facts (AWS, Azure, GCP, Docker, Windows properties) before issuing a credential, so identity is tied to verified infrastructure attributes rather than a token the caller simply presents
What happens to a service's credentials if the node or container it runs on is compromised or torn down?
credentials are short-lived and rotated automatically, and attested nodes are pruned from the datastore, so a stolen certificate stops being useful once it expires and the node's registration is removed
Can I restrict which AWS account or specific nodes are allowed to attest as a given identity?
the account ID selector on the AWS node attestor scopes attestation to named accounts, and an optional node selector lets individual nodes be aliased or restricted, narrowing who can claim a given SPIFFE ID
Is my metrics or telemetry traffic exposed to anyone who can reach the scrape endpoint?
the metrics endpoint can require a SPIRE-issued certificate over TLS with an allowlist of permitted SPIFFE IDs, so only authenticated collectors can pull metrics
Which of my running agents haven't been upgraded to the version I expect?
the server records each agent's version through its status API, visible in agent listing commands, so mismatched agent versions across a fleet show up directly
34 capabilities
across 7 areas
· 3 backed by code, an API document or a real run
Built from spire's releases, docs, README and our own runs.
“Seen” marks the month we first spotted a release the vendor didn't date.
Group names and tags are our labels.
+Workload Identity Issuance2 capabilitiesSPIRE's core function is issuing cryptographic identities to workloads in the form of X.509 and JWT SVIDs. These identities are the foundation of zero-trust authentication between services.▸
+Workload identity issuance (X.509-SVID and JWT-SVID)verifiedIssues X.509 and JWT identity documents to workloads, with controls over signing, key type, and token claims.29 releases · 11 other sources · first seen Jan 2019▸
release
29 total
Adds configurable JTI claim inclusion in JWT-SVIDs at the entry level.
v1.15.2 · Jul 2026
· source
· release history
JWT-SVID profile on spire-server can now be disabled via the disable_jwt_svids config option.
v1.14.0 · Dec 2025
· source
· release history
SPIRE Agent LRU identity cache is now always enabled, with size controllable via x509_svid_cache_max_size.
v1.11.0 · Oct 2024
· source
· release history
Adds forced rotation and revocation support for SVIDs.
v1.11.0 · Oct 2024
· source
· release history
The SPIRE Agent LRU identity cache is now unconditionally enabled; any configuration that previously disabled it will no longer have that effect.
v1.11.0 · Oct 2024
· source
· release history
X509-SVIDs minted by SPIRE can now include wildcards in the DNS names
v1.9.0 · Feb 2024
· source
· release history
docs
SPIFFE Runtime Environment toolchain that establishes trust between software systems by attesting workloads and issuing SPIFFE IDs and SVIDs.
command line
--jwtSVIDIncludeJTI — A boolean value that, when set, includes a unique 'jti' claim in JWT-SVIDs issued for this entry and bypasses the agent JWT-SVID cache
v1.15.2 · Jul 2026
· command-line history
--disableX509SVIDPrefetch — A boolean value that, when set, disables prefetching X509 SVID for this entry
v1.15.0 · May 2026
· command-line history
--signingAlgorithm — Signing algorithm for the workload signing key
v1.14.3 · Mar 2026
· command-line history
Disable JWT-SVID issuance on a server that only needs X.509 SVIDs, reducing attack surface.$ server { disable_jwt_svids = true }
v1.14.0 · Dec 2025
· source
Control the size of the now-always-on SPIRE Agent LRU identity cache to tune memory usage for your workload density.$ # In the SPIRE Agent config file agent { x509_svid_cache_max_size = 1000 }
v1.11.0 · Oct 2024
· source
Configure SPIRE to issue X509-SVIDs with wildcard DNS names for broader service discovery.$ # Set the allow_wildcards_in_dns_names flag to true in your agent configuration entry { dns_name: "*.example.com" } # Ensure server config allows wildcards if supported by version
v1.9.0 · Feb 2024
· source
Create an SPIFFE entry with a specific JWT token lifetime distinct from the X.509 certificate lifetime.$ spire-server entry create -parentID spiffe://example.org/ns/workload/sa/agent -spiffeID spiffe://example.org/app -jwtSVIDTTL 1h -x509SVIDTTL 24h
v1.5.0 · Nov 2022
· source
Update an existing entry to set the JWT token TTL using the new API field directly.$ curl -X PATCH http://localhost:8081/v1/entry/entry-id-123 -d '{"jwt_svid_ttl": "3600s", "x509_ttl": "86400s"}'
v1.5.0 · Nov 2022
· source
Authenticate remote workloads by creating registration entries via the secured API$ curl -X POST https://spire-server:8443/v1/agent/svid/register -H 'Authorization: Bearer <token>' -d '{"entry": {}}'
0.7.2 · Jan 2019
· source
+SPIFFE BrokershippedProvides a brokering endpoint that facilitates SPIFFE identity federation across trust domains.6 releases · 1 other source · first seen Apr 2018▸
Also counts toward: REST API
release
The Broker API endpoint is now included in health checks when enabled.
v1.15.3 · Aug 2026
· source
· release history
Introduces the SPIFFE Broker endpoint and API.
v1.15.2 · Jul 2026
· source
· release history
SPIRE Server bundle endpoint now includes the bundle_sequence_number field to track trust anchor rotation
v1.7.2 · Aug 2023
· source
· release history
Entry API and spire-server entry create, spire-server entry show, spire-server entry update CLI commands now accept hint information.
v1.6.3 · Apr 2023
· source
· release history
Added experimental_federation support for SPIFFE federation
0.8.1 · Jul 2019
· source
· release history
example
Export the SPIRE server's CA bundle for manual federation with external trust domains.$ spire-server print-bundle > spiffe-ca-bundle.pem
0.5 · Apr 2018
· source
+Node and Workload Attestation1 capabilitySPIRE verifies the identity of nodes and the workloads running on them before any identity is issued. Pluggable attestors allow this verification to work across different platforms and environments.▸
+Node attestationshippedVerifies the identity of nodes using pluggable attestors, with platform-specific controls for AWS, Windows, and certificate-based attestation.21 releases · first seen Jun 2018▸
release
21 total
Adds disable_group_name_selectors option for the Windows workload attestor.
v1.15.2 · Jul 2026
· source
· release history
Adds optional verification of client certificate IPs in the x509pop node attestor.
v1.15.2 · Jul 2026
· source
· release history
Adds attestation support for Envoy proxy workloads when Istio is configured with holdApplicationUntilProxyStarts: true
v1.4.4 · Oct 2022
· source
· release history
Adds windows workload attestation support on Kubernetes to allow workloads running on Windows nodes to be attested via the Kubelet secure port
v1.4.0 · Aug 2022
· source
· release history
Supports anonymous authentication to the Kubelet secure port for workload attestation on Kubernetes via a new flag/option in the node attestor
v1.4.0 · Aug 2022
· source
· release history
Adds kubernetes workload attestation support when the Kubelet is run as a standalone component
v1.3.2 · Jul 2022
· source
· release history
+Cryptography and Key Management2 capabilitiesSPIRE manages the signing keys used to mint SVIDs and supports modern and post-quantum cryptographic algorithms. External key management systems such as AWS KMS can be used to protect those keys.▸
+Post-quantum cryptography (PQC) supportshippedApplies post-quantum cryptography policies to SPIRE endpoints and supports additional PQC curves for future-proof identity signing.5 releases · first seen Mar 2026▸
release
Post-quantum cryptography policy is now applied to the bundle endpoint and Prometheus server.
v1.15.2 · Jul 2026
· source
· release history
Adds support for two additional post-quantum cryptography (PQC) curves.
v1.15.2 · Jul 2026
· source
· release history
Supports two additional post-quantum cryptography (PQC) curves.
v1.15.2 · Jul 2026
· source
· release history
The RequirePQKEM TLS policy now uses the standardized X25519MLKEM768 algorithm instead of the draft x25519Kyber768Draft00.
v1.14.3 · Mar 2026
· source
· release history
The RequirePQKEM TLS policy switches from x25519Kyber768Draft00 to X25519MLKEM768; any peer or configuration that negotiated the draft KEM will no longer be compatible.
v1.14.3 · Mar 2026
· source
· release history
+AWS KMS key managementshippedStores and retrieves signing keys in AWS KMS, including discovery of existing keys via resource tags.3 releases · first seen Nov 2018▸
Also counts toward: Plugin API support, Plugin system
release
Adds tag-based key discovery support in the aws_kms Key Manager plugin.
v1.15.2 · Jul 2026
· source
· release history
New HashiCorp Vault Key Manager plugin for storing SPIRE signing keys in Vault.
v1.15.0 · May 2026
· source
· release history
KeyManager plugin interface (server.keymanager.*) allowing custom key storage backends
0.7.0 · Nov 2018
· source
· release history
+Agent Deployment and Configuration2 capabilitiesSPIRE agents run on each host and must be configurable for diverse deployment topologies. These capabilities control how agents are identified, how their interfaces are exposed, and how access to those interfaces is throttled.▸
+Agent socket and instance configurationverifiedAllows multiple agent instances to run on the same host by substituting an instance name into socket path templates.38 releases · 5 other sources · first seen Feb 2018▸
Also counts toward: Command-line interface
release
38 total
Adds opt-in enable_namespace_labels option in the k8s workload attestor, producing ns-label selectors from namespace labels
v1.15.3 · Aug 2026
· source
· release history
Adds disable_kubelet_client option for the k8s workload attestor
v1.15.3 · Aug 2026
· source
· release history
Adds opt-in enable_namespace_labels option in the k8s workload attestor, producing ns-label selectors from namespace labels.
v1.15.3 · Aug 2026
· source
· release history
Adds disable_kubelet_client option for the k8s workload attestor.
v1.15.3 · Aug 2026
· source
· release history
Adds trust_bundle_spiffe_workload_api agent configuration option to fetch the initial trust bundle from a Workload API endpoint, simplifying nested agent deployments.
v1.15.3 · Aug 2026
· source
· release history
Adds slurm workload attestor for cluster integration
v1.15.3 · Aug 2026
· source
· release history
command line
--instance — Instance name to substitute into socket templates (env SPIRE_AGENT_PUBLIC_SOCKET_TEMPLATE).
v1.15.0 · May 2026
· command-line history
example
Enable namespace label selectors in the Kubernetes workload attestor to write SPIFFE policies based on namespace-level labels.$ enable_namespace_labels = true
v1.15.3 · Aug 2026
· source
Suppress Windows group-name selectors from the workload attestor when group names are not needed, reducing selector noise.$ # In spire-agent.conf NodeAttestor "windows" { plugin_data { disable_group_name_selectors = true } }
v1.15.2 · Jul 2026
· source
Access the Agent's Admin API via its new default location instead of specifying a custom socket path.$ # Use the new default Unix domain socket for Admin API calls sudo curl --unix-socket /run/spire/server/api.sock https://localhost/v1/agent/health
v1.9.0 · Feb 2024
· source
Inspect existing registration entries via the new unified CLI interface$ spire-server register list
0.4 · Feb 2018
· source
+Workload API and Envoy SDS rate limitingverifiedLimits the rate at which individual callers can use the Workload API and Envoy SDS interfaces on an agent.11 releases · 4 other sources · first seen May 2023▸
Also counts toward: Plugin API support, Plugin system, S3 export
release
11 total
Adds disable_workload_api and disable_sds_api agent options to disable the Workload API and SDS APIs on the public endpoint.
v1.15.3 · Aug 2026
· source
· release history
Adds disable_workload_api and disable_sds_api agent options to disable the Workload API and SDS APIs on the public endpoint
v1.15.3 · Aug 2026
· source
· release history
Adds experimental per-caller rate limiting for the agent Workload API and Envoy SDS.
v1.15.2 · Jul 2026
· source
· release history
Introduces experimental per-caller rate limiting for the agent Workload API and Envoy SDS.
v1.15.2 · Jul 2026
· source
· release history
PROXY protocol support added for correct rate limiting when SPIRE sits behind load balancers.
v1.15.0 · May 2026
· source
· release history
New account_id selector for the aws_iid node attestor enables scoping attestation to specific AWS accounts.
v1.15.0 · May 2026
· source
· release history
command line
--disableSDSAPI — Disable the Envoy SDS API
v1.15.3 · Aug 2026
· command-line history
--disableWorkloadAPI — Disable the SPIFFE Workload API
v1.15.3 · Aug 2026
· command-line history
example
Disable the Workload API and SDS API on a public-facing agent endpoint to reduce attack surface in environments where those APIs are not needed.$ disable_workload_api = true disable_sds_api = true
v1.15.3 · Aug 2026
· source
Restrict node attestation to a specific AWS account ID using the new account_id selector.$ spire-server entry create \ -spiffeID spiffe://example.org/workload \ -selector aws_iid:account_id:123456789012 \ -parentID spiffe://example.org/agent
v1.15.0 · May 2026
· source
+Observability and Monitoring2 capabilitiesSPIRE exposes metrics and structured logs so operators can monitor the health and behaviour of their deployments. These capabilities cover both the metrics endpoint and the agent-side logging controls.▸
+Agent logging and observabilityshippedProvides configurable logging for the agent, including the option to record workload selectors and clearly marked deprecation warnings.11 releases · 2 other sources · first seen Dec 2019▸
release
11 total
Adds debug getinfo subcommand in the spire-server and spire-agent CLIs to access the Debug APIs.
v1.15.3 · Aug 2026
· source
· release history
Introduces a Logger service for spire-agent.
v1.15.2 · Jul 2026
· source
· release history
Adds log_selectors configuration item for the agent.
v1.15.2 · Jul 2026
· source
· release history
Deprecation warnings now use dedicated log markers for easier detection.
v1.15.2 · Jul 2026
· source
· release history
Selectors are no longer logged at the agent level, preventing potential leakage of sensitive information.
v1.14.3 · Mar 2026
· source
· release history
example
Inspect live agent state via the Debug API without needing to query the gRPC endpoint directly.$ spire-agent debug getinfo
v1.15.3 · Aug 2026
· source
Rotate SPIRE log files without restarting the process by sending a signal to the PID$ kill -SIGUSR2 <spire-server-pid>
v1.2.2 · Apr 2022
· source
+Prometheus metrics endpointshippedExposes a Prometheus metrics endpoint that can be secured with a SPIRE-issued certificate and restricted to specific SPIFFE IDs.8 releases · first seen Dec 2018▸
release
8 total
Adds TLS support for the Prometheus metrics endpoint using a SPIRE SVID, with an optional SPIFFE ID allowlist.
v1.15.2 · Jul 2026
· source
· release history
A metric label is renamed from bootstraped to bootstrapped; any dashboards or alerts keyed on the old label name will stop matching.
v1.15.0 · May 2026
· source
· release history
TLS support added to the Prometheus metrics sink for encrypted metric scraping.
v1.15.0 · May 2026
· source
· release history
The uptime_in_ms gauge metric now reports float64 precision instead of integer.
v1.14.1 · Jan 2026
· source
· release history
Enables an optional trust_domain label on all metrics for finer-grained observability.
v1.11.2 · Feb 2025
· source
· release history
Adds new metrics configuration options to filter out specific metrics and labels
v1.0.2 · Sep 2021
· source
· release history
+Scalability and Database Performance1 capabilityIn large deployments the SPIRE server's database becomes a bottleneck. These capabilities reduce that load through query optimisation and configurable bulk-processing of stored records.▸
+Database performance and scalabilityshippedReduces database load in large deployments by optimising queries, fetching nodes in bulk, and making pruning batch sizes configurable.4 releases · first seen May 2019▸
release
Optimizes MySQL list entries query to reduce database CPU usage under load.
v1.15.2 · Jul 2026
· source
· release history
Attested nodes are now fetched in bulk, reducing database load in large deployments.
v1.15.2 · Jul 2026
· source
· release history
Adds configurable batch size for pruning attested nodes.
v1.15.2 · Jul 2026
· source
· release history
Adds MySQL support to the SQL DataStore plugin
0.8.0 · May 2019
· source
· release history
+Other24 capabilities▸
+Bundle publishing pluginsshippedAllows publishing SPIFFE trust bundles to external stores via pluggable BundlePublisher interfaces, such as AWS S3.11 releases · 1 other source · first seen May 2023▸
Also counts toward: Plugin API support, Plugin system, S3 export
release
11 total
Adds azure_blob BundlePublisher plugin to publish the trust bundle to Azure Blob Storage
v1.15.3 · Aug 2026
· source
· release history
New azure_blob BundlePublisher plugin for publishing the trust bundle to Azure Blob Storage.
v1.15.3 · Aug 2026
· source
· release history
The JSON output of the CLI no longer wraps objects in slices when printing; any tooling that parses CLI JSON output may break.
v1.15.0 · May 2026
· source
· release history
Adds spire-agent version reporting to spire-server via the PostStatus API, now visible in GetAgent/ListAgents CLI output.
v1.14.3 · Mar 2026
· source
· release history
Adds refresh hint support to aws_s3, gcp_cloudstorage, and k8s_configmap BundlePublisher plugins for published bundles.
v1.13.1 · Sep 2025
· source
· release history
New k8s_configmap BundlePublisher plugin lets SPIRE Server publish trust bundles directly to a Kubernetes ConfigMap.
v1.12.4 · Jul 2025
· source
· release history
example
Publish SPIFFE bundles to a self-hosted MinIO cluster instead of AWS S3 by pointing the aws_s3 BundlePublisher at a custom endpoint.$ BundlePublisher "aws_s3" { region = "us-east-1" bucket = "spire-bundles" object_key = "bundle.jwks" endpoint = "https://minio.internal:9000" force_path_style = true }
v1.12.0 · Mar 2025
· source
+OIDC discovery provider pluginshippedServes JWKS from trust domain signing keys via an OIDC discovery provider.9 releases · 1 other source · first seen Nov 2019▸
release
9 total
OIDC Discovery Provider can now read the trust bundle from a file, removing the dependency on a live SPIRE Server endpoint.
v1.12.4 · Jul 2025
· source
· release history
Adds support for specifying a server path prefix in the OIDC Discovery Provider.
v1.11.2 · Feb 2025
· source
· release history
Supports environment variable expansion in the OIDC Discovery Provider configuration.
v1.11.2 · Feb 2025
· source
· release history
Allows the JWKS URI returned in the OIDC Discovery Provider discovery document to be explicitly configured.
v1.11.2 · Feb 2025
· source
· release history
Enables a configurable JWT issuer (jwt_issuer) in the OIDC Discovery Provider, allowing operators to override the default issuer claim.
v1.11.1 · Dec 2024
· source
· release history
Adds optional health check endpoints to the OIDC Discovery Provider service
v1.3.2 · Jul 2022
· source
· release history
example
Override the JWT issuer in the OIDC Discovery Provider to match your organisation's public domain instead of the default.$ jwt_issuer = "https://oidc.example.com"
v1.11.1 · Dec 2024
· source
+Registration entry managementshippedManages registration entries including expiry, pruning, and auto-migration control.8 releases · 1 other source · first seen Jan 2019▸
Also counts toward: Command-line interface
release
8 total
Adds use_sync_authorized_entries experimental setting to enable the new SyncAuthorizedEntries RPC for incremental entry synchronization
v1.8.7 · Dec 2023
· source
· release history
Adds experimental events-based entry cache to reduce database overhead
v1.8.7 · Dec 2023
· source
· release history
Adds pagination support to the server entry show command
v1.3.2 · Jul 2022
· source
· release history
SPIRE Server CLI adds agents, entries, and bundlescount subcommands for listing quantities
v1.0.0 · Jul 2021
· source
· release history
Registration entries can be queried/filtered by federates_with in the entry API
v1.0.0 · Jul 2021
· source
· release history
Add disable_auto_migrate config key to disable SQL auto-migration
0.9.0 · Nov 2019
· source
· release history
example
Query the number of registered entries via the new count subcommand.$ spire-server entries count
v1.0.0 · Jul 2021
· source
+Kubernetes workload registrar enhancementsshippedSupports SPIFFE ID assignment based on Kubernetes annotations.7 releases · first seen Oct 2019▸
release
7 total
The webhook mode has been removed from the k8s-workload-registrar, requiring migration to an alternative registration method
v1.4.0 · Aug 2022
· source
· release history
Support for the configmap leader election lock type has been removed from the k8s-workload-registrar, requiring users to switch to a different leader election mechanism
v1.4.0 · Aug 2022
· source
· release history
leaderElectionresourceLockType in the K8s Workload Registrar configuration to change the Kubernetes resource lock mechanism used for leader election
v1.3.0 · May 2022
· source
· release history
K8s Workload Registrar CRD mode now supports registering downstream workloads
v1.2.2 · Apr 2022
· source
· release history
Adds identity template support for workload registration in k8s-workload-registrar
v1.0.2 · Sep 2021
· source
· release history
The registration_api config section in k8s-workload-registrar is removed; use server_api instead.
v0.12.0 · Dec 2020
· source
· release history
+Database plugin supportshippedAdds AWS Secret Manager and GCP CloudSQL as upstream CA plugins.6 releases · first seen May 2019▸
Also counts toward: gRPC API support
release
Adds multi-region support to the gcp_secretmanager SVIDStore plugin, letting operators specify which regions secrets are created in.
v1.11.2 · Feb 2025
· source
· release history
Adds configurable ca_pool setting to the GCP CAS UpstreamAuthority plugin to specify the CA pool location
v1.1.0 · Oct 2021
· source
· release history
Adds the gcp_cas UpstreamAuthority plugin using Google Cloud Platform's Certificate Authority Service
v0.12.2 · Apr 2021
· source
· release history
Introduces a new RPC FetchBundle in the Node API for fetching an up-to-date bundle
v0.10.0 · Apr 2020
· source
· release history
Added cloudsql_gcp upstream CA plugin for GCP CloudSQL support
0.8.1 · Jul 2019
· source
· release history
+Nested SPIRE federationshippedAllows server clusters to be chained together for federated identity.5 releases · 1 other source · first seen May 2019▸
Also counts toward: gRPC API support, Client SDKs
release
Adds azure_key_vault KeyManager plugin for key storage
v1.8.0 · Sep 2023
· source
· release history
spire-server federation CLI commands now accept the -output flag for structured output.
v1.5.4 · Jan 2023
· source
· release history
SPIFFE bundle endpoint URL is configurable within the federates_with config block
v1.0.0 · Jul 2021
· source
· release history
Introduces a new RPC FetchBundle in the Node API for fetching an up-to-date bundle
v0.10.0 · Apr 2020
· source
· release history
Introduces the v2 client library for Workload API interaction
0.8.0 · May 2019
· source
· release history
example
Export federation configuration in JSON format for automated ingestion by orchestration tools.$ spire-server federation show -output json
v1.5.4 · Jan 2023
· source
+Workload API v2 client libraryshippedIntroduces the v2 client library for Workload API interaction.5 releases · first seen May 2019▸
Also counts toward: Client SDKs
release
Adds incremental WIT-SVID support including building WIT-SVIDs in the svid.v1 API client and marshalling support for WIT-SVID keys
v1.15.3 · Aug 2026
· source
· release history
Adds WIT-SVID building support in the svid.v1 API client and marshalling support for WIT-SVID keys.
v1.15.3 · Aug 2026
· source
· release history
Supports marking registration entry X509-SVIDs as non-prefetchable to control caching behavior.
v1.15.0 · May 2026
· source
· release history
Agents can now fetch the X509-SVID for SPIFFE attestation mode directly from the Workload API socket.
v1.15.0 · May 2026
· source
· release history
Introduces the v2 client library for Workload API interaction
0.8.0 · May 2019
· source
· release history
+Workload selector enhancementsshippedAllows disabling executable hashing and configuring issuers for JWT-SVIDs.5 releases · first seen Nov 2019▸
release
iss claim support added for JWT-SVIDs (WIT-SVIDs).
v1.15.0 · May 2026
· source
· release history
AWS KMS key manager plugin now supports key tagging.
v1.14.0 · Dec 2025
· source
· release history
Adds the aws_kms server KeyManager plugin to use AWS Key Management Service
v0.12.2 · Apr 2021
· source
· release history
Add issuer claim configuration for JWT-SVIDs
0.9.0 · Nov 2019
· source
· release history
Add disable_hash option to workload selectors to skip executable hashing
0.9.0 · Nov 2019
· source
· release history
+Agent resilience and configurationshippedImproves agent reliability with automatic rebootstrap, file-based join token sources, and stricter validation of startup parameters.5 releases · first seen Sep 2022▸
release
oidc-discovery-provider now refuses to start when passed unrecognized arguments; previously unrecognized arguments were silently ignored, so any deployment passing extra flags will fail on upgrade.
v1.13.3 · Oct 2025
· source
· release history
oidc-discovery-provider now fails to initialize when started with unrecognized arguments, surfacing misconfigurations at startup.
v1.13.3 · Oct 2025
· source
· release history
New spire-agent configuration option sources join tokens from files, enabling integration with third-party credential providers.
v1.13.3 · Oct 2025
· source
· release history
Automatic agent rebootstrap support when the server CA goes invalid, improving resilience without manual intervention.
v1.13.0 · Aug 2025
· source
· release history
+Upstream Authority plugin interfaceshippedProvides a pluggable UpstreamAuthority plugin interface for X.509-SVID and JWT-SVID generation, allowing downstream servers to push keys upstream.5 releases · first seen Apr 2020▸
Also counts toward: gRPC API support, Plugin API support, Plugin system
release
New UpstreamAuthority.SubscribeToLocalBundle RPC enables streaming updates of the local trust bundle to upstream authority plugins.
v1.12.4 · Jul 2025
· source
· release history
gcp_kms KeyManager plugin is now available for encryption at rest
v1.5.3 · Dec 2022
· source
· release history
Adds vault as Upstream Authority built-in plugin
v0.10.1 · Jun 2020
· source
· release history
Introduces a new RPC PushJWTKeyUpstream in the Node API for publishing JWT-SVID signing keys from downstream servers
v0.10.0 · Apr 2020
· source
· release history
Introduces new plugin type UpstreamAuthority, which supports both X509-SVID and JWT-SVID as well as the ability to push upstream changes into SPIRE Server
v0.10.0 · Apr 2020
· source
· release history
+Agent re-attestation managementshippedEnables querying agent re-attestation status and purging stale agent records from the datastore.4 releases · 1 other source · first seen Apr 2023▸
Also counts toward: Command-line interface, REST API
release
Evicted agents that support reattestation can now reattest without being restarted.
v1.10.0 · Jun 2024
· source
· release history
Adds new agent purge subcommand for removing stale agent records from the datastore.
v1.6.4 · May 2023
· source
· release history
spire-server agent CLI commands now display whether agents can be re-attested.
v1.6.3 · Apr 2023
· source
· release history
Agent APIs support by_can_reattest filtering for querying agent re-attestation status.
v1.6.3 · Apr 2023
· source
· release history
example
Filter agents by re-attestation capability via the Agent API.$ curl -s http://localhost:8081/v1/agent/by_can_reattest/true
v1.6.3 · Apr 2023
· source
+Events-based entry cache improvementsshippedEnhances the experimental entry cache with batch fetching, read-only replica support, and full cache reload capabilities to improve database performance.4 releases · first seen Mar 2025▸
release
New server configuration to periodically purge expired agents, reducing stale entry accumulation.
v1.13.0 · Aug 2025
· source
· release history
Events-based cache now implements a full cache reload, completing its feature parity path.
v1.13.0 · Aug 2025
· source
· release history
Improves events-based cache performance via batch fetching of updated entries (experimental).
v1.12.1 · May 2025
· source
· release history
Experimental events-based cache now supports reading from read-only database replicas when data staleness is tolerated, improving read performance.
v1.12.0 · Mar 2025
· source
· release history
+SVID attribute customizationshippedProvides a CredentialComposer plugin interface to customize SVID and CA attributes during issuance.3 releases · 1 other source · first seen Feb 2023▸
Also counts toward: Plugin API support, Plugin system
release
Adds SPRIG library functions to the Go text/template engine available in SPIRE plugins, expanding templating power for plugin authors.
v1.11.1 · Dec 2024
· source
· release history
uniqueid CredentialComposer plugin that adds the x509UniqueIdentifier attribute to workload X509-SVIDs
v1.9.0 · Feb 2024
· source
· release history
Adds CredentialComposer plugin interface for customizing SVID and CA attributes
v1.6.0 · Feb 2023
· source
· release history
example
Inject the x509UniqueIdentifier attribute into issued workload X509-SVIDs using the new Composer plugin.$ # Add `uniqueid` to your SPIRE Agent's credential_composer section in server_entries.yaml # (or equivalent config file path for your deployment) credential_composer { plugins [ "uniqueid" ] }
v1.9.0 · Feb 2024
· source
+Authorization policy enhancementsshippedExpands the Rego authorization engine with V1 syntax support and caller path filtering capabilities.3 releases · first seen Mar 2025▸
release
OPA policy evaluation performance improved by approximately 2× through use of partial evaluation.
v1.14.3 · Mar 2026
· source
· release history
New capability to filter on caller path in spire-server Rego authorization policies.
v1.13.3 · Oct 2025
· source
· release history
Supports Rego V1 syntax in the authorization policy engine.
v1.12.0 · Mar 2025
· source
· release history
+Node attestation enhancementsshippedExtends node attestation capabilities with new selector types, platform-specific attestors, and cluster verification options.3 releases · first seen Mar 2025▸
release
New azure_imds node attestor plugin attests nodes running in Microsoft Azure using the Azure Instance Metadata Service (IMDS).
v1.14.0 · Dec 2025
· source
· release history
Enables aws_iid NodeAttestor to verify that attesting nodes belong to specified EKS clusters.
v1.13.1 · Sep 2025
· source
· release history
Adds SAN-based selectors in the x509pop NodeAttestor plugin for finer-grained node attestation.
v1.12.0 · Mar 2025
· source
· release history
+Plugin configuration validationshippedProvides the ability to validate plugin configurations before deploying changes to a live SPIRE server.2 releases · 1 other source · first seen Dec 2019▸
Also counts toward: Command-line interface
release
spire-server validate now supports validating plugin configuration.
v1.14.0 · Dec 2025
· source
· release history
Agent and server now detect unknown configuration options in supported blocks
0.9.1 · Dec 2019
· source
· release history
example
Validate plugin configuration before deploying changes to a live SPIRE server.$ spire-server validate -config /etc/spire/server.conf
v1.14.0 · Dec 2025
· source
+OIDC Discovery Provider flexibilityshippedEnhances the OIDC Discovery Provider with configuration overrides, trust bundle file sources, and stricter argument validation.3 releases · first seen Feb 2025▸
release
OIDC Discovery Provider can now read the trust bundle from a file, removing the dependency on a live SPIRE Server endpoint.
v1.12.4 · Jul 2025
· source
· release history
Adds support for specifying a server path prefix in the OIDC Discovery Provider.
v1.11.2 · Feb 2025
· source
· release history
Allows the JWKS URI returned in the OIDC Discovery Provider discovery document to be explicitly configured.
v1.11.2 · Feb 2025
· source
· release history
+Experimental entry cacheshippedReduces database overhead by using an events-based entry cache and incremental synchronization for registration entries.3 releases · first seen Dec 2023▸
release
Agents now use the SyncAuthorizedEntries API for periodic entry synchronization by default.
v1.12.0 · Mar 2025
· source
· release history
Adds use_sync_authorized_entries experimental setting to enable the new SyncAuthorizedEntries RPC for incremental entry synchronization
v1.8.7 · Dec 2023
· source
· release history
Adds experimental events-based entry cache to reduce database overhead
v1.8.7 · Dec 2023
· source
· release history
+ACME bundle distributionshippedAllows serving trust bundles via ACME protocol for Web PKI integration.3 releases · first seen Oct 2019▸
release
Adds Web-PKI authentication support to the bundle endpoint client
0.9.2 · Jan 2020
· source
· release history
Enables ACME v2 protocol support in the bundle endpoint configuration.
0.8.4 · Oct 2019
· source
· release history
spire_server.bundle.acme config section allows serving Web PKI bundles via ACME protocol
0.8.2 · Oct 2019
· source
· release history
+X.509 SVID customizationshippedAllows fine-grained control over X.509 SVID generation, including key type selection and SHA-256 SKI enforcement.2 releases · first seen Oct 2025▸
release
Adds support for the ec-p384 curve in the workload_x509_svid_key_type configuration option in spire-agent.
v1.14.0 · Dec 2025
· source
· release history
spire-server now uses SHA-256 for X.509-SVID Subject Key Identifiers when GODEBUG contains fips140=only.
v1.13.3 · Oct 2025
· source
· release history
+TLS listener policy configurationshippedAllows configuration of TLS policies that are applied to TLS listeners.1 release · first seen Oct 2026▸
release
Supports configuring TLS policies to be applied to TLS listeners.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
v1.15.4 · Oct 2026
· source
· release history
+Agent CLI observabilityshippedProvides CLI output for agent details and attested nodes.1 release · first seen Nov 2019▸
release
Add node_id and other details to agent CLI output for attested nodes
0.9.0 · Nov 2019
· source
· release history
+AWS Certificate Manager integrationshippedAdds an Upstream CA plugin for AWS Certificate Manager.1 release · first seen Nov 2019▸
release
Add Upstream CA plugin for AWS Certificate Manager integration
0.9.0 · Nov 2019
· source
· release history
+CA key persistenceshippedAllows the in-memory server CA plugin to persist signing keys to disk using configurable storage options.1 release · first seen Jul 2018▸
release
ServerCA memory plugin can now optionally persist keys to disk using persist_keys and key_store_path config options
0.6.1 · Jul 2018
· source
· release history
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
View
Source
No command matches.
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian time to a maintainer’s first reply
Nine scores for spire, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail spire puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
SPIFFE's home page and 5 more pages as they looked each month from September 2021 to October 2026: 19 renders, 1 change of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
Show
77 entries
No entries match these filters.
October 20261
August 20261
July 20261
May 20261
March 20261
January 20261
December 20251
October 20251
September 20251
August 20251
July 20251
May 20251
March 20251
February 20251
December 20241
October 20241
September 20241
August 20241
June 20241
May 20241
March 20241
February 20241
December 20231
November 20231
October 20231
September 20231
August 20231
July 20231
June 20231
May 20231
April 20231
February 20231
January 20231
December 20221
November 20221
October 20221
September 20221
August 20221
July 20221
June 20221
May 20221
April 20221
March 20221
January 20222
December 20211
November 20211
October 20211
September 20211
August 20211
July 20211
May 20211
April 20211
March 20212
December 20201
September 20201
August 20201
June 20201
April 20201
March 20201
January 20201
December 20191
November 20191
October 20192
July 20191
May 20191
February 20191
January 20191
December 20181
November 20181
September 20181
July 20181
June 20181
April 20181
February 20181
Project health
Issue, contributor and maintainer activity in spiffe/spire, 2023-10 – 2026-09,
as of 2026-09-25. Twelve-month figures first; the trend lines run
the whole window.
Contributors75+31 vs prior 12 months
Maintainers7+7 joined · −6 left, last 12 months
Bus factor2committers behind half the commits
Community-filed81%of issues opened, last 12 months
Median time to close90 daysfirst maintainer reply 3.6 days
Open backlog96of 1,769 issues ever filed
Issues opened / month4 · 0communitymaintainers
Open backlog96
Contributors / month10
Commits / month27
Stars2,536
Issue themes, last 12 months
other 100%
Counts from the project's public repository and git history; no individuals
are identified. Maintainers are the committers covering 80% of the last year's
commits. how we measure this
Articles
1 article
· updated Nov 4, 2026
Where spire turns up in what others publish: how-tos, attack reports that
name it, and incident write-ups. A row says why it is here and quotes where the
article names it; the link goes to the publisher.
Our research shows how an attacker with root can spoof the Linux control group (cgroup) information the SPIRE agent uses during workload attestation.
2 more quotes
When designing threat models for SPIFFE/SPIRE, organizations should assume that root-level access to a node grants access to all cryptographic identities scoped to it.
Note to readers: If you’re already familiar with SPIFFE/SPIRE concepts and architecture, you can jump directly to Workload Attestation and How the Agent Attests the Workload sections.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can
follow every release here.