Design
Stakeholders
Groundwork is primarily targeted to Developers to make it easier to develop federated applications, especially ones that target specialized business domains.
| Stakeholder | Key benefits | 
|---|---|
| Developer: Primary stakeholder. Anyone that wants to build modular domain-specific application services that can be federated and are compliant to Fediverse open-standards. | 
 | 
| Provider: Secondary stakeholder. Party that offers an application or add-on, packaged as service modules. | 
 | 
| Sysadmin: Person responsible for maintaining a Groundwork server and its service module deployments. | 
 | 
| Host: Indirect (not shown in domain model). Party that provides Groundwork as a service platform. | 
 | 
| Fedizen: Indirect (not shown in domain model). Person with accounts on the service platform. | 
 | 
Application domains
Apart from the layering presented above there are four functional areas, or application domains:
| Domain | Description | 
|---|---|
| Groundwork Core | Common server features, such as configuration, logging, identity and authentication, security, federation endpoints, and more. | 
| Groundwork Service Modules | Framework for creation of dynamically loaded Service Modules. This includes bootstrap projects to jumpstart development. | 
| Groundwork Service Administration | Facilities for Sysadmins and Providers to deploy and manage Service Modules at runtime. | 
| Groundwork Account Management | Facilities for managing Member Accounts on the platform. |