> For the complete documentation index, see [llms.txt](https://docs.realis.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realis.network/true-story.md).

# True Story

Realis started in 2017 with a small game studio.&#x20;

Our first 2 games were a failure, and the founder even had to sell his only apartment to pay the developers' salaries. He lived and worked with the team in a small office in Kharkiv, where everything started. And this is by the way his bed in those days 😄

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

In April 2019 we released our first successful game **Crypto Cats**. And then **Crypto Dragons** in September 2020.

In 2021, the downloads grew by 25 times. Now we have 7 successful games and an audience of 3.6 million users worldwide. We are actively growing and moving towards our goals. Join our journey and become a part of Realis family.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.realis.network/true-story.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
