# App Types (Overview)

<details>

<summary>In Progress</summary>

This page is currently under active development. Content may be incomplete, evolving, or placeholder-only. Please check back later for finalized documentation and fully structured examples.

</details>

[GLIK Cloud](/glik-cloud.md) supports multiple app types, each optimized for specific orchestration needs. Whether building lightweight assistants, autonomous agents, or complex enterprise flows with persistent memory, GLIK provides flexible [app types](/app-types/overview.md) that align with a wide range of enterprise use cases.

This guide introduces each app type available in **GLIK Cloud** and outlines when to use them in the context of a managed, browser-based environment.

{% embed url="<https://www.mermaidchart.com/raw/21d5603e-7b4d-41bb-b3d2-82bfd2af9ab2?theme=light&version=v0.1&format=svg>" %}
How different apps rely on a structured combination of uploaded documents, memory modules, and policy logic to function. Each agent pulls from a configurable set of requirements — enabling modular deployment across enterprise domains.
{% endembed %}

### App Type Comparison

| App Type                                         | Description                                                                   | Best For                                           |
| ------------------------------------------------ | ----------------------------------------------------------------------------- | -------------------------------------------------- |
| [**Chatbot**](/app-types/chatbot.md)             | Simple, prompt-response interaction. No persistent memory.                    | Quick utilities, testing, FAQ bots                 |
| [**Agent**](/app-types/agent.md)                 | Autonomous agent with reasoning and tool invocation capabilities.             | Self-driven tasks, decision routing                |
| [**Advanced Chat**](/app-types/advanced-chat.md) | Multi-turn memory-enabled dialog with structured memory and escalation logic. | Internal workflows, document agents, approval bots |
| [**Workflow**](/app-types/workflow.md)           | Single-turn orchestration for automated API chains or tool calls.             | ETL-style logic, external automation               |

### Design Philosophy

Each app type runs on the same orchestration engine but is optimized for different levels of:

* **Session duration** (single turn vs. multi-turn)
* **Memory access** (stateless vs. scoped persistence)
* **Tool coordination** (LLM-only vs. hybrid with plugin calls)
* **Enterprise readiness** (compliance, logging, fallback paths)

### Choosing the Right App Type

* Use [**Chatbot** ](/app-types/chatbot.md)for basic assistants with no memory or tool logic
* Use [**Agent** ](/app-types/agent.md)when tools, autonomous execution, or goal-seeking behavior is required
* Use [**Advanced Chat**](/app-types/advanced-chat.md) to manage conversational memory, approvals, or fallback escalation
* Use [**Workflow** ](/app-types/workflow.md)to streamline deterministic pipelines (e.g., extract → transform → export)

### Other Deployment Environments

While this page focuses specifically on app types as they appear in **GLIK Cloud**, these same app types are available in other environments such as **GLIK Open Core**. Behavioral differences, configuration options, and deployment patterns for each app type within Open Core will be covered in that section of the documentation.

Refer to [GLIK Open Core > App Types](/developers/glik-open-core.md) for self-hosted implementation guidance.


---

# 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.glik.ai/glik-cloud/app-types-overview.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.