Schedule a command to execute on a defined schedule in a specific environment

Command which runs after build and before the deploy

By using a permanent server, we can achieve maximum build speed with maximum caching.

Easily build and deploy lamba functions with a Vercel-inspired DX

Currently all environments in a project have to be in the same AWS account, but we can allow them to be in separate accounts.

This is for things like running rake tasks in a production environment

Premium feature for additional cost

Eliminate service config duplication

A way to run a command after RDS DB is created for a branch to use for seeding the database

Built into Flightcontrol, no extra config needed

Manage your flightcontrol projects and config from Terraform

Environment VPCs would span across all projects by default

Both by default and as an override

currently we can do it manually for you

Easily attached groups of env vars to different projects, environments, & services

Like max CPU, memory, crashes, etc

Display & notifications

Easily change nixpacks version, native dependencies, etc without nixpacks.toml

Deploy frontends to Vercel but backends to AWS. *Please* let us know how you'd like this to work.

One use case for this is if you want to use Cloudflare instead

Automatically get a new planetscale branch attached to PR deployments

For services that depend entirely on runtime environment variables

Get a private remote cache server + S3 storage deployed inside your AWS account instead of having to use Vercel

This supports deploying code to an EC2 instance. Great for services that need a permanent disk.

This service type will not deploy any code, manage OS updates, or anything like that. But it does make it easy to set up a server, manage the instance size, etc.

*Please* tell us what you want a CLI to do! :)

Deploy frontends to Netlify but backends to AWS. *Please* let us know how you'd like this to work.

Easily give users access to Flightcontrol managed resources