Your cloud infrastructure feels complicated because the 3 core components live in different systems: 1. Infrastructure-as-Code. Your Terraform state and history is in something like Terraform Cloud or, God forbid, your local machine 2. Code deployments. Your ECS/k8s deployments are in CI or some other deploy controller. 3. Metrics, logs, cost tracking. Maybe you’re suffering with AWS Cloudwatch or Datadog. Now how can you expect developers to make and monitor changes effectively with this fragmentation? Soon we’re shipping something groundbreaking that solves this in a way every platform engineer will love 👀

I think every team using AWS is going to LOVE the all new @Flightcontrolhq we’ve been working on for 10 months. We’ve designed the most powerful and simple system I’ve ever seen. Devops define IaC that’s turned into a Vercel style interface for developers and agents. Engineered to deploy fast and understand every change. For both your existing infra and new. This product is going to make waves. It’s too much fun. Launching soon!

The design of this user facing system literally blows my mind. It’s is SO SIMPLE yet SO POWERFUL. Infinitely flexible to model any infra and deployment workflow you might want. While also being extremely simple and easy both for devops to implement and for developers to use. I think we’ve finally figured out the fundamental building blocks of infra, enabling the software model to match the world

👀 New @Flightcontrolhq is 100% IaC based AND 100% user configurable! including all orchestration and all UI forms 😱 shown here is our most generic "stack" module that replaces Terraform Cloud / Atlantis, complete with resource tracking but this can get very specific, like wrapping your custom Terraform stacks with a developer facing UI and these modules can reference other modules 😲

Yo, I think EVERY Terraform user is going to really want to use the next version of @Flightcontrolhq 👀 It’s SO GOOD! Alpha version dropping very soon

A WAY better AWS console is part of the value of the coming new @Flightcontrolhq 🔥 This is the ECS deployment view. Easily see what task definition is deployed, what changed, and the state and logs for all instances. All on one view instead of 10 different screens in AWS. *this is the design file so ignore data accuracy*

Yikes!! “The agent determined that the best course of action was to "delete and recreate the environment" You absolutely need a system of guardrails for AI to operate on your infra. @Flightcontrolhq provides this for AWS, but soon we’re taking the gloves off so you can design your own system and support multicloud systems

GitHub Actions, but it runs in your cloud. Sneak peek at our new pipelines 👇 Is this something you're interested in? Any requests?

Who is using LLMs to interact with their AWS stuff? What are you trying to do? What issues do you have with your workflow?

Simple AWS without the handcuffs — is it even possible? Countless companies have tried. No one's nailed it. Here's why I still think we can →

Every secret management tool i've seen has a broken data model (including my product) PROBLEM: item keys like STRIPE_SECRET_KEY are duplicated throughout the system. Even if you have groups, it's duplicated across your groups SOLUTION: single entry in the system for an item like stripe secret key and you can define multiple values for that with user defined ids like production and staging (prototype ui) USING THEM: Link one-off items anywhere you need like STRIPE_SECRET_KEY=$ref:stripe-secret-key:production Link groups that define key=value mappings (prototype ui) BUT WHY? see at a glance exactly (1) how many different values for a key exist, (2) what those values are, AND (3) where each of those values are used 🤯 Coming soon to users near you

Taking the gloves off. Sneak peek at what we're building @Flightcontrolhq →

🔥 ANNOUNCING @Flightcontrolhq's NEXT EVOLUTION 🔥 Teams chose Flightcontrol to simplify infrastructure without loosing control to a PaaS abstraction. For many workflows, it delivers. But growing teams hit limits, leaving them managing settings and infrastructure outside Flightcontrol that they wish lived inside it. 🚨 We're removing those limits, bringing new features so you can use Flightcontrol for everything! 🚨 The next version is a fundamentally more powerful system. Instead of a few fixed workflows, you get composable primitives: 🚀 Flightcontrol Modules turn any Terraform into a reusable, UI-driven component. —— This is like our current "service types", but now you can customize ours or add your own. 🚀 Terraform CI shows you exactly what's happening—every plan, every apply. —— Modules are sugar on top of Terraform stacks. And you can bring your own stacks (goodbye Terraform Cloud!) 🚀 Pipelines give you GitHub Actions-level flexibility for builds and deploys, but running in your cloud! —— Our same build and deploy features, but now you can orchestrate any way you please. Current Flightcontrol makes a few workflows easy. This makes any workflow easy. Including multi-cloud! We're aiming for production-ready by end of Q1. Let me know if you're interested in early access 👀