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

# Architecture

The Sling Data Platform consists of three main components that work together to provide a scalable and secure data movement solution:

1. Control Server & Database
2. Agents (Self-hosted)
3. Frontend UI

## System Overview

![Sling Platform Architecture](https://3453272330-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M93cpHl7B7NPZlDrubS%2Fuploads%2Fgit-blob-9e8f30ab5666515edb23e357755204f17a0836bc%2Fsling-platform-architecture.png?alt=media)

### Control Plane

The Control Plane is the central coordination point of the Sling Platform that:

* Manages user authentication and authorization
* Stores configuration data (connections, replications, etc.)
* Coordinates job scheduling and execution
* Maintains system state and job history
* Communicates with agents via secure NATS websockets
* Provides REST API endpoints for the frontend UI

### Agents

Agents are distributed workers that:

* Run the Sling CLI to execute data jobs
* Operate within your infrastructure for secure data access
* Connect to the Control Server via secure NATS websockets
* Can be deployed across multiple environments (dev, prod, etc.)
* Scale horizontally to handle increased workload
* Provide secure access to data sources without exposing credentials

### Frontend UI

The Frontend UI provides:

* Web-based interface for managing Sling operations
* Secure communication with Control Server via HTTPS
* Visual workflow creation and management
* Real-time monitoring and alerting
* Team collaboration features
* Connection management interface

## Communication Flow

1. Users interact with the Frontend UI over HTTPS
2. Frontend UI communicates with Control Server via REST API
3. Control Server coordinates with Agents using NATS secure websockets
4. Agents execute jobs and report status back to Control Server
5. Control Server updates Frontend UI with job status and results

## Security

* All communication between components uses encryption (HTTPS, WSS)
* Agents run in your infrastructure, keeping sensitive data and credentials secure. No ports need to be opened.
* Authentication and authorization managed by Control Server
* Credentials stored securely in Control Server database, or on your self-hosted agent.


---

# 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.slingdata.io/sling-platform/platform/architecture.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.