> ## Documentation Index
> Fetch the complete documentation index at: https://docs.databite.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Databite is a self-hosted integration library that eliminates months of boilerplate code. Powerful custom connector builder, pre-built connectors for popular services, and complete control over your infrastructure.

<img className="block rounded-md" src="https://mintcdn.com/databite/E1cMmqUXpP7jVZbO/images/hero.png?fit=max&auto=format&n=E1cMmqUXpP7jVZbO&q=85&s=55f5f1e54e432d16ec70c542d4a96d4a" alt="Databite SDK" width="1280" height="720" data-path="images/hero.png" />

## Quick Start

Get up and running with Databite in minutes:

<Steps>
  <Step title="Start your server">
    Create and run a Databite server that hosts connectors and integrations
  </Step>

  <Step title="Add integrations">
    Add built-in or custom connectors and create integrations on your server
  </Step>

  <Step title="Manage or connect">
    Use the self-hosted dashboard to manage everything, or integrate `@databite/connect` into your app for user connections
  </Step>
</Steps>

## Three-Tier Hierarchy

Databite uses a clear three-tier hierarchy for managing integrations:

1. **Connector** - A template/blueprint that defines what properties and configurations are available for a service.
2. **Integration** - An instance of a connector where configuration values have been filled in.
3. **Connection** - When someone actually uses an integration to connect to a service.

## What's Next?

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Stand up a server and connect from your app in minutes
  </Card>

  <Card title="Dashboard" icon="dashboard" href="/guides/hosting-the-dashboard">
    Self-host a management dashboard for your server
  </Card>

  <Card title="Server API" icon="book" href="/packages/server">
    Explore server setup and API endpoints
  </Card>

  <Card title="Example Web App" icon="code" href="/examples/webapp">
    See a working client that talks to your server
  </Card>
</CardGroup>