Skip to content


It's not just about choosing the right tool. It's about how you use the tools you've chosen.

Stage 1: Build a great product. Own the user experience#

Figgy builds a cohesive framework around configuration & secret management by supporting various use cases and providing automation across multiple stages of the SDLC.

Figgy provides this cohesive experience by automating and connecting these parts of the daily user experience

  • Single sign on, session management
  • Local development libraries for a tight integration with daily developer workflow
  • Local development automation (Figgy CLI)
  • Remote config-store management & maintenance (Figgy Cloud).
  • Simple & efficient multi-account config management and visibility (Figgy UI)

On top of this Figgy layers:

  • Deep observability / tracking
  • Disaster recovery
  • Monitoring
  • Live events / change notifications

Stage 2: Establish a community#

At this time we are attempting to ramp up Stage 2 to establish a strong community to continually improve Figgy.

  • Expand library support across all major languages & frameworks (Go, Java, C#, etc.)
  • Expand support to more SSO providers (OneLogin, JumpCloud, etc)
  • Expand multi-account customizations
  • Figgy Kubernetes Operator
  • Add features based on community feedback.

Stage 3: Expand support to new languages, backends.#

At this time Figgy operates as an abstraction and management framework over AWS native services like AWS Parameter Store & Secrets manager . In the future, this abstraction can be expanded facilitate the integration of 3rd party tools into the Figgy framework, including:

  • Hashicorp Vault & Consul
  • Kubernetes Configurations & Secrets