Generic architectures for Posit Team

Posit Team combines Posit Workbench, Posit Connect, and Posit Package Manager into a data science platform. This page shows how the three products connect and deploy together.

To choose an architecture by answering a few questions about your environment, use the install planner.

For product-specific architectures, see:

How the products connect

Data science teams access Workbench through a browser to develop in Positron Pro, RStudio Pro, Jupyter, or VS Code. Workbench sessions install packages from Package Manager and publish content to Connect. When a user publishes from Workbench, the content bundle (code, data, and metadata) transfers directly to Connect. Stakeholders and decision makers access published data science content on Connect through a browser. Connect installs packages from Package Manager when building and running deployed content.

Conceptual diagram showing how Posit Team products connect. Data science teams access Workbench, which publishes to Connect. Viewers access content on Connect. Both Workbench and Connect install packages from Package Manager, which syncs metadata from the Posit Package Service.

Ports and data flows

In most production deployments, all services are exposed over HTTPS on port 443, either directly on the instance or through a reverse proxy or load balancer. For the default ports each product uses and outbound access requirements, see Networking.

Shared infrastructure

Each product operates independently and does not read from another product’s database. In multi-node deployments, the three products can share infrastructure such as an external PostgreSQL server, Network File System (NFS) shared storage, and an authentication provider such as LDAP, SAML, OpenID Connect (OIDC), or Pluggable Authentication Modules (PAM).

Resource Workbench Connect Package Manager Shared across products?
Linux server Dedicated Dedicated Dedicated No
Database Own database Own database Own database Defaults to SQLite; external PostgreSQL required for high availability. One PostgreSQL server can host all three, with a separate database per product.
Shared storage Home directories App data bundles Package files Not needed for single-server; required for high availability or multi-node deployments (NFS, or S3 for Package Manager)
Authentication PAM (password), LDAP, SAML, OIDC Password, LDAP, SAML, OIDC Token auth, OIDC (optional) Same provider recommended

Cross-product requirements

For individual product prerequisites, see Requirements for Posit professional products and Networking. The following requirements are specific to multi-product deployments:

Important

Skipping or misconfiguring these requirements can cause deployment failures, data access issues, or unsupported configurations that Posit cannot troubleshoot.

  • Install each product on a separate, dedicated server. Resource contention between products can cause session timeouts and failed deployments, and Posit does not support multi-product servers.
  • Workbench sessions and Connect processes require network access to Package Manager to install packages. Without this access, users cannot install packages during development, and deployed content cannot rebuild its dependencies.

Deployment options

Posit Team supports three deployment options. Choose one based on your availability requirements and infrastructure:

  • Single servers deploy each product on its own dedicated server with no shared storage or external database.
  • Load-balanced clusters run two or more servers per product behind a load balancer for high availability and additional capacity.
  • Kubernetes runs all three products in a shared cluster using Posit-maintained Helm charts.

Posit Team on single servers

In this architecture, each product runs on a dedicated Linux server. The single-server deployment does not require shared storage or an external database.

Architecture diagram of Posit Team deployed on single servers. Each product runs on a dedicated server: Workbench Server with IDE sessions, Connect Server with supported applications, and Package Manager Server. Package Manager syncs packages from the Posit Package Service.

Posit Team on load-balanced clusters

In this architecture, each product runs on two or more servers behind a load balancer for high availability and additional capacity.

Additional requirements

  • User home directories (Workbench), application data (Connect), and package files (Package Manager) must each reside on separate shared storage, typically NFS or S3 for Package Manager.
  • Each product must use an external PostgreSQL database. You can host all databases on the same PostgreSQL server with separate databases per product.

Architecture diagram of Posit Team deployed on load-balanced clusters. Each product runs on two servers behind a load balancer. Shared infrastructure includes a PostgreSQL database and three NFS mounts for home directories, application data, and package files. Package Manager syncs packages from the Posit Package Service.

Posit Team on Kubernetes

In this architecture, each product runs in a Kubernetes cluster using Posit-maintained Helm charts. Products can share a cluster and ingress controller, with each product in its own deployment.

Additional requirements

  • Each product requires shared storage through persistent volume claims.
  • Each product must use an external PostgreSQL database, inside or outside the cluster. You can host all databases on the same PostgreSQL server with separate databases per product.

Architecture diagram of Posit Team deployed in a Kubernetes cluster. An ingress controller routes traffic to Workbench with Launcher, Connect with Launcher, and Package Manager. External PostgreSQL and shared storage provide persistent data. Package Manager syncs packages from the Posit Package Service.

Next steps

After deploying the products, configure them to work together. See Configure Posit professional products to work together for integration instructions.

Back to top