FFS — the Foundational Feature Server — is a platform for web applications written in modern C++. It is often mistaken for a website builder, because the sites you are reading now run on it. But a page of text is the simplest thing FFS does. The same server hosts an artifact repository manager with twenty-one repository types, git and Mercurial and Subversion hosting, a token-protected REST API and a rule engine — all of it written as FFS plugins, none of it a change to the core.

A small core, and everything else a plugin

┌───────────────────────────────────────────────────────────────┐
│                         FFS core                              │
│  sites · routing · sessions · themes · languages · consent    │
│  TLS · guard · plugin verification · configuration checking   │
├───────────────────────────────────────────────────────────────┤
│  page components    │  services            │  identity        │
│  what a visitor     │  HTTP / SSH APIs     │  who you are,    │
│  sees and uses      │  for clients and CI  │  what you may do │
└───────────────────────────────────────────────────────────────┘
          every plugin is a signed shared library

The core does only what every application needs and nobody should write twice: it receives the request, decides which site it belongs to, guards it, manages the session, renders the navigation, the theme and the language, and loads the plugins the site asks for — after it has verified their signature.

Everything a site actually does is a plugin of one of three kinds:

KindWhat it isExamples
Page componentAn interactive page or a part of one — a slot on a pagearticles, blog, portfolio, contact form, a repository browser, an account page
ServiceA back-end endpoint under a path of the site, for programs rather than peoplea git server, a package registry, a REST API
Identity pluginAuthentication, authorization or the login screenpassword accounts, roles, a login page, a company directory, single sign-on, an identity provider

A site enables a plugin by naming it in its configuration. Installing a new component does not mean rebuilding or forking the server, and removing one does not leave half of it behind.

Built for applications, not only for pages

Server-side state, real-time updates. An FFS page is a live application running on the server. Browsers get an interactive interface, and the server can push changes to it over WebSocket while the visitor is looking. There is no client framework to maintain and no API layer written only for your own front end.

Plain HTML where it matters. Search engines, link previews and other automated readers get a fully rendered HTML page, not a loading script. The list of such readers is configuration, and the site publishes a sitemap.xml with every language version of every page.

One configuration language. Sites, pages, guards, rules and services are configured in FSON — a JSON superset with comments, unquoted keys and a one-character way to switch a setting off without deleting it. Files are checked before they are used and re-read when they change.

Languages and themes. Every page can exist in several languages, chosen from the address, the visitor's explicit choice or the browser's preference — in that order — and every component carries its own translations. Themes are CSS; a site picks one and may add its own styles.

Privacy by default. Cookies are declared by the components that set them. The cookie policy page is generated from those declarations, the consent dialog appears only when a site actually sets a cookie that needs consent, and a cookie a site no longer declares is removed from the visitor's browser.

Why C++

Because a server that is exposed to the internet all day should be small, fast and predictable. FFS is written in C++23 and compiled to native code. There is no interpreter on the server, no package manager running inside the application, and no plugin loaded that was not built and signed for it.

What you can build

  • Product and documentation sites — the fedem sites, this one included.
  • Self-hosted developer infrastructure — Depotify, a complete artifact repository manager, is a set of FFS plugins.
  • Internal portals and line-of-business applications — anything that needs sign-in, roles, an audit trail and an API next to its pages.
  • Customer-specific applications — FEDEM develops plugins to order: tell us what you need.

Licensing and pricing

FFS is commercial software from FEDEM. There is no price list: a licence depends on how many sites and which components you run, and on the support and custom development you need — so we make you an offer for exactly that. Talk to us.