# apolloconfig/apollo

Apollo is a reliable configuration management system suitable for microservice configuration management scenarios.

Repository: https://github.com/apolloconfig/apollo
Canonical: https://ross.abutalabs.com/products/apollo
Homepage: https://www.apolloconfig.com
Language: Java
License: Apache-2.0
License Family: permissive
Topics: configuration-management, spring-boot, config-management, microservices, spring-cloud, distributed-configuration
Last push: 2026-08-22T05:44:08+00:00

## Health v2 (maintenance only)
Score: 88/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 68, longevity 100
- inputs: {"age_days": 3834, "days_push": 11, "days_rel": 52, "gap_med": 119, "n_releases_24m": 4}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 29803, forks 10164 (observed 2026-08-28T04:11:53.677133+00:00)

## What it is
Apollo is a reliable, centralized configuration management system for microservices, built on Spring Boot and Spring Cloud. It provides a web portal and server for managing configurations across environments and clusters, with SDKs for Java and .NET that support real-time (hot) configuration updates.

## Use cases
- centrally manage microservice configurations across environments and clusters
- push configuration changes to running services in real time without restarts
- share common configuration across multiple applications via namespaces
- roll back bad configuration releases and track change history
- give different clusters of the same app different configuration values
- self-host a configuration center for Spring Boot / Spring Cloud apps

## When to choose
- you run many microservices and need centralized, versioned configuration management
- you need hot-reload of configuration without redeploying services
- you use Spring Boot/Spring Cloud and want first-class Java SDK integration
- you need environment/cluster/namespace separation with permissions, audits, and rollback

## When to avoid
- you only need simple per-service config files or a lightweight key-value store
- your stack is not Java or .NET and lacks an official SDK
- you already standardize on a platform like Kubernetes ConfigMaps or a cloud config service
- you cannot operate the additional server-side infrastructure (portal, config service, database)

## Facets
- artifact type: service
- maturity: stable
- function: configuration-management, microservices, self-hosted, developer-tools
- domain: microservices, backend, self-hosted
- platform: jvm, self-hosted, cross-platform
- tags: config-center, spring-cloud, hot-reload, config-server, java-client, dotnet-client, devops, spring-boot, docker

## Member repositories
- apolloconfig/apollo (main) score 88

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:11:53.677133+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T16:52:52.988989+00:00, confidence not recorded.
  - readme: https://github.com/apolloconfig/apollo (fetched 2026-08-28T04:11:53.677133+00:00, sha 8e3c5fc87702)
  - homepage: https://www.apolloconfig.com (fetched 2026-08-29T07:49:54.654992+00:00, sha f118bdd5429e)
- Data as of 2026-08-30T08:39:29.467469+00:00.