Single Server

Posit Connect can be configured to run on a single server, without requiring any additional storage resources. The content data bundles are stored on the server, and the content processes run on the same server. This architecture is designed to provide a simple, cost-effective way to run Connect for small teams or organizations.

Architectural overview

This implementation of Posit Connect includes the following components:

Because a standalone instance of Connect includes both the published application data and the internal Connect SQLite database, we recommend following your organization’s backup and retention strategies to maintain snapshots of the EBS volume associated with this EC2 instance.

Architecture diagram

Architecture Diagram


This architecture utilizes a single EC2 instance running Posit Connect. During our performance tests, we used a t3.2xlarge instance running Ubuntu 22.04.

Refer to the Posit Connect Admin Guide for detailed information on system requirements and installation steps.


SQLite is the default database provider for Posit Connect and does not require any additional setup. You can find more information about SQLite in the Admin Guide.


The Connect team conducts smoke and performance testing on this architecture. During our testing, we published a Python-based FastAPI and a R-based Plumber application (using jumpstart examples included in the product) to Connect, simulating a load of 100 concurrent users.

Based on our performance test results, the system’s response times meet acceptable criteria for the majority of users. The system was able to handle the load without any issues, and the response times were within acceptable limits.

These tests demonstrate the capability of Connect to manage and serve applications to users. However, it is important to note that the computational footprint of the content used in testing was minimal. For most Connect installations, the majority of computational power is dedicated to the Python and R content that publisher-users deploy, rather than Connect itself. If your team is deploying lightweight apps, APIs, and jobs to Connect, our testing results are likely to be applicable. However, if your team is deploying APIs or apps that involve heavy-duty data processing, machine learning, or other computationally intensive tasks, you may want to consider one of our other architectures.