# Overview

## What is Heimdahl.xyz?

**Heimdahl** is a cloud-based, all-in-one solution designed to address the blockchain data needs of users across multiple industries. It provides seamless access to both historical and real-time data from a wide range of blockchains, all through user-friendly REST and WebSocket APIs. Whether you're a developer, data analyst, or enterprise, **Heimdahl** securely routes blockchain data to your application, enabling effortless integration and analysis in your preferred programming language.

### State of modern onchain data processing<br>

<figure><img src="/files/RzgdkPjQOoZKZVBDk8SO" alt=""><figcaption></figcaption></figure>

### Unified data stream&#x20;

<figure><img src="/files/6uM7fEECvVw0Bph7csWm" alt=""><figcaption></figcaption></figure>

Heimdahl provides complete blockchain data infrastructure:

* Direct sourcing from blockchain nodes&#x20;
* Instant API access
* Real-time data streaming
* Open source consumer ready to setup and collect&#x20;
* Historical data access<br>

## Blockchain Data Infrastructure Comparison

| Feature                | Heimdahl                     | The Graph                        | Custom Infrastructure       |
| ---------------------- | ---------------------------- | -------------------------------- | --------------------------- |
| **Setup Time**         | ✅ Minutes to connect         | ❌ Days/Weeks to deploy subgraphs | ❌ Months to build           |
| **Integration**        | ✅ Standard REST/WebSocket    | ❌ GraphQL learning required      | ❌ Custom implementation     |
| **Real-time Data**     | ✅ WebSocket streaming        | ❌ Limited/No streaming           | ❌ Complex to implement      |
| **Data Access**        | ✅ REST, WebSocket, JDBC/ODBC | ❌ GraphQL only                   | ❌ Custom solutions          |
| **Development Effort** | ✅ Zero development needed    | ❌ Subgraph development required  | ❌ Significant development   |
| **Maintenance**        | ✅ Zero maintenance           | ❌ Subgraph maintenance needed    | ❌ Ongoing maintenance       |
| **Query Language**     | ✅ Standard SQL/REST          | ❌ GraphQL only                   | ❌ Custom implementation     |
| **Infrastructure**     | ✅ Fully managed              | ❌ Node deployment needed         | ❌ Self-managed              |
| **Cost Structure**     | ✅ Predictable pricing        | ❌ Query-based costs              | ❌ High infrastructure costs |
| **Historical Data**    | ✅ Instant access             | ❌ Needs indexing time            | ❌ Needs building/syncing    |
| **Professional Tools** | ✅ JDBC/ODBC for analytics    | ❌ Limited professional tools     | ❌ Custom development needed |
| **Time to Market**     | ✅ Immediate                  | ❌ Days/Weeks                     | ❌ Months                    |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://heimdahl.gitbook.io/heimdahl.xyz/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.