This proposal defines terminology related to servers, instances, and tenants in a Fediverse context. The goal is to provide consistent vocabulary for specifications, implementations, and documentation across projects.
Fediverse discussions use overlapping but sometimes inconsistent terminology when describing software, deployments, and administrative boundaries. In particular, the words “server” and “instance” are often used interchangeably.
The terminology issue becomes even more clear for multi-tenant server implementations and instances. As more projects implement multi-tenant architectures, clear terminology becomes important for:
This document proposes terminology that other FEPs and implementations may reference.
A server implementation is a software codebase that implements one or more Fediverse-related protocols (such as ActivityPub). This software must be deployed on computational infrastructure to participate in the Fediverse.
Characteristics:
Example Implementations:
The word server may also refer to computational infrastructure (physical or virtual hardware, containers, etc.) in some contexts. This is not how the word is used in this proposal, which only refers to server software.
A server instance is a specific deployment of a server implementation, including its running processes, configuration, and associated persistent storage, operated by a defined administrative authority.
Characteristics:
Examples:
In common Fediverse usage, “instance” often implicitly refers to a server instance; this document uses the explicit term “server instance” for clarity.
A tenant in a Fediverse context is a logically and administratively distinct group of actors and related data that is served by a server instance and for which the server provides isolated configuration, policies, and data separation.
This definition adapts the general notion of multitenancy where a single software instance serves multiple tenants while isolating their data and configuration to the specific case of Fediverse services.
Characteristics:
https://tenant-a.server.example/, https://tenant-b.server.example/, https://tenant-c.example/).Examples:
https://alice.example/ and https://bob.example/).Related concepts:
“Bring your own domain” (BYOD): In general, this does not require a multi-tenant instance although multi-tenant support will typically provide the feature. A user-registered domain can also be used with a single-tenant self-hosted server, for example.
Reverse-proxied cluster: An architecture with multiple single-tenant server instances with a reverse proxy is not considered a multi-tenant instance given the definitions in this proposal. However, more broadly, it could be considered a multi-tenant cluster architecture.
+-----------------------+
| Server implementation |
+-----------------------+
| software codebase |
| release artifacts |
+-----------------------+
|
| 0..*
v
+-----------------------+
| Server instance |
+-----------------------+
| running deployment |
| config + storage |
| admin boundary |
+-----------------------+
| \
| \
| \
v v
+----------------+ +----------------+
| Single tenant | | Multi-tenant |
| deployment | | deployment |
+----------------+ +----------------+
\ /
\ /
\ /
\ 1 / 1..*
v v
+----------------+
| Tenant |
+----------------+
| isolated data |
| isolated policy|
| admin boundary |
+----------------+
This document:
CC0 1.0 Universal (CC0 1.0) Public Domain Dedication
To the extent possible under law, the authors of this Fediverse Enhancement Proposal have waived all copyright and related or neighboring rights to this work.