# Overview

> Learn how to get started with Roadie Context Store.

*Published: 2026-05-25T12:00:00.0Z*


## Introduction

The Data Store is a centralised database of metadata about the software you create and the authors of that software. Everything from cloud resources from AWS to org charts from Workday.

The Data Store is constructed by Data Sources which use Integrations to retrieve items from a given system of record. The retrieved items are typically structural data such as users, repositories, projects, or accounts are stored as nodes in the context graph.

## Integrations

Integrations group all Data Sources.

A single Integration manages configuration and controls rate limiting across all scheduled Data Sources.

For example, if you have 15 Data Sources configured under the `AWS` integration to pull things like S3 buckets and EKS Clusters, the integration will manage rate limits across that set of Data Sources to ensure the load is balanced.

Configuring an Integration unlocks all available Data Sources for that integration.

The Context Store comes with many pre-baked Integrations that only require the addition of a secret or config in order to be activated.

Custom Integrations can be configured using the `+ New` button.

To connect an integration quickly, use one of the [Pre-built Integrations](/docs/context/data-store/pre-built-integrations/github/) as a reference.

![integrations](./integrations.webp)


## Data Sources

Data Sources are single endpoints or groups of endpoints that return an object that you'd like to store in the Data Store. 

For example, let's imagine you want to retrieve users from GitHub members. You need to first call the GitHub Members endpoint to get the `login` of each member, then enumerate through that list to get the email and complete user entity associated to each login name. 

These can also be enriched with secondary calls, if you'd like to store an item.

For example, AWS S3 buckets can be retrieved from the AWS Cloud Formation API using a single call. However, this object can be sparse. A richer array of information can be appended by making a second call using the output of the first and adding the returned metadata to the initially retrieved objects.

The Context Store comes with many pre-built Data Sources that only require an active Integration to be enabled.

Custom Data Sources can be configured using the `+ New` button.

After ingesting data, define how entities connect in [Relationships](/docs/context/data-store/relationships/).

![data-sources](./data-sources.webp)


## Secrets & Config

Each Integration requires different configuration and secrets. You can add these in the `Secrets` section of the application.

It's also worth bearing in mind the nature of the data you want to pull. Many secrets and credentials are scoped to only allow the retrieval of specific kinds of information from a third-party. 

Check with each third-party to ensure the tokens you provide are able to retrieve the information requested.

For examples of required credentials and setup expectations, see the [GitHub](/docs/context/data-store/pre-built-integrations/github/) and [PagerDuty](/docs/context/data-store/pre-built-integrations/pagerduty/) integration guides.

![secrets](./secrets.webp)