Foundry status update: making it practical to operate
Self-hosted storage, scalable routing and a working nightly Snapshot: a progress report on the less visible work that makes Foundry usable in practice.
Topic
Foundry
Lab notes on Foundry's control plane, runtime-composed application shell, module developer tooling, and deployment substrates.
Maintenance needs operational visibility
A stuck Open Access module led us from a shared locking defect to our first live Foundry tenant upgrade, making the less visible work of sustainable maintenance concrete.
Making the value beyond Apache visible
Release Frontier turns K-Int's FSL release history, audited delivery effort and Apache publication state into an understandable case for sponsoring earlier community releases.
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.
FOLIO: How Many Grapes Went into the Wine?
An opinion on operational enclosure, ecosystem enclosure, and the reciprocal obligations needed to sustain open-source library software.
Foundry's operational spine is starting to show
A short bookend on the hosted Foundry work after the Console adoption-loop proof, and why the next lab pivot turns toward OpenRS and ORS-Appliance.
The business layer is infrastructure for the mission
A working note on ki-console, Foundry, and why sustainable open library infrastructure needs an adoption loop as well as a developer loop.
Foundry Module SDK: profiles for a smaller FOLIO dev loop
A walkthrough of the new Foundry Module SDK profile model: start a production-shaped module runtime, then substitute only the backend or frontend you are actively changing.
Why not the whole of FOLIO?
Foundry could become a lighter self-hosting substrate for FOLIO, but the immediate goal is a sovereign home for K-Int apps and ILS-neutral library extensions.
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.