> ## Documentation Index
> Fetch the complete documentation index at: https://docs.actionx.top/llms.txt
> Use this file to discover all available pages before exploring further.

# System architecture

> Understand ActionX core services, data flow, and role-based entry points from a platform perspective.

This page focuses on system boundaries and data flow rather than code-level details. Think of it as the map of the whole ActionX platform.

```mermaid theme={null}
%%{init: {'flowchart': {'defaultRenderer': 'elk'}}}%%
flowchart TB
    entry["Entry layer<br/>Website<br/>Publisher dashboard<br/>SDK<br/>Backend API<br/>MCP"] --> ads["ads-server<br/>Intent<br/>Retrieval orchestration<br/>Ranking<br/>Tracking"]
    product["product-feed<br/>Semantic product retrieval"] --> ads
    partner["partner-stack-feed<br/>Program and entity retrieval"] --> ads
    ads --> data["data-center<br/>Analytics and observability"]
    ads --> finance["finance-center<br/>Statement, balance, withdrawal"]
    mcp["mcp-tool-server<br/>Remote MCP access"] --> ads
```

## Platform layers

<Columns cols={2}>
  <Card title="Access layer">
    The website, Publisher Dashboard, SDK, Backend API, and MCP are the main ways users enter ActionX.
  </Card>

  <Card title="Decision layer">
    Handles intent detection, retrieval orchestration, ranking, and result return.
  </Card>

  <Card title="Supply layer">Provides product and program supply that supports different commercial outcomes.</Card>
  <Card title="Data and settlement layer">Handles event ingestion, observability, financial management, and settlement.</Card>
</Columns>

## How data flows

* Requests enter through the access layer, then converge into `ads-server` for decisioning.
* During decisioning, the platform pulls candidates from product, affiliate, or SaaS program sources.
* Impression and click events are written into Redis Streams, then persisted by `data-center`.
* Settleable data ends up in `finance-center`, which powers statements and withdrawals in the publisher dashboard.

## Continue reading

<Columns cols={2}>
  <Card title="Platform capabilities" href="/overview/core-modules">
    See how the platform is organized across access, decisioning, observability, and settlement.
  </Card>

  <Card title="Publisher dashboard" href="/publishers/dashboard-overview">
    See how these services show up as user-facing capabilities in the dashboard.
  </Card>
</Columns>