Introduction

Habitat provides a data ownership layer for organizations. This means that building a product or application with Habitat looks a bit different than the traditional product stack today. The components that Habitat provides as primitives for teams to use are authentication & identities, fine-grained permissioning, and syncing primitives. Using these foundations, products built on Habitat push to and pull from an Organizational Data Server to deliver richer user experiences.

Architecturally, Habitat is an adaptation of AT Protocol that directly solves for community and organizational needs. Products and applications build on Habitat are roughly analogous to AppViews in AT Protocol. We highly recommend reading and getting familiar with a few basic concepts of AT Protocol, such as user repositories, DIDs, lexicons, AppViews, and how sync works. Though we provide high-level documentation of relevant components, more in-depth documentation and linked readngs of these concepts can be found on the official AT Protocol docs here.