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

# Team

### Built in production, not theory

The people behind Cestus have spent the last several years building across both AI and blockchain. Not in research papers. Not in pitch decks. In live environments, with real users, actual revenue, and production systems that break at 2 AM. We have taken products from zero to launch, scaled them to globally distributed user bases, and driven them to token listings and sustained revenue. We know what breaks at scale, what slows teams down, and what it actually takes to ship in web3.That experience is not decoration. It is why Cestus exists. Decentralized inference is not a theoretical problem. It is an infrastructure problem that demands people who have already solved hard coordination, scaling, and delivery challenges under real constraints.

***

### Mirza Begić - Founder

<figure><img src="https://1479099636-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKOOJr3ueC7QMWGB9MlPV%2Fuploads%2FkkLeoz4j7kUmNFHL6Mvd%2Fphoto_2026-05-15_16-08-17.jpg?alt=media&amp;token=85e3c17a-ac98-4a09-9fc3-6318f1724938" alt="" width="375"><figcaption></figcaption></figure>

Mirza has spent over a decade building and shipping AI-native products at startup speed without compromising quality, reliability, or user experience. His background sits at the intersection of enterprise software engineering and applied AI. Before Cestus, he led product development and quality engineering across HR platforms, ERP systems, and intelligent transportation infrastructure. The systems he built and oversaw are used by tens of thousands of users globally, handling real workloads under real latency and uptime constraints. What sets Mirza apart is his focus on context engineering and AI-driven software development. He does not treat models as black-box APIs to be called. He designs systems that extract maximum effectiveness from modern AI architectures by understanding how context, prompt structure, and inference pipelines interact with product requirements. That skillset is rare, and it is directly responsible for Cestus being built as a product-first platform rather than a raw compute marketplace. At Cestus, Mirza drives architecture, product direction, and the engineering culture that treats every decision as a trade-off between speed, correctness, and operator economics.

### Tarik Delić - Advisor

<figure><img src="https://1479099636-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKOOJr3ueC7QMWGB9MlPV%2Fuploads%2FrAT0sBRPbEcHWJaNDBP1%2FTarik.jpg?alt=media&amp;token=439fbd17-ea35-40a9-83c5-d63c965c03f8" alt=""><figcaption></figcaption></figure>

Tarik brings over twenty years of experience delivering business-based engineering solutions across telecoms, gaming, and digital sectors on a global scale. He co-founded OctaSpace, a decentralized compute network that scaled to 18,000+ active users and reached a $100 million all-time-high market capitalization. That is not advisory-board credibility. That is founder-level experience in taking a decentralized infrastructure project from concept to live network to liquid token, navigating the exact growth, governance, and operational challenges that Cestus will face as it expands. His background spans product management, technical program management, and enterprise delivery at scale. He understands how to align engineering output with market timing, how to structure token economies that incentivize long-term participation, and how to build teams that can execute under pressure .At Cestus, Tarik advises on network growth strategy, token economics, and the operational discipline required to scale a permissionless infrastructure project from early nodes to a globally distributed swarm.

***

### Why this team for this problem

Decentralized AI infrastructure has been attempted before. Most efforts fail not because the technology is impossible, but because the teams building them come from only one side of the problem. Pure AI researchers underestimate the coordination and incentive challenges of decentralized systems. Pure crypto builders underestimate the latency, reliability, and product-quality requirements of production inference. This team does not have that blind spot. Mirza brings the AI product and engineering depth. Tarik brings the decentralized network and token economics depth. Together, they represent the exact combination required to build an inference platform that developers actually want to use and operators actually want to run. That is the standard we hold ourselves to. Not whether the protocol works in a testnet. Whether a developer can switch from OpenAI to Cestus in one config change and never look back. Whether a GPU operator can run one Docker command and start earning the same day. That is what we are building. That is who we are.


---

# 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.cestus.network/project/team.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.
