Building the Future of Open ERM
K-Int's view of FOLIO ERM stewardship, sustainable modernisation, knowledge-base choice, and why alternative open implementations strengthen the community.
Topic
FOLIO Licenses
Evidence and open questions from running the FOLIO Licenses module as a standalone, tenant-aware application.
Foundry now runs a small FOLIO app suite on a laptop
Licenses, Agreements, Open Access, Serials Management, and ILL now run together in Foundry through descriptor-selected module-federation artifacts.
Foundry platform services and the docking layer
How Foundry is separating platform support APIs from FOLIO utility modules, and why acquisition units belong behind a provider-backed platform boundary.
The first Foundry roadmap: FOLIO ERM, artifacts, Kubernetes, and external ILS
The spike has produced enough evidence to publish the first roadmap: local runtime, artifacts, operational catalog, Kubernetes demo substrate, and external ILS extension.
From FOLIO Licenses and Agreements wrappers to a UI artifact supply chain
How Foundry widened a narrow ui-licenses proof into repeatable ERM wrapping evidence across Agreements, Open Access, and ILL.
Foundry from spike to shape: FOLIO Licenses, Loom, Lattice, and Envoy
What the FOLIO Licenses proof now demonstrates, how tenant work happens, and where Foundry goes next.
Foundry after the spike: from FOLIO Licenses proof to Loom lifecycle
Turning the standalone FOLIO Licenses proof into the first durable Loom lifecycle foundation.
A first look at Foundry: FOLIO Licenses without Okapi
Running FOLIO Licenses as a standalone, tenant-aware ERM application without Okapi or Eureka.