# Check supported systems

Check this page before you roll Blink out, so nobody finds out mid-call that a computer is not supported.

## Computers you support

| | Support tool (one-off sessions) | Access agent (unattended) |
|---|---|---|
| **Windows** 10 or later, 64-bit (x64) | Yes | Yes |
| **macOS** 12.3 or later, Apple silicon or Intel | Yes | Not available |
| **Linux** | No | No |
| **iPhone, iPad, Android, ChromeOS** | No | No |

- **Support** is for a session with someone sitting at the computer: they enter a code on your Blink address and run the support tool. Nothing stays installed. See [Run the support tool](/install/support-tool/).
- **Access** is for computers you reach when nobody is there. The Access agent installs as a Windows service and stays connected. See [Install the Access agent on Windows](/install/access-agent-windows/).

:::note[Mac]
On a Mac, Blink runs Support sessions only. The Mac needs two privacy permissions before you can see and control it: see [Allow Blink on a Mac](/install/mac-permissions/).
:::

:::caution[iPad, phones and Linux]
An iPad that opens your Blink address is told to use a Mac or a Windows PC instead. There is no Blink app for phones, tablets or Linux.
:::

:::note[Phone camera with Blink View]
With the Blink View add-on, a customer can show you their phone camera during a session from the phone's web browser, with no app to install. Use Safari on an iPhone or iPad, or Chrome on Android; other browsers may work. See [See the customer's phone camera with Blink View](/use/blink-view/).
:::

## Technicians

Technicians work in a web browser: they sign in to the console at your Blink address and view sessions in a browser tab. There is nothing to install on the technician's computer.

## Your own server

On Blink Cloud, IZT runs the server and there is nothing to check here. On premises, Blink needs a dedicated server running Debian 13 (x64), from 2 vCPU, 4 GB of memory and 64 GB of SSD storage, plus space for recordings. See [Server requirements](/install/on-premises-server/#server-requirements).

## Network

Every Blink connection starts from the computer you support. Nothing needs to reach in to that computer, so you do not open any inbound ports at the customer's site.

- **Required:** the computer reaches your Blink address over HTTPS (TCP port 443).
- **Recommended:** it can also reach the server's media and relay ports, which gives the smoothest picture. When only HTTPS gets through, the Access agent and the support tool still relay their connection over port 443.

For Blink View, the customer's phone must reach your Blink address over HTTPS from wherever it is, usually mobile data or a guest network. A server activated online creates Blink View codes over its existing connection to `build.blink.izt.app` (443/TCP), the same one it uses for online activation; there is nothing extra to open.

If you run your own server, the ports to open on the server side are listed in [Install Blink on your own server](/install/on-premises-server/#open-the-ports).