Get started

Pick your language. Each SDK builds on the library that ecosystem already trusts: that library keeps loading and parsing, and docuconf adds descriptions, secrets, constraints, boot checks and contract export.

• Goon caarlos0/env v11conformance 134/134
• TypeScript (T3 Env)on T3 Env + Zod 4conformance 131/134
• TypeScript (NestJS)on @nestjs/config + class-validatorconformance 131/134
• .NETon Options pattern + appsettingsconformance 132/134
• Pythonon pydantic-settings 2conformance 134/134
• Rubyon anyway_config 2conformance 134/134
• Java (Spring Boot)on Spring Boot 3 / 4 @ConfigurationPropertiesconformance 134/134
• Kotlinon Hoplite 3conformance 134/134
• Ruston figment + serdeconformance 134/134
• Swifton swift-configurationconformance 132/134
• Elixiron config/runtime.exsconformance 134/134
• Gleamon envoy + gleam/dynamic/decodeconformance 132/134
• C++on CLI11conformance 134/134
• PHP (Laravel)on Laravel config + vlucas/phpdotenvconformance 134/134
• PHP (Symfony)on Symfony config + %env()% processorsconformance 134/134
• COBOLon GnuCOBOL copybooks + docuconf execconformance 134/134

Each page takes the same steps, in the same order: install, declare, load at boot, run it and see an error, test it, export the contract, and fit it into your framework. Every snippet is compiled or run against the SDK's main branch in CI.

All 16 SDKs are v0.1 alphas and none is on a package registry yet, so each page installs from git. They implement the same specification and pass the shared conformance suite; the SDK requirements page compares what each one supports.

Your language is not here?

Any language can have an SDK. The specification says what an SDK must do, and the shared conformance suite checks it mechanically. See Get involved.