Raftt Certified

Raftt only uses the data required to spawn your dev env. Raftt first syncs the repo directory, excluding whatever is in .gitignore. If the build process requires extracting more data, we extract the data into our cloud env.

Raftt isolates the environment from all others at a network, filesystem, and runtime level.
So there is no risk of data leaking between environments.
For more details see our docs.

The environment and the data persist as long as it's used by you. Raftt terminates the whole environment if it’s unused for long enough, all environment data is deleted at that time.
You can explicitly terminate an environment and remove the data at any time by running raftt down -d

Like most devs, you run your code locally, either as processes, or as containers using docker-compose, Minikube, or similar tools. There are several drawbacks like wasting time on dev env setup and maintenance, drift between dev envs and production, and difficult branch switching.

We overcome those challenges by running remote envs that feel like they’re local.

Products that mimic staging and prod envs don’t solve many of the problems of developing and debugging in these types of envs. For example, running tests, debugging, or using local tools and clients is still a struggle.

With Raftt, it doesn’t matter which DB client or IDE you use locally, or what languages you program with. We’ll successfully spawn the environments and let you keep using the tools you know and love. Raftt supports various environment definition methods, such as docker-compose, Helm Charts and raw Kubernetes manifests.