> For the complete documentation index, see [llms.txt](https://docs.biscit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.biscit.com/ekr-user-guide/getting-started/ekr-network-diagram.md).

# EKR Network Diagram

This diagram illustrates the integration flow between an end user, the EKR system hosted in the BISCIT Azure Tenant, and the customer's Epicor Kinetic environment.

**Key Components**

1. **User Access:** The EKR User connects to the web-based EKR Frontend via a browser using a secure HTTPS connection.
2. **BISCIT Azure Tenant:**

* The EKR Frontend relays requests to the EKR Backend over HTTPS.
* Both the Frontend and Backend components stream real-time operational telemetry into a central Monitoring & Diagnostics module for tracking system health and diagnostics.

3. **Customer Kinetic Instance:**

* The EKR Backend communicates securely with the customer's Epicor Kinetic APIs using HTTPS REST API calls authenticated with Bearer Tokens.
* The Epicor Kinetic APIs handle data operations directly with the underlying Epicor Kinetic Database.

<pre class="language-mermaid"><code class="lang-mermaid"><strong>graph TB
</strong>    %% Users
    subgraph User["👤 EKR User's Network&#x3C;br/>"]
        EKRSPA["EKR SPA"]
    end

    %% RMS Cloud
    subgraph RMS["☁️ EKR (Hosted in BISCIT Azure Tenant)"]
        HostedSPA["EKR Hosted SPA"]
        Backend["EKR APIs"]
        Monitoring["Monitoring &#x26;&#x3C;br/>Diagnostics"]
    end

    %% Customer
    subgraph Customer["🏢 Customer's Kinetic Instance 
    (dependant on if on prem or cloud)"]
        Spacer[" "]
        EpicorAPI["Epicor Kinetic APIs"]
        EpicorDB[("Epicor Kinetic Database")]
        
    end

    %% Connections
    HostedSPA -->|"Downloads"| EKRSPA
    EKRSPA -->|"HTTPS"| Backend
    Backend -->|"HTTPS REST API&#x3C;br/>(Bearer Token)"| EpicorAPI
    Backend -.->|"Telemetry"| Monitoring
    EKRSPA -.->|"Telemetry"| Monitoring
    EpicorAPI --> EpicorDB
    Spacer ~~~ EpicorAPI

    %% Styling
    classDef azure fill:#DCEEFF,stroke:#4A90E2,stroke-width:2px
    classDef customer fill:#DFF5E1,stroke:#5cb85c,stroke-width:2px
    classDef user fill:#F1F3F4,stroke:#9aa0a6,stroke-width:2px
    classDef hidden fill:none,stroke:none,color:transparent

    class RMS azure
    class Customer customer
    class User user
    class Spacer hidden
</code></pre>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.biscit.com/ekr-user-guide/getting-started/ekr-network-diagram.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
