# Gateway Architecture

Source: /docs/gateway-architecture

Architecture guide for a customer-hosted Raptor MCP Gateway inside an organization's approved domain and connected to customer-approved Qlik environments.

## Overview

Raptor MCP Gateway is the controlled bridge between an organization's approved AI tooling and its customer-approved Qlik access.

This view is intentionally limited to the organization's domain and security boundary.

## Architecture diagram

```mermaid
flowchart LR
  subgraph ORG["Organization domain / security boundary"]
    USER["Customer user"]
    AI["Customer AI / IDE / LLM"]
    SECURITY["Identity, network and security controls"]
    CREDS["Customer Qlik access credentials / service account / OAuth"]
    subgraph GATEWAY["Customer-hosted Raptor MCP Gateway"]
      HTTP["Streamable HTTP Gateway"]
      TOKEN["Access key / token validation"]
      POLICY["Policy / entitlement check"]
      ROUTING["MCP tool routing"]
      CONNECTOR["Qlik connector layer"]
      LOGS["Audit / event logging"]
    end
    OPSSEC["Customer logging, monitoring and incident response"]
  end

  subgraph QLIK["Customer-approved Qlik environment"]
    QCLOUD["Qlik Cloud"]
    QSEOW["Qlik Sense Client-Managed / QSEoW"]
    APPS["Qlik apps"]
    DATA["Qlik data connections"]
    OPS["Automation, migration and metadata operations"]
  end

  USER --> AI
  AI --> SECURITY
  SECURITY --> HTTP
  CREDS --> CONNECTOR
  HTTP --> ROUTING
  HTTP --> TOKEN
  TOKEN --> POLICY
  POLICY --> ROUTING
  ROUTING --> CONNECTOR
  ROUTING --> LOGS
  LOGS --> OPSSEC

  CONNECTOR --> QCLOUD
  CONNECTOR --> QSEOW
  QCLOUD --> APPS
  QSEOW --> APPS
  APPS --> DATA
  APPS --> OPS
```

[Download SVG diagram](/docs/raptor-mcp-organization-architecture.svg)
[Download PNG diagram](/docs/raptor-mcp-organization-architecture.png)

The diagram shows the organization's users, AI environment, security controls, customer-hosted Raptor MCP Gateway runtime, Qlik credentials, audit/event logging, and approved Qlik endpoints.

## Customer-hosted gateway

Customers may run the Raptor MCP Gateway inside their own approved infrastructure. In this model, the customer controls network access, Qlik connectivity, credentials, AI tooling, logging, monitoring and security policies.

## Security and data boundaries

Security ownership stays aligned to the selected gateway route and the customer's approved Qlik access model.

- Customer AI/LLM remains in the customer's chosen environment.
- Customer controls Qlik credentials and access rights.
- Gateway access is entitlement-controlled.
- Audit/event logging routes to the organization's approved logging, monitoring and incident response process.
- Any customer-provided content or evidence is processed only under the applicable approved process, terms and privacy notices.

## Qlik connectivity

The gateway connects to Qlik using the customer-approved Qlik access method, such as Qlik Cloud API/OAuth/service account configuration or Qlik Sense Client-Managed/QSEoW connectivity. Access must be configured and approved by the customer.

Qlik Cloud, Qlik Sense and related marks are trademarks of QlikTech International AB or its affiliates. Raptor MCP is an independent Modern Management gateway-access platform and is not owned, operated, endorsed or sponsored by Qlik.

## Customer AI / BYO AI model

Raptor MCP does not require customers to move their AI tooling into Modern Management infrastructure. Customers may use their own AI, IDE or LLM environment, subject to their own security, cost and governance controls.

## Gateway operations

Gateway operations should follow the organization's normal controls for service hosting, secret management, network allowlists, log retention, monitoring, incident response, change management, and access review.

## Commercial portal dependencies

The commercial portal is outside the runtime architecture diagram. It is still required for payment/subscription administration, gateway deployment package download, and the administrative setup needed to manage users within the gateway for on-premises or cloud-hosted gateway routes.

Runtime AI-to-gateway and gateway-to-Qlik traffic remains governed by the configured gateway route, customer-approved Qlik permissions, and the organization's security controls.

- Payment and subscription status for the Raptor MCP gateway entitlement.
- Download access for the gateway deployment package and approved supporting materials.
- Administrative user setup for gateway access when the gateway is customer-hosted on-premises or cloud-hosted.

## Setup prerequisites

Prepare these items before connecting a production Qlik environment through Raptor MCP Gateway.

- Approved customer-hosted gateway route.
- Qlik Cloud or Qlik Sense Client-Managed / QSEoW environment.
- Customer-approved Qlik access credentials / OAuth / service account.
- Customer AI / IDE / LLM environment.
- Network access from gateway to Qlik endpoint.
- Approved secret store for Qlik credentials and gateway access keys.
- Approved logging, monitoring and incident response process.

## FAQs

Does Raptor MCP host my AI? No. Customers may use their own approved AI, IDE or LLM environment. Raptor MCP provides governed gateway access to Qlik workflows.

Does Raptor MCP store my Qlik production data? Customer Qlik data access is controlled by the customer-approved gateway and Qlik permissions.

Can the gateway run in my environment? Yes. Customers may run a customer-hosted gateway where they have suitable infrastructure and security approvals.

## Related Links

- [Raptor MCP](/docs/raptor-mcp)
- [Hosted gateway access](/docs/raptor-mcp/hosted-gateway-access)
- [Enterprise gateway](/docs/raptor-mcp/enterprise-gateway)
- [Install and configure](/docs/raptor-mcp/install-and-configure)
- [Raptor technical perspective](https://raptorbi.ai/technical-perspective) - Background technical perspective for Qlik delivery context; this gateway architecture page is the current authority for Raptor MCP access.