About the service
Tired of copied YAML that diverges between environments and breaks in production? I design configuration in Pkl, a typed configuration language from Apple, to make your settings code you can trust. Instead of manually editing dozens of almost identical JSON, YAML, plist or properties files you get a single typed source of truth with classes, templates and validation that catches errors before release.
What you will get: strictly typed Pkl schemas for application configuration; reusable templates and modules that eliminate duplication across environments (dev, staging, prod); generators that produce clean JSON, YAML, plist or Java properties on demand; Kubernetes manifests and CI pipeline descriptions assembled from a single typed model. Any constraint important to you — ports, replica count, required fields, valid enums — becomes a check at config build time, so invalid configuration simply won't be generated.
The process is transparent. I parse your current sprawling config, model it with Pkl classes and templates, embed output generation into the build or CI and hand over documentation with examples your team can extend. I also migrate existing YAML or JSON to Pkl and set up local rendering so nothing remains a black box. The result is fewer outages, faster changes and configuration that reviews like real code.
What you will get: strictly typed Pkl schemas for application configuration; reusable templates and modules that eliminate duplication across environments (dev, staging, prod); generators that produce clean JSON, YAML, plist or Java properties on demand; Kubernetes manifests and CI pipeline descriptions assembled from a single typed model. Any constraint important to you — ports, replica count, required fields, valid enums — becomes a check at config build time, so invalid configuration simply won't be generated.
The process is transparent. I parse your current sprawling config, model it with Pkl classes and templates, embed output generation into the build or CI and hand over documentation with examples your team can extend. I also migrate existing YAML or JSON to Pkl and set up local rendering so nothing remains a black box. The result is fewer outages, faster changes and configuration that reviews like real code.
