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
| Layer | What it guarantees | Checked by |
|---|---|---|
| TLS per site | You are talking to this site, and nobody listened in | the visitor's browser or client |
| Signed plugins | This plugin is byte for byte what its publisher signed | FFS, every time it loads one |
| Chain of trust | That publisher is allowed to ship plugins at all | FFS, against a root compiled into it |
| Signed packages | The installation packages and their index came from us unaltered | the operating system's package manager |
| The guard | Hostile traffic is recognised and refused before it reaches a site | the FFS front-end and each site's worker |
| Fail closed | A broken configuration keeps the door shut, never open | every 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
- Signed plugins and the chain of trust — why an FFS server refuses code nobody released.
- TLS per site — a complete TLS profile for every site on the server.
- The guard — blacklists, attack patterns, honeypots and rate limits in front of every site.
- Answering bots with silence — a seven-filter classifier that drops hostile automation without telling it why.
- Fail closed — what FFS does when something is wrong.
- Privacy and data protection — cookies, consent and logs.
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.
