Introduction

The Inrupt Enterprise Solid Server (ESS) is a Solid Pod Server. Its microservices architecture enables simple scaling, high performance, and support for highly available deployment configurations.

Features

Pod Management

The Pod Provisioning Service creates Pods. Pods are where users store their data. With ESS’ support for the Solid Protocol specification, navigating, creating, deleting and editing Solid Resources within a Pod is directly supported via the standard HTTP interfaces.

Identity

WebID

The WebID Service issues and manages WebIDs. A WebID is a URI that uniquely identifies an agent (a person, organization, etc).

In ESS, Pods and WebIDs are created independently of each other and WebID profiles are not hosted on the Pods. This allows for multiple Pods per WebID, prevents users from locking themselves out of their Pods, and allows users to obtain their WebID or Pods from alternative providers.

For more information, see WebID Service

Client ID

An application identifies itself using a client identifier (Client ID). ESS supports the following Client ID types:

a URL that dereferences to a Client ID Document, or
a registered value (either through OIDC dynamic or static registration).

For more information, see:

Security

ESS’ security features include:

Authentication to support login with any existing OIDC-compliant identity provider
Support for User Managed Access Grant 2.0 (UMA)
Support for Access Control Policies (ACP)
Support for Access Requests and Grants
Support for Auditing

For more information, see Security

Notifications

ESS provides a secure implementation of a WebSocket notification protocol. ESS WebSocket service sends asynchronous notifications upon changes to Resources. Applications can subscribe to a particular Resource, including a Container, and receive notifications upon changes to the subscribed Resource(s).

For more information, see WebSocket Notification Service