Remote Development Environments
Modern distributed systems require a lot of computing resources and bring laptops to their limits. Move your dev runtime to the cloud and benefit from infinite scalability and a cool laptop to work with.
Validating your code and running full integration tests on your local machine is often hardly possible and may produce vastly different results than in your staging or testing environments.
If your application needs heavyweight, high-maintenance backing services such as a Kafka cluster or a distributed database, admins can create a central service and make it available for all engineers in their respective dev environments.
Development environments managed with Loft work with any development tool that is designed to be used with Kubernetes, including DevSpace, Tilt, Skaffold, and Telepresence.
Most modern cloud-native development tools such as DevSpace provide a two-way sync for files, so that you can keep coding using your local IDE and even set breakpoints in your local IDE but the actual code execution happens inside your cloud-based development environment inside a Kubernetes cluster.
Loft's advanced inactivity detection monitors when engineers are not working with their namespaces and virtual clusters, so you can define rules for automatically putting pre-production environments to sleep or even configure Loft to automatically delete them after a certain period of inactivity.
Once an engineer starts using a namespace again (e.g. run a kubectl command), Loft automatically restores the state of the namespace and the engineer can keep working.
