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

# Condense Architecture

{% hint style="info" %}
**First Time User? Free Credits on us!**

Get up to $200 worth of Free credits when you sign up for the first time. Use this link to create a new account on Condense and claim your free credits!

[<mark style="background-color:purple;">https://www.zeliot.in/try-now</mark>](https://www.zeliot.in/try-now)
{% endhint %}

Condense leverages a robust and secure architecture to facilitate efficient data ingestion.\
This section analyses the key components of the system and their interactions.

## Condense Architecture - Microsoft Azure

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

## Condense Architecture - Amazon Web Services (AWS)

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

## Condense Architecture - Google Cloud Platform (GCP)

<figure><img src="/files/4OjeFwcuyqIqVnkJFkFm" alt=""><figcaption></figcaption></figure>

## Architecture Components

Condense employs a three-tier architecture, ensuring clear separation of concerns and promoting efficient communication between components:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><h3><strong>Cloud Provider</strong></h3></td><td>The cloud marketplace (e.g., Azure, AWS and GCP) serves as the platform for deploying Condense. Users access Condense through the provider's interface.</td><td><a href="/files/ghmQexMt4w7qLKxczK1Y">/files/ghmQexMt4w7qLKxczK1Y</a></td></tr><tr><td><h3>Zeliot Central Tower</h3></td><td>This central hub manages deployments, user authentication, release updates, and monitors the overall health of Condense instances.</td><td><a href="/files/G3jrTEeHDcnwmOiS2qKc">/files/G3jrTEeHDcnwmOiS2qKc</a></td></tr><tr><td><h3>Condense Application</h3></td><td>Deployed within the user's cloud environment, this application processes data from mobility devices, performs transformations, and sends it to designated outputs.</td><td><a href="/files/0BI1ozOnM4WltsTWoKYj">/files/0BI1ozOnM4WltsTWoKYj</a></td></tr></tbody></table>


---

# 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.zeliot.in/condense/introduction-to-condense/condense-architecture.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.
