Requirements

This page lists the requirements for Posit Connect. The requirements in Requirements for all deployments apply to every installation. In Requirements for your deployment type, select how you install Connect to see the extra requirements for that deployment.

Requirements for all deployments

These requirements apply to every Posit Connect installation.

ImportantDedicated server required

Install Posit Connect on its own dedicated server. Do not put Connect on the same machine as other Posit products (Posit Workbench, Posit Package Manager). Each product needs its own server for production deployments.

Run Posit Connect on a server with a minimum of:

  • 16 GB of RAM
  • 100+ GB of disk storage
Note

Connect can need more than 16 GB of RAM and 100+ GB of disk space. The amount depends on the resource usage of your content. See Sizing and capacity planning to size your server.

Set both Server.DataDir and Server.TempDir to locations that permit execution of binary files. If either location uses the noexec mount option, you cannot deploy or run content on Connect. For more information about the noexec option, see the Linux mount man page.

ImportantPosit Team installation order

If you use Posit Package Manager as the package repository for Connect (the typical Posit Team setup), install and configure Package Manager first. Connect then uses Package Manager to resolve and install R and Python packages. See Posit Team installation order. For a detailed installation guide for Posit Team, see the Posit Team install planner.

Linux support

Posit Connect is supported on the following Linux distributions:

  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9
  • Red Hat Enterprise Linux 10
  • SUSE Linux Enterprise Server 15 SP6, SP7, or openSUSE 15.6
  • Ubuntu 22.04 (Jammy Jellyfish)
  • Ubuntu 24.04 (Noble Numbat)
  • Ubuntu 26.04 (Resolute Raccoon)
  • Debian 13
NoteRHEL Alternatives

There are multiple distribution options, such as Rocky Linux and AlmaLinux, which state they are 1:1 binary compatible with RHEL. These distributions can be used as long as they stay 1:1 binary compatible with RHEL. CentOS Stream is not a 1:1 binary compatible distribution and not supported by Posit.

Within each version of a Linux distribution, Posit supports the latest patch release or “service pack.” The Posit Platform Support page explains the support period for each Linux distribution.

Installers are available for the x86-64 architecture on all supported Linux distributions. ARM64 (aarch64) installers are available for Ubuntu 24.04, Ubuntu 26.04, and Red Hat Enterprise Linux 10. Installation requires root privileges. Most environments also require root privileges to run Connect.

Runtime support

Posit Connect is supported with the following runtimes:

Browser support

Posit Connect is supported against the latest versions of the following browsers:

  • Chrome
  • Firefox
  • Safari
  • Microsoft Edge
ImportantInternet Explorer 11 - End of Support

Internet Explorer 11 is no longer supported by Posit server products. For more information, see Platform Support.

Requirements for your deployment type

Select your deployment type to see the extra requirements for it. The requirements for all deployments also apply.

A single-server installation runs the Connect service and all published content on one host. The requirements for all deployments cover this deployment. Also plan for the following:

  • SELinux in permissive mode during installation (sudo setenforce 0).

Next: Server installation.

A multi-server installation runs the same version of Connect on more than one node behind a load balancer. All nodes share one database and one data directory for high availability (HA). In addition to the requirements for all deployments, you need:

  • SELinux in permissive mode during installation (sudo setenforce 0).
  • The same version of Connect on each node.
  • A shared PostgreSQL database. All nodes must use the same database.
  • A shared data directory on POSIX-compliant storage, such as NFS or EFS. Set Server.DataDir to the same shared location on each node. Keep the UID and GID of the content-execution accounts the same on every node, because shared file systems enforce permissions by numeric ID.
  • A load balancer that supports session affinity (also called sticky sessions, which sends each user to the same node) and WebSocket connections.
  • Synchronized clocks on all nodes, for example with ntp.

Next: Multi-server installation and High Availability and Load Balancing.

Off-host execution runs published content in containers on a Kubernetes cluster, isolated from the Connect service. In addition to the requirements for all deployments, you need:

  • A Posit Connect license that permits off-host execution.
  • Working knowledge of Kubernetes and Helm.
  • A running Kubernetes cluster and API access to it.
  • kubectl, the Kubernetes command-line tool.
  • Helm v3, the Kubernetes package manager.
  • A PostgreSQL database.
  • A StorageClass backed by POSIX-compliant PersistentVolume storage that supports symlinks and ReadWriteMany access.
  • At least 100 GB of shared storage.

Next: Off-host execution installation.