# Architecture

### The Architecture of ZKUnity

Here is the architecture of ZKUnity:

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

### Components

As you can see in the above diagram, ZKUnity is composed of some components:

* Compiler
* zkServer
* Game engine SDKs

We supply integrated SDKs with Unity, Unreal, Bevy, React, and other game engine frameworks, therefore, game developers can use the tech stacks they feel familiar with.

Then, We use dedicated compilers to compile the core logic of the game code to zk code of ZKWasm, RiscZero, or other ZKVMs.

We use zkServer to encapsulate the zk bytecode part with the runtime part (e. g. C# runtime for a Unity game).

Here is the difference between the traditional way and the ZKUnity way:

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


---

# 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.bladedao.games/zkunity-game-engine/zkunity-guide/architecture.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.