Self-hosting FOLIO with Foundry: two libraries, one ILL system
A reproducible FOLIO LSP install on Podman passes 11 tests across seven app areas, including an ISO 18626 interlibrary loan between two institutions in one tenant.
Topic
FOLIO ERM experiments
Lab notes on running FOLIO-adjacent ERM capabilities such as Licenses and Agreements in smaller, runtime-composed systems.
Alma and FOLIO resource sharing: see the library staff workflow
Follow an Alma patron’s request to a FOLIO supplying library in Casey Henderson and Richard Mann’s interactive OpenRS DCB demonstration.
Show, don't tell: OpenRS resource sharing at the library desk
Two interactive walkthroughs from Casey Henderson and Richard Mann show everyday OpenRS borrowing and lending across Alma, FOLIO and Koha.
This week in Foundry: more of FOLIO, and preparing to run it elsewhere
Acquisitions, Lists, Circulation Log and Courses broaden Foundry's native FOLIO selection, with ILL testing and repeatable independent installations next.
This week in Foundry: more of FOLIO, one Workspace at a time
Catalogue tools, Calendar, Notes and native Circulation bring Foundry closer to full FOLIO, with selectable modules in Console and portability on the drawing board.
This week in Foundry development: whose authority is it anyway?
What real FOLIO workflows taught us about authentication, authorization, delegation and the limits of module replaceability.
This week in Foundry development
Building towards affordable FOLIO for galleries, libraries, archives and museums: mod-ciim, Source Record Storage, Kafka and repeatable release channels.
FOLIO modules on Grails 8: a stronger foundation for your next upgrade
Six K-Int FOLIO backends now run on Grails 8 and JDK 25, with container SBOMs, build provenance and documented upgrade qualification. Here is why implementors should plan their adoption.
A Dashboard fix shouldn’t mean a whole-platform release
Foundry Release Control connects Git releases, container images and independent frontend bundles into continuously maintained release descriptions, without forcing upgrades.
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.
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.
OLF sustainability
K-Int proposes a temporary FSL funding buffer for completed FOLIO engineering, with Apache-2.0 release and an explicit aim to merge the work back into the community repositories.
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 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.
Federated Identity in Libraries Is Already Happening
A response to Amanda Ferrante's Scholarly Kitchen article, and an argument that library federation is not only about login protocols but also about trust, attestation, and shared circulation across institutions.
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.