The main task of the infrastructure team at Replit is to ensure your Repls run well. A Repl can be thought of as a Linux container with a filesystem. To run Repls, we need to take care of several pieces of infrastructure: Virtual machines to run Repl containers on Databases to keep track of container and VM states Cloud storage to store Repl contents Reverse proxies to route HTTP requests| Replit Blog
In 2023, we brought the vision of idea to software, fast, to reality. We shipped the first conversational AI programmer to code your ideas faster, made AI available for everyone, and introduced Deployments to ship from where you write your code. We made coding on Replit a better and more productive experience by redesigning the Console, Git integration, Packages tool, and more. We released the Replit Desktop App so you could choose the form factor that works best for you. We’re not finished...| Replit Blog
Stay connected A few months ago, we shared that we upgraded some of the virtual machines (VMs) that back Repls. This meant that Hacker, Pro, and Teams users were 10x less likely to have to reconnect and lose the running state of their program because the backing container restarted. We know that the reconnect can be painful and interrupt your state of flow.| Replit Blog
Repls today allow 256+ GiB of storage space, up from a historical 1GiB limit. This post is about the infrastructure that enabled that change. Historically Replit limited files in each Repl to 1 GiB of storage space. The 1 GiB limit was enough for small projects, but with the advent of AI model development and with some projects needing gigabytes worth of dependencies to be installed, 1 GiB is not enough. We announced on Developer Day that we were rolling out the infrastructure to unlock much ...| Replit Blog