> For the complete documentation index, see [llms.txt](https://wiki.datadike.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.datadike.com/en/administration/assets/platforms.md). # Platforms A platform is the **technical model of an asset**. It tells the solution what technology it is dealing with and, from that, which access protocols are available, on which ports, whether the connection may pass through a gateway, and whether switching accounts after login is allowed. Every registered asset belongs to a platform. It is the platform that knows a Windows server can be reached over RDP on 3389 and WinRM on 5985, while an Oracle database is reached over the `oracle` protocol on 1521. ## How the list is organized Platforms appear as **cards grouped by category**, each group under a collapsible header showing the category name and how many platforms it holds — `HOST 8`, for example. Each card shows: * the platform **name** and a badge with its **type** (`LINUX`, `UNIX`, `WINDOWS`) * the enabled **protocols**, each with its default port (`SSH: 22`, `RDP: 3389`) * **DEVICES** — how many assets use that platform * the **BUILT-IN** badge, when the platform ships with the product Built-in platforms can only be **duplicated**. Platforms you create also show edit and delete icons. ## The details pane Selecting a platform opens a pane on the right with the name, the protocols as badges, a **Sync protocols to assets** button, and four tabs: | Tab | Contents | | --------------- | ----------------------------------------- | | **Detail** | The *Quick update* and *Protocols* blocks | | **Devices** | Assets using this platform | | **Automations** | Automations that apply to it | | **Activities** | Change history | **Quick update** holds the three most-used settings: | Setting | What it does | | ------------------------ | --------------------------------------------------------------------------- | | Gateway enabled | Allows connections to this platform to pass through a gateway | | Enabled su | Allows switching accounts after login — elevating to `root`, for example | | Sync protocols to assets | Pushes the protocol configuration to every asset already using the platform | The **Protocols** block lists each protocol with its port, which can be changed, and opens advanced settings from the **...** menu. {% hint style="warning" %} The port set here is the **default inherited** by assets of that platform. Changing it does not affect assets already registered until you use **Sync protocols to assets**. {% endhint %} ## Built-in platforms ### Host Physical and virtual servers. The largest category, because it covers three operating-system families. | Platform | Type | Default protocols | When to use it | | ----------------- | ------- | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | | **Linux** | Linux | SSH 22 · SFTP 22 · TELNET 23 · VNC 5900 · RDP 3389 | Linux distributions in general. The most used platform in a typical environment | | **Gateway** | Linux | SSH 22 · SFTP 22 · TELNET 23 · VNC 5900 · RDP 3389 | Machines acting as jump hosts. Same base as Linux, kept separate so the host's role is clear in the inventory | | **Unix** | Unix | SSH 22 · TELNET 23 · VNC 5900 · RDP 3389 | Generic Unix systems | | **AIX** | Unix | SSH 22 · TELNET 23 · VNC 5900 · RDP 3389 | IBM Unix, common in large environments | | **BSD** | Unix | SSH 22 · TELNET 23 · VNC 5900 · RDP 3389 | FreeBSD, OpenBSD, and derivatives | | **macOS** | Unix | SSH 22 · TELNET 23 · VNC 5900 · RDP 3389 | macOS workstations and servers | | **Windows** | Windows | RDP 3389 · WinRM 5985 · SSH 22 · VNC 5900 | Windows servers and workstations. RDP serves graphical access, WinRM serves automations | | **Windows-RDP** | Windows | RDP 3389 · WinRM 5985 · SSH 22 · VNC 5900 | For hosts that require classic RDP negotiation, without TLS | | **Windows-TLS** | Windows | RDP 3389 · WinRM 5985 · SSH 22 · VNC 5900 | For hosts that require RDP over TLS | | **RemoteAppHost** | Windows | RDP 3389 · WinRM 5985 · SSH 22 | The host that publishes remote applications. It runs the applets; it is not an ordinary access target | | **Other** | Other | SSH 22 · SFTP 22 · TELNET 23 · VNC 5900 · RDP 3389 | Hosts that fit none of the families above | {% hint style="info" %} The three Windows variants exist because RDP security negotiation differs between server versions and configurations. When a graphical connection fails during negotiation, switching the asset between **Windows**, **Windows-RDP**, and **Windows-TLS** is the first thing to try. {% endhint %} ### Database Databases reached through the web console or a native client. | Platform | Default protocol | Note | | -------------- | ---------------- | -------------------------------------------------------- | | **Oracle** | oracle 1521 | | | **MySQL** | mysql 3306 | | | **MariaDB** | mariadb 3306 | A MySQL fork, treated as its own platform | | **PostgreSQL** | postgresql 5432 | | | **SQLServer** | sqlserver 1433 | Microsoft SQL Server | | **MongoDB** | mongodb 27017 | Document database | | **Redis** | redis 6379 | Versions before 6 | | **Redis6+** | redis 6379 | Version 6 and later, which have their own users and ACLs | | **ClickHouse** | clickhouse 9000 | Columnar analytical database | | **DB2** | db2 50000 | IBM Db2 | | **Dameng** | dameng 5236 | DM database | {% hint style="info" %} **Redis** and **Redis6+** are separate because Redis gained per-user authentication in version 6. Choosing the wrong one prevents login with a named credential. {% endhint %} ### Device Network equipment, reached by command line. All use **SSH 22** and **TELNET 23**. | Platform | When to use it | | ------------ | ---------------------------------------------------------- | | **General** | A generic network device, when no specific platform exists | | **Cisco** | Cisco equipment | | **Huawei** | Huawei equipment | | **H3C** | H3C equipment | | **Fortinet** | Fortinet appliances | The difference between them is terminal handling and command recognition, which affects command auditing and command inspection for each vendor. ### Cloud | Platform | Default protocol | When to use it | | ------------------ | ---------------- | -------------------------------------------------------------- | | **Kubernetes** | k8s 443 | Kubernetes clusters, with panel access through the web console | | **Vmware-vSphere** | http 80 | VMware vSphere virtualization | ### Web | Platform | Default protocol | When to use it | | ----------- | ---------------- | ----------------------------------------------------------------------------------- | | **Website** | http 80 | Web applications opened in the browser with the credential injected by the solution | ### GPT | Platform | Default protocol | When to use it | | ----------- | ---------------- | ----------------------------------------- | | **ChatGPT** | chatgpt 443 | Audited access to a generative AI service | ## Custom platforms When no built-in platform fits, create one with **Create**, or duplicate an existing platform, which keeps its protocol configuration as a starting point. Custom platforms are identified by the **absence of the BUILT-IN badge** and can be edited and deleted freely. Duplicating a built-in platform is the recommended path when you only need to adjust ports or disable a protocol while keeping the rest of the behavior. ## Related pages * [Core concepts](/en/get-started/core-concepts.md) — how platforms relate to assets and accounts * [Asset inventory](/en/administration/assets/inventory.md) * [Connection methods](/en/administration/sessions/connection-methods.md)