Replit Publishing
Replit puts your application into operation under your domain, public or for your team only.
Portals grow with demand, websites are served statically, reports run on a schedule. Who may access it and how operation is monitored we settle before the first publication.
For teams with an accepted application that they want to run publicly or internally only, with monitoring in place.
- Autoscale
- Static
- Reserved VM
- Scheduled
- Private Deployments
- Monitoring Agent

One click to operation
The order portal for dealers has been accepted. One click publishes it under portal.your-company.ch; compute grows with the Monday morning rush and shrinks at night. Only signed-in members of your workspace see the internal tool next to it, and a report starts at the same time every morning. If something fails, monitoring reports it before the first dealers call.
How we publish applications
For each application we choose the kind of publishing that fits its load. Examples:
- Portals and APIs with AutoscaleCapacity follows usage and drops to zero in quiet times.Result: you pay for the load that actually occurs.
- Websites with StaticPages without server logic, served fast under your domain.Result: a website with hardly any running costs.
- Always-on services on a Reserved VMBots, real-time connections and services that must always be reachable, on a machine with fixed capacity.Result: reliable response times at predictable costs.
- Scheduled runsImports, reconciliations and reports start at set times.Result: recurring work gets done at the set time, and compute runs only while it is needed.
- Access and monitoringPublic, password protected, workspace only or invite only, plus health checks, alerts and the Monitoring Agent if you wish.Result: only the right people see the application, and outages get noticed.
What is settled before go-live
Your domain and a person who sets the DNS record. A decision on who may see the application; private access comes with Pro and Enterprise. The publishing region, because it cannot be changed afterwards. And a person who receives alerts and decides whether an error is fixed at once.
What you have at the end
An application under your domain, with the kind of publishing that fits its load. Access rules we have tested with a test user. Monitoring that reports outages to the right person. And the running costs from the pilot, before the application is opened to everyone.
Sound familiar? Tell us where you stand today.
ContactWhat's new.
As of: 24 October 2026
- As of 24 October 2026
Autoscale, Static, Reserved VM and Scheduled.
Autoscale adjusts resources to usage, Static serves websites without server logic, a Reserved VM runs continuously with fixed capacity, and Scheduled starts an application at set times. Custom domains can be connected or bought directly.
Source: Replit Docs: Replit Deployments - As of 24 October 2026
Access public, password protected, workspace only or invite only.
Administrators restrict the allowed options, and on the Enterprise plan private deployments can be required for all projects, with exceptions per project.
Source: Replit Docs: Private deployments - Since 22 October 2026
The Monitoring Agent takes the on-call shift.
It reads logs and metrics of the production application, investigates alerts and proposes validated fixes; if you wish, it publishes them itself. It builds on monitoring with health checks and downtime alerts.
Source: Replit: Monitoring Agent
Built with Replit and in operation.
REV Ritter uses the application for market inspections, abonax provides its legal and regulatory offering on the platform, and OLAO Health connects website, clinic portal and app on one shared base.
What IT and business teams ask before go-live.
Which kind of publishing suits us?
That depends on the load: Autoscale for portals with fluctuating use, Static for websites, a Reserved VM for services that run all the time, Scheduled for runs at set times. We decide per application and check it in the pilot.
Can we publish an application internally only?
Yes. On Pro and Enterprise only workspace members, invited people or whoever knows the password then see it. On the Enterprise plan administrators require private deployments for all projects.
May the Monitoring Agent publish fixes on its own?
Only if you allow it. We recommend having a person review its proposals first and enabling autonomous publishing only for narrowly defined errors.
Where does the published application run?
In the region you choose at the first publication; compute, database and storage then sit there together. If data has to stay in Switzerland, we run the application in your Azure.
Agree on a useful next step
Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.



