Use case

Why the best companies use preview environments for every pull request

Join 4,000+ companies already growing

Loft provides everything you need to add automatic preview environments for every pull request

CI Integration

Set up preview environments in seconds with the CI tool of your choice

1

Virtual Clusters

Let every team or developer have their own Kubernetes clusters without breaking the bank

<10 Seconds Startup Time because a virtual cluster is essentially just a container.

Running on top of EKS, GKE, AKS and others for seamless use of other cloud-managed services.

Production-like ephemeral clusters at the fraction of the cost of “real” clusters.

Easy Provisioning via CLI, UI, or even just via kubectl and CRDs.

Certified Kubernetes Distro ensures that it works just like any Kubernetes cluster.

Virtual Cluster Templates ensure company-wide standards and easy upgrades.

2

Sleep mode

Automatically turns off preview environments when nobody is using them and immediately wakes them up when somebody hits the preview URL.

Automatic Idle Detection to instantly detect unused virtual clusters.

Automatic Wakeup resumes the virtual cluster and its workloads once requests come in.

Out-of-the-box Compatibility for any infrastructure and any workloads.

Customizable Idle Timeout to define when auto-sleep should kick in.

Sleep/Wakeup Schedule to enforce sleep mode at certain times or pre-head environments on a schedule.

Advanced Customizations to exclude certain workloads or customize the sleep mode logic.

1

Developer adds a new feature

2

Product team needs to review it, but nobody is looking at it right away

3

So the environment goes to sleep after [30] minutes

4

Until finally, maybe 7 days later, someone from product has time to review the new feature

makers of
& more

Ready to get started with Loft?

Install Loft to your Kubernetes cluster to unlock self-service environment provisioning and virtual clusters for your engineering team.

Get Started Now

Debugging access

Give developers direct access to preview environments for debugging

1

Developer pushes a fix to make sure preview running

2

Product team reviews preview and finds 2 bugs

3

Developer connects to preview environment to debug the issues

How to get started:

Get Started Now