Kalo ecosystem explorer

Find the path from contract to code.

Specifications define durable knowledge. Plugins turn explicit formats into implementation artifacts. Explore each transformation, then compose the path your stack needs.

40 open-source plugins12 specifications35 declared formats0 integrity-verified releases

Compilation lab

See the whole graph execute.

Follow an actual Morphe model through three pinned WASM plugins into Go, TypeScript, and PostgreSQL. Every displayed input, artifact, and output includes the SHA-256 recorded by the successful CLI run.

ContractMorphe YAMLKA:MO1:YAML1
WASM plugins3 pinned stagesGo · TS · PSQL
Output34 generated fileshash recorded

Transformation catalog

Small plugins. Explicit boundaries.

Registry facts and public source evidence are shown separately. A listing is not called verified until an artifact hash is available.

30 plugins are currently listed by the operational registry; newer public-source plugins are marked as pending registry sync.Open registry ↗

Loading catalog filters…

Portable contracts

Specifications are the durable layer.

Formats make each contract concrete. Producers and consumers can change while the specification remains explicit.

dataassertions

Data Assertions

A declarative specification for targeted assertions against CSV and JSON data files. Validates row counts, column types, and containment.

KA:DA1:YAML1KA:DA1:GO1KA:DA1:GO_TEST1
datasnapshots

Data Snapshots

A declarative specification for comparing exported data against committed golden files. Supports CSV and JSON with ignore rules for volatile fields.

KA:DS1:YAML1KA:DS1:GO1
httpcheck

HTTP Check

A declarative specification for describing HTTP request/response interactions with assertions. Defines scenarios with shape, value, and capture assertions for API validation.

KA:HC1:YAML1KA:HC1:GO1KA:HC1:GO_TEST1
KA:PL1

Kalo Plugin Manifest

Defines the portable manifest contract for Kalo plugin identity, inputs, outputs, stores, and configuration.

KA:PL1:YAML1
KA:MO1

Morphe

A declarative schema definition language for defining data models, enums, structures, and entities. Morphe schemas are used to generate code, database schemas, and API definitions.

KA:MO1:YAML1KA:MO1:PSQL1KA:MO1:GO1KA:MO1:TS1
morphe-diff

MorpheDiff

A specification for describing changes between two Morphe schema versions. Used to generate migration scripts and changelogs.

KA:MD1:YAML1KA:PSQL:MIGRATION1
morphemap

MorpheMap

A declarative type mapping and transformation specification for cross-domain structural mapping between Morphe types and external systems.

KA:MM1:YAML1KA:MM1:GO1KA:MM1:TS1
morpherepo

MorpheRepo

A specification for defining data access contracts derived from Morphe models. Describes repository interfaces, identifiers, filters, and CRUD operations.

KA:MR1:YAML1KA:MR1:GO1KA:MR1:GO_PSQL1
openapi

OpenAPI

The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to RESTful APIs.

KA:OA1:YAML1KA:OA1:HTML_DOCS1KA:OA1:GO_CLIENT1KA:OA1:REPORT1
KA:UB1

UI Bindings

Maps UI page structures to backend operations, SDK methods, fields, and route parameters.

KA:UB1:YAML1KA:UB1:GO1
uiflows

UI Flows

A declarative specification for describing user interaction sequences. Defines flows with navigation, click, fill, and assertion steps referencing testIds.

KA:UF1:YAML1KA:UF1:GO1
uipages

UI Pages

A declarative specification for describing UI page structure. Defines pages, ordered elements, testIds, and visibility conditions.

KA:UP1:YAML1KA:UP1:GO1KA:UP1:PLAYWRIGHT1

Extend the graph

Built a Kalo plugin?

Tell us what it transforms. We will help review the manifest, compatibility, and path to a registry listing.

Get your plugin listed →