Technical Foundations
Diving into the technical details of how foundation4 is built and why
Technical Foundations
One key per classification: what foundation4 encrypts, and what it doesn't
A map of foundation4's encryption for security reviewers. Which data is encrypted, with which key, where each key lives, what stays readable to the database, and which controls stay with the operator.
Technical Foundations
Scoping every search to the reader with classifications
One foundation4 pipeline can serve many audiences, each seeing only its share. This post explains classifications, inheritance and matching modes, and how scoping runs in the same query as the ranking.
Technical Foundations
Running retrieval on an isolated network: what works offline
A planning checklist for installing foundation4 on a network with no internet access. Which models, splitters and model servers work offline, how they reach the cluster, and what to confirm before you start.
Technical Foundations
API keys for retrieval integrations: one key for each application
A practical guide to the API keys a retrieval integration needs in foundation4. It covers creating a key, granting permissions, classification allow-lists, expiry and rotation, and the errors you will see.
Technical Foundations
Why we built on PostgreSQL
Why foundation4 keeps text, vectors, metadata and version history in one PostgreSQL database, how that compares with document databases and dedicated vector stores, and what the choice costs.
See foundation4 inside your perimeter.
Tell us about your environment and we will walk you through how foundation4 fits.