store alternatives and similar packages
Based on the "Configuration" category.
Alternatively, view store alternatives based on common mentions on social networks and blogs.
-
koanf
Simple, extremely lightweight, extensible, configuration management library for Go. Supports JSON, TOML, YAML, env, command line, file, S3 etc. Alternative to viper. -
konfig
Composable, observable and performant config handling for Go for the distributed processing era -
gookit/config
📝 Go configuration manage(load,get,set,export). support JSON, YAML, TOML, Properties, INI, HCL, ENV and Flags. Multi file load, data override merge, parse ENV var. Go应用配置加载管理,支持多种格式,多文件加载,远程文件加载,支持数据合并,解析环境变量名 -
gcfg
read INI-style configuration files into Go structs; supports user-defined types and subsections -
goConfig
DISCONTINUED. goconfig uses a struct as input and populates the fields of this struct with parameters from command line, environment variables and configuration file. -
joshbetz/config
🛠 A configuration library for Go that parses environment variables, JSON files, and reloads automatically on SIGHUP. -
configuro
An opinionated configuration loading framework for Containerized and Cloud-Native applications. -
hocon
go implementation of lightbend's HOCON configuration library https://github.com/lightbend/config -
configure
Configure is a Go package that gives you easy configuration of your project through redundancy -
Genv
Genv is a library for Go (golang) that makes it easy to read and use environment variables in your projects. It also allows environment variables to be loaded from the .env file. -
swap
Instantiate/configure structs recursively, based on build environment. (YAML, TOML, JSON and env).
CodeRabbit: AI Code Reviews for Developers

Do you think we are missing an alternative of store or a related project?
Popular Comparisons
README
Store
Store is a dead simple configuration manager for Go applications.
I didn't like existing configuration management solutions like globalconf, tachyon or viper. First two just don't feel right and viper, imo, a little overcomplicated—definitely offering too much for small things. Store supports either JSON, TOML or YAML out-of-the-box and lets you register practically any other configuration format. It persists all of your configurations in either $XDG_CONFIG_HOME or $HOME on Linux and in %APPDATA% on Windows.
Look, when I say it's dead simple, I actually mean it:
package main
import (
"log"
"time"
"github.com/tucnak/store"
)
func init() {
// You must init store with some truly unique path first!
store.Init("cats-n-dogs/project-hotel")
}
type Cat struct {
Name string `toml:"naym"`
Clever bool `toml:"ayy"`
}
type Hotel struct {
Name string
Cats []Cat `toml:"guests"`
Opens *time.Time
Closes *time.Time
}
func main() {
var hotel Hotel
if err := store.Load("hotel.toml", &hotel); err != nil {
log.Println("failed to load the cat hotel:", err)
return
}
// ...
if err := store.Save("hotel.toml", &hotel); err != nil {
log.Println("failed to save the cat hotel:", err)
return
}
}
Store supports any other formats via the handy registration system: register the format once and you'd be able to Load and Save files in it afterwards:
store.Register("ini", ini.Marshal, ini.Unmarshal)
err := store.Load("configuration.ini", &object)
// ...