# Architecture

Glacis is a pure on-chain protocol, that means that all its components are Smart Contracts, these components can be aggregated in two groups:

* **Infrastructure Components**: Maintained by Glacis and deployed on each supported chain.
  * Router
  * Adapters
  * Mediators
* **Client Components**: Maintained by Glacis,accessible as package and deployed by user through the use of inheritance on his own contracts.
  * Clients

> All components have different behavior depending if they act as a source chain component or a destination chain component.

## Component diagram

This diagram represents the complete flow between components in Glacis Architecture.

![](/files/1uBv9sIETBKnPIqJqUWd)


---

# 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.glacislabs.com/glacis-core/concepts/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.