Most web platforms treat security as something you add: a plugin, a reverse proxy, a checklist before go-live. FFS was designed the other way round. The questions "who built this code?", "who is this visitor?" and "what happens when the configuration is wrong?" are answered by the core, for every site, before any application code runs.

The layers at a glance

LayerWhat it guaranteesChecked by
TLS per siteYou are talking to this site, and nobody listened inthe visitor's browser or client
Signed pluginsThis plugin is byte for byte what its publisher signedFFS, every time it loads one
Chain of trustThat publisher is allowed to ship plugins at allFFS, against a root compiled into it
Signed packagesThe installation packages and their index came from us unalteredthe operating system's package manager
The guardHostile traffic is recognised and refused before it reaches a sitethe FFS front-end and each site's worker
Fail closedA broken configuration keeps the door shut, never openevery component that reads one

The layers are independent on purpose. A valid TLS certificate says nothing about who built a plugin; a signed package says nothing about whether FFS will load what is inside it. Each question gets its own answer.

In this section

Security in the applications, too

The same principles carry into the applications built on FFS. In Depotify, every repository type uses one rule engine where the most specific rule wins and an exact tie is a denial; a read that is not allowed answers 404 so a private repository does not even reveal that it exists; access tokens are stored only as hashes; and every decision is written to an audit log.