# dotnetcore/AgileConfig

基于.NET Core开发的轻量级分布式配置中心 / .NET  Core lightweight configuration server

Repository: https://github.com/dotnetcore/AgileConfig
Canonical: https://ross.abutalabs.com/products/agileconfig
Language: C#
License: MIT
License Family: permissive
Topics: agileconfig, websocket, dotnet-core, configuration-server, configuration-management, configuration-center, configuration, microservice
Last push: 2026-08-26T15:19:38+00:00

## Health v2 (maintenance only)
Score: 99/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 98, longevity 100
- inputs: {"age_days": 2766, "days_push": 7, "days_rel": 15, "gap_med": 20, "n_releases_24m": 22}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1620, forks 322 (observed 2026-08-28T04:05:12.279343+00:00)

## What it is
AgileConfig is a lightweight distributed configuration center built on .NET Core, deployable via Docker or IIS, with a management UI and clients for many languages. It pushes configuration changes to clients in real time and can double as a simple service registry.

## Use cases
- manage microservice configs from a central server
- push config changes to services in real time without restarts
- self-host an alternative to Apollo or Spring Cloud Config for .NET apps
- roll back configuration versions after a bad deploy
- manage configs across dev, test, and production environments
- register and discover services with a lightweight registry
- control who can edit configs with role-based permissions

## When to choose
- you run .NET Core microservices and want IConfiguration/IOptions integration out of the box
- you need a simple, easy-to-deploy config center instead of heavyweight options like Apollo or Nacos
- you want multi-language clients (Java, Go, Python, Node, Rust) for a polyglot stack
- you need real-time config updates, versioning, and rollback with minimal setup

## When to avoid
- you only need static appsettings. files with no dynamic updates
- you require a full-featured platform with built-in service governance,熔断, or metrics beyond OpenTelemetry export
- your stack has no client for your language and you cannot use the REST API
- you need Kubernetes-native config (ConfigMaps/Operators) rather than a standalone server

## Facets
- artifact type: service
- maturity: active
- function: configuration-management, http-server, websocket, webhook, auth, monitoring
- domain: microservices, backend, self-hosted, developer-tools
- platform: dotnet, self-hosted, cross-platform
- tags: configuration-center, distributed-config, service-registry, sso, opentelemetry, ioptions, devops, docker, web-server

## Member repositories
- dotnetcore/AgileConfig (main) score 99

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:12.279343+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-30T03:49:18.315102+00:00, confidence not recorded.
  - readme: https://github.com/dotnetcore/AgileConfig (fetched 2026-08-28T04:05:12.279343+00:00, sha ea15f62e4c1b)
- Data as of 2026-08-30T08:39:29.467469+00:00.