# KEPLER

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

### Welcome to KEPLER

We give developers the tools they need to launch and scale dApps without spending time managing nodes, renting oversized servers, or setting up backend services from scratch.

KEPLER provides reliable access to blockchain data through private APIs, event streams, and managed nodes, allowing developers to build faster and scale without worrying about infrastructure maintenance.

Kepler powers all major Project X products — from **Saturn** (real-time token and NFT event engine) and **Atlas** (wallet analytics) to the **Project X Validator** and internal DAO systems — and is now available for everyone.

***

### What Kepler Does

Kepler abstracts the complexity of running and maintaining MultiversX observers, gateways, and indexers. It provides a single, unified interface for querying, subscribing, and delivering blockchain data in real time.

* **Private APIs** — fast and reliable endpoints for accounts, transactions, tokens, and NFTs.
* **Custom APIs** — tailored endpoints designed for specific business needs, optimized for each use case while maintaining performance and consistency.
* **ElasticSearch indexing** — optimized data search and filtering at scale.
* **Event Streams** — real-time push of token swaps, NFT sales, and transfers.
* **Dedicated nodes** — private, high-availability gateways for production use cases.
* **Webhooks** — secure and signed event delivery to your backend.

***

### Why Builders Use Kepler

Developers choose Kepler when they need:

* **Speed and reliability** beyond public gateways.
* **Simplified integration** without running their own nodes.
* **Consistent data** indexed and normalized for analytics or monitoring.
* **Event-driven infrastructure** to react to on-chain activity instantly.
* **Scalability** without additional infra or DevOps overhead.

By using Kepler, you can focus entirely on your application logic while Kepler manages uptime, redundancy, and data pipelines underneath.

***

### How It Works

Kepler runs a distributed pool of observers and gateways that continuously sync blockchain data.\
Events are decoded, enriched, and indexed in real time, then exposed to builders.

Each project receives its own **API key** and isolated rate limits.\
Requests are authenticated via header (`Api-Key`) or URL query param (`Api-Key`) and served at minimum latency.

***

### Mainnet and Devnet Access

Kepler maintains separate environments:

* **Mainnet** — for production integrations.
* **Devnet** — for testing and development.

Both environments expose identical endpoints.

***

### Plans and Access

Kepler offers three plans:

* **Developer** — for individual builders testing or prototyping.
* **Business** — for projects in active production.
* **Custom / Enterprise** — for organizations needing dedicated nodes or SLAs.

All plans include private endpoints, access to Mainnet + Devnet, and full community support through the Project X channels.

***

### Support and Community

The Project X team maintains an active builder community.

For help and enterprise onboarding DM the team on [**Discord**](https://discord.com/invite/project-x-dao-1047509567858299000) or [**Telegram**](https://t.me/ProjectX_DAO).

***

### The Vision

KEPLER is part of a decentralized, community-owned infrastructure network.

Every plan contributes back to the Project X DAO, ensuring that the tools builders rely on are maintained by the very ecosystem they help grow.

Fast. Reliable. Community-powered.\
Welcome to Kepler.


---

# 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://docs.projectx.mx/products/kepler.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.