Why Fig?
Every service needs configuration: API URLs, timeouts, credentials, logging levels. Those values change by environment, and they need to stay consistent across many microservices.
Architecture
Fig is a centralized settings-management system for .NET services. Operators manage values in Fig Web; applications consume them through the ASP.NET configuration system (IOptions / IOptionsMonitor).
Comparison To Alternatives
Modern dotnet applications might be configured to draw from a range of different configuration providers. This provides a lot of flexibility but can also be confusing for those configuring the application. Fig is also a configuration provider and as such, can work along side other configuration sources. However, fig is more than just a configuration provider. It is a complete solution for managing settings across multiple micro-services. This is because when an application starts up, it registers its configuration with Fig meaning those settings are now viewable and editable from within the Fig web application.
Videos
The walkthrough below was recorded for Fig 2.0. The product has moved on (Aspire, MCP, Dashboards, Reports, Fig Assistant, Keycloak, and more), so treat it as a historical overview rather than a setup guide.