Schema Registry
A catalog is where a schema-backed model resolves the schema it validates against. Catalogs decouple a Guardrail from any single schema format or registry: the model references a catalog by name, and the catalog supplies the actual schema at runtime, by subject, by topic, or by ID.
name: zilla-namespace
catalogs:
host_filesystem:
type: filesystem
options:
subjects:
tool-payload:
path: tool-payload.jsonLocal Catalogs
Local catalogs bootstrap a Guardrail quickly or package a schema that rarely changes alongside the Zilla install.
- Filesystem reads schemas from files relative to
zilla.yaml. - Inline embeds the schema directly in
zilla.yaml, useful when the local filesystem isn't accessible.
Remote Catalogs
Remote catalogs fetch schemas from an external registry, so a Guardrail always validates against the latest published schema without a redeploy. Zilla can also pin a specific schema version or ID.
- Apicurio Registry
- Karapace Schema Registry
- Confluent Schema Registry (Zilla Plus)
- AWS Glue (Zilla Plus)
Once a catalog is registered, a model references it by name and specifies which subject, topic, or schema ID to fetch. See Validate for how the two work together.

