Private Deployments
Replit’s Private Deployments feature allows you to control who can access your deployment without any code configuration. By making a deployment private, you ensure that only users with correct permission levels can view or interact with your deployed application. This is particularly useful for projects requiring restricted access, such as internal tools, beta applications, or sensitive projects.
Private deployments are only available to Teams subscribers
When you make a deployment private, visitors to your site will encounter a Replit login prompt. Only Replit users who are members of your Organization and logged in with their team credentials will be able to access the deployed site.
Enabling Private Deployments
When deploying your Replit App, you can choose between a Public or Private deployment. To make your deployment private, follow these steps:
- Navigate to the Deployment Settings: When you’re ready to deploy your Replit App, click on the Deploy button.
- Select Private Deployment: In the deployment settings, you will see a toggle to choose the deployment visibility. Select Private. Note that Scheduled Jobs are not able to be private because they do not allow incoming traffic.
- Deploy Your Replit App: Once you’ve set the desired permissions, proceed with the deployment. Only the users you specified will have access to view or interact with the deployed Replit App.
Updating Private Deployments
To enable or disable Private Deployments for an existing deployment, click “Edit commands and secrets”, toggle the setting on or off and redeploy.
Managing Access
Adding/Removing Users
After deploying your Replit App privately, you can manage access at any time. Users with Editor permissions (or greater) will be allowed to access the deployed application.
See Teams Identity and Access Management for more information on managing user permissions.
Considerations
- Website-Focused: Private deployments are primarily intended for websites and web applications. While APIs can be deployed privately, the login requirement makes them less practical for typical API use cases.
- Collaboration: Users with access to the private deployment must be logged into their Replit accounts to view or interact with the Replit App.
- Security: Always review and manage your access list to ensure only authorized users have access to your deployment.