VCM provides Duke students and instructors with semester-long access to containers running applications such as RStudio and Jupiter and virtual machines (VMs). These environments are intended for coursework, software development, and as test servers for Innovation CoLab projects.
Think of VCM as an alternative to running a server in your dorm room - you have complete control of the server, but with this freedom comes responsibility -- you are responsible for server security and backing up your work.
Virtual machines in VCM are well-suited to acting as back-end servers for mobile applications or public-facing web services because they have public IP addresses and are available 24x7.
Since VCM is a software development sandbox, you should not run production / high traffic servers on VCM virtual machines. For enterprise-level production servers, click here for details. Information about research compute resources can be found here