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

# Introduction

<pre className="ascii-art">
  {`
    ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
    ┃▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ opendata overview ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒┃
    ┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
    ┃                                                                ┃
    ┃   ╔timeseries══╗                            ╔vector══════╗     ┃
    ┃   ║ ┌────────┐ ║▒                           ║ ┌────────┐ ║▒    ┃
    ┃   ║ │slateDB │ ║──────────────┬─────────────║ │slateDB │ ║▒    ┃
    ┃   ║ └────────┘ ║▒             ▼             ║ └────────┘ ║▒    ┃
    ┃   ╚════════════╝▒      ╔════════════╗       ╚════════════╝▒    ┃
    ┃    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒      ║            ║▒       ▒▒▒▒▒▒▒▒▒▒▒▒▒▒    ┃
    ┃                        ║   Object   ║▒                         ┃
    ┃                        ║   Storage  ║▒                         ┃
    ┃                        ║            ║▒                         ┃
    ┃                        ╚════════════╝▒                         ┃
    ┃   ╔log═════════╗        ▒▒▒▒▒▒▲▒▒▒▒▒▒▒      ╔════════════╗     ┃
    ┃   ║ ┌────────┐ ║▒             │             ║            ║▒    ┃
    ┃   ║ │slateDB │ ║──────────────┴─────────────║   Buffer   ║▒    ┃
    ┃   ║ └────────┘ ║▒                           ║            ║▒    ┃
    ┃   ╚════════════╝▒                           ╚════════════╝▒    ┃
    ┃    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒                            ▒▒▒▒▒▒▒▒▒▒▒▒▒▒    ┃
    ┃                                                                ┃
    ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
    `}
</pre>

OpenData is a collection of operationaly simple, open source databases that
share a unified storage foundation on object storage.

Database software is often available for free as open source, but the real cost
comes from the operational expertise required to keep them running. Operators
must understand and configure behavior for replication, failover, backup,
capacity planning, and disaster recovery. These concerns multiply with every
additional database system since each ship with their own implementations.

Is there a better way? We believe that the general avaialbility of Object
Storage is the escape hatch.  Services like S3 provide durability, replication,
and availability *at commodity prices* with no operational overhead. When you
push replication and durability down to the storage layer, the database itself
becomes dramatically simpler. Entire categories of complexity disappear:

* **Durability & Availability**: opendata systems can be deployed in production with a
  single replica and still maintain durability and high write availability.
* **Failover & Scaling**: worker nodes are stateless and only use local
  disks for caching, making failovers and horizontal scaling trivial.
* **Backups & Branches**: all data is stored immutably, so backups and branches
  are as easy as marking data immune to garbage collection.
* **Cost to Serve**: object storage is not only less expensive than replicated disks,
  it also provides free cross-zone data transfer for ingestion and replication.

By implementing these patterns once in [SlateDB](https://slatedb.io), we can
share them across all databases in the OpenData family and provide a unified
operational experience.

## Databases

<CardGroup cols={2}>
  <Card title="Timeseries" icon="chart-line" href="/timeseries">
    Prometheus-compatible metrics database
  </Card>

  <Card title="Log" icon="scroll" href="/log">
    Key-oriented event streaming
  </Card>

  <Card title="Vector" icon="brain" href="/vector">
    SPANN-style approximate nearest neighbor search
  </Card>

  <Card title="Buffer" icon="inbox" href="/buffer">
    Highly-available ingestion buffer
  </Card>
</CardGroup>