Amit

Why NonBioS Chose Cloud VMs for a Native, Full-Stack User Experience

At NonBioS, we’ve been hard at work evaluating various infrastructure options to build a robust Linux sandbox environment for our users.

At NonBioS, we’ve been hard at work evaluating various infrastructure options to build a robust Linux sandbox environment for our users. Our goal is to deliver a full native Linux experience—not just a platform for building web apps but a complete system where you can spin up services, run background processes, and even log in directly to your own cloud box. After a detailed analysis of the options, we decided to use cloud VMs to provide a truly native experience.

Exploring the Options

When designing our service, we considered two major approaches:

  • Container-Based Systems with Kubernetes:
    Platforms like Replit have successfully leveraged Docker containers orchestrated by Kubernetes. This method packs many lightweight containers onto shared hardware, offering fast startup times and impressive cost efficiency. However, containers share the host’s kernel, which means that while they work great for web-based coding and development, they impose some limitations. For example, users typically have restricted system-level access and can’t perform certain low-level operations—making this approach less suitable for those who need a complete, unbridled Linux experience.
  • On-Demand Cloud Virtual Machines:
    On the other hand, provisioning full virtual machines offers an authentic Linux environment. Each VM runs its own complete operating system, allowing users full root access, the ability to install any software, and the freedom to spin up a range of services—just like on a dedicated physical server. The trade-off here is that VMs usually come with a bit more overhead and may have slightly longer startup times compared to containers.

We also looked at lightweight virtualization technologies such as Firecracker and Kata Containers, which strike a balance between security isolation and resource efficiency, yet they added complexity and didn’t fully align with our vision of complete system control. Additionally, we considered container-native PaaS solutions like Fly.io that abstract away the underlying infrastructure, but these services typically optimize for web applications rather than the full spectrum of use cases we envisioned—from spinning up diverse services to allowing direct user logins. Ultimately, while each option had distinct benefits, none offered the comprehensive, full-stack environment we wanted, prompting us to choose cloud VMs to provide an unbridled, authentic Linux experience.

Our Decision: Full Native Experience with Cloud VMs

After weighing the trade-offs, we decided that cloud VMs are the best fit for our full-stack vision. Here’s why:

  • Complete Control and Flexibility:
    We want you to be able to do everything—a full Linux environment where you can install any package, run any service, or customize your system to your liking. With cloud VMs, you get a real Linux machine, not a container with restrictions. This means you’re free to explore, experiment, and build without limitations.
  • Direct Login Access:
    Our approach enables direct login into your cloud box. Unlike container-based systems that often abstract away the underlying infrastructure, our VMs provide you with a direct connection—making remote management, SSH access, and debugging feel just like working on your local machine.
  • Tailored for a Full-Stack Service:
    While platforms like Replit focus primarily on enabling users to build web apps, we’re committed to offering a full stack service. Our infrastructure is designed to support everything from web development to running persistent background services. This holistic approach means that whether you’re building a website, hosting a microservice, or setting up a complete development environment, our VMs are built to handle it.

How It Compares to Replit

Replit is a fantastic platform that uses container orchestration to deliver code execution in a multi-tenant environment. Their system is optimized for speed and resource efficiency by suspending inactive containers and quickly waking them up on demand. However, this design inherently limits some low-level system operations and full OS-level control.

At NonBioS, our mission is to go beyond that model. We want to give you an environment where you have a dedicated Linux system, even if it comes with the complexity of managing full VMs. This approach better aligns with our vision of a complete full-stack service—one that caters not only to web app development but to any use case you might imagine.

What’s Coming Next

While we’re excited about this new direction, we’re still in the early stages of the rollout. Currently, our virtual sandbox is implemented as a shared box, but we’re actively developing the cloud VM solution that will allow each user to have their own isolated environment. We plan to go live with this new system sometime next week. Our team is working diligently to ensure a smooth transition and an excellent user experience.

Stay tuned for more updates as we refine and expand this feature. We’re eager to see how our community uses their new, fully native Linux environments to build, innovate, and push the boundaries of what’s possible.

At NonBioS, we believe that giving you the tools to truly own your computing environment is the first step towards unleashing your full potential. We can’t wait for you to try out our upcoming VM-based sandboxes and see the difference for yourself!

Apply for Beta

Experience the next level of AI-driven, transparent, and controllable software development.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.