Home
Companies
LaunchFlow

LaunchFlow

A better developer experience on GCP and AWS

LaunchFlow is the easiest way to build and deploy Python apps on GCP and AWS. LaunchFlow manages cloud environments in your own GCP / AWS account that are secure, scalable, and cost effective by default. Import Postgres, Redis, and other cloud resources in your Python code, then deploy everything to your cloud with a single command.

LaunchFlow
Founded:2023
Team Size:3
Location:
Group Partner:Michael Seibel

Active Founders

Josh Tanke

Co-Founder of LaunchFlow. Previously worked as a Software Engineer at Google[X] and Verily (formerly Google Life Sciences).

Josh Tanke
Josh Tanke
LaunchFlow

Caleb Van Dyke

Co-Founder of LaunchFlow. Previously worked as a Lead Software Engineer at various teams across Alphabet. Built primary ML infra platform for real-time data processing at Verily (formerly Google Life Sciences). Enabled real-time document prediction at Google Drive.

Caleb Van Dyke
Caleb Van Dyke
LaunchFlow

Company Launches

TLDR

LaunchFlow manages cloud environments in your own GCP / AWS account that are secure, scalable, and cost-effective by default. Import Postgres, Redis, and other cloud resources in your Python code, then deploy everything to your cloud with a single command.

LaunchFlow is an infrastructure-from-code tool that aims to dramatically improve your developer experience on GCP and AWS. We automatically deploy infrastructure to dedicated environments in your cloud as you use it in your code and ensure it's configured for both local development and production deployments.

The Problem

We believe managing and using cloud infrastructure is far more complex than it should be. It's hard to set up deployment pipelines. It's frustrating to run your application locally. It's annoying to keep your cloud configuration in sync with your application code.

Most teams cobble together their own DevOps automations using a mixture of Terraform, Pulumi, custom scripts, and environment variables. These automations are great when they work but are often brittle and eventually become the main source of overall system complexity.

We believe there's a better way.

The Way

Use LaunchFlow’s Python SDK to import Postgres, Redis, and other cloud resources in your Python code, then deploy everything to dedicated environments in your cloud with a single command.

Everything in the LaunchFlow ecosystem is fully configured for local development and cloud deployments by default.

Environments

LaunchFlow deploys and manages your infrastructure inside Environments that run in your own cloud account. These Environments satisfy most compliance requirements by default and are automatically configured for cost, security, and reliability.

Resources

You can create and connect to cloud Resources in an Environment by simply importing them into your code. Our SDK provides ready-to-use client APIs for every Resource so you can immediately start using them in your application both locally and when deployed.

Deployments

You can build and deploy Python applications in the same environment as your resources with a single command. LaunchFlow Services lets you deploy your APIs to GCP / AWS with all resource permissions and networking settings automatically configured. We will be adding Jobs and Notebook deployments in the next couple of months.

Works anywhere that Python runs

LaunchFlow Resources manages its own configuration and can be plugged into any existing Python app. We’re framework-agnostic and work anywhere that Python runs - we also include a library of common utilities for building FastAPI, Flask, and Django apps on the cloud.

Why not just use Terraform / Pulumi?

Tools like Terraform and Pulumi make it easy to automate cloud infrastructure, but there is still an added cost of maintaining a separate IaC tool and keeping it in sync with your application encode.

On top of this, these tools only help you create the infrastructure, but they don't help you actually use it. Engineers can spin up infrastructure in a few minutes, but they'll often spend the rest of the day (or longer) stumbling through docs and blogs, trying to figure out how to actually connect it to their application.

Things only get worse once you add a release pipeline into the mix and now need to figure out how to structure your code to work across multiple environments.

This creates a tradeoff between automation and overall system complexity, which is why many teams put off IaC practices until they can afford a DevOps engineer/team to maintain the automations for the company.

Our ask

We are looking for pilot users who would like to start using LaunchFlow today.

If you’re interested in using LaunchFlow, please email me at josh@launchflow.com or schedule a demo call using my Calendly.

Happy launching! 🚀