The lockfile for
infrastructure schemas.
Versioned, lazy-fetched, IDE-native schema management for Kubernetes CRDs, GitHub Actions, Terraform providers, and more.
One lockfile. Every editor. Every CI. Free forever for public schemas.
Schemas are the missing dependency.
Your code has lockfiles. Your provider binaries have lockfiles. But the schemas your IDE and CI validate against? Ad-hoc, version-blind, and silently drifting across environments.
No autocomplete for CRDs
VS Code shows nothing for operator.victoriametrics.com/v1beta1. Same API version, different fields across operator releases β your editor has no idea.
Action version skew
actions/checkout@v4 adds inputs that don't exist in v3. No IDE shows the schema. Workflows break silently on bumps.
Terraform provider drift
Same module deployed against two provider versions = two different schemas. Validation passes one, fails the other.
CI uses different schemas than your IDE
Validation passes locally. Fails in CI. Or worse β passes both and breaks on apply.
One primitive across every ecosystem.
Schemas are fetched lazily from a public API, pinned per-file or via lockfile, cached locally forever. Your IDE, your CLI, and your CI all use the same source of truth.
Public schema API
CDN-backed, content-addressed, free forever. Lazy-fetch only what your workspace actually uses.
Lockfile pinning
One schemalock.yaml per repo. Pin schemas to producer versions. Team gets identical IntelliSense.
IDE-native
Plugin for VS Code, JetBrains, Neovim. Status bar shows pinned version per file. Switch with one click.
CI parity
Same schemas in CI as in your editor. schemalock validate uses the lockfile. No drift, no surprises.
Schema diff
See exactly what changed between operator 0.50 and 0.52 before you upgrade. Per ecosystem, per version.
Multi-environment aware
Dev cluster on a newer operator than prod? Your editor warns at edit time, not on broken apply.
Built for every declarative ecosystem.
One CLI, one IDE plugin, one lockfile format. Each new ecosystem reuses the same primitive β start with what you use most, expand naturally as we ship more.
Be first to try it.
We're building the v1 (Kubernetes CRDs) now. Drop your email to get notified when the plugin and CLI hit beta, plus an invite to the early-access Discord.