How NeuBird established measurable infrastructure recovery and faster provisioning with FluidCloud

NeuBird has raised $64M, holds the AWS Generative AI Competency, and has resolved more than 1M production alerts for its customers. It was founded by Gou Rao and Vinod Jayaraman, who previously built and sold Portworx to Pure Storage for $370M.

Its largest enterprise customers need dedicated, single-tenant deployments to meet their own security and compliance obligations, so NeuBird's AWS estate is several isolated environments rather than one. Like most platform teams, NeuBird described them with a maintained Terraform library. As the number of environments grew, that library set the pace of onboarding, and it was also the artifact any rebuild would start from. NeuBird wanted both to come from the accounts themselves.

Capture runs twice daily against the AWS accounts and daily against the Azure account. Each capture is an immutable, individually addressable record of the estate, and deployable Terraform with a matching state file can be regenerated from any of them. FluidCloud compares each capture with the one before it and reports what was added, modified and removed. AWS CloudTrail records every read-only call, so NeuBird keeps an independent audit trail of what was accessed.

NeuBird chose this over the conventional alternatives. A warm standby estate carries continuous AWS cost for capacity used only during an incident. Snapshots and AWS Backup protect volumes, databases and objects, which NeuBird still retains, but not Amazon VPC topology, security groups, IAM roles, load balancer configuration or the order resources must come up in. AWS CloudFormation or the AWS CDK would have added a second infrastructure-as-code format alongside the Terraform NeuBird already ran, across an estate that also spans Azure. The cross-account role, scoped and revocable by NeuBird with no long-lived credential to distribute, is what kept the security review proportionate.

Standing up an isolated enterprise customer environment now takes about an hour, against about seven days before. Engineers previously wrote or adapted Terraform for the target AWS account, configured CI/CD pipelines, provisioned secrets through AWS Secrets Manager for each deployment and validated the result against production. Provisioning from a capture taken out of the live account removes that reconciliation work. NeuBird's first account scan ran on 23 April 2026, and its first environment deployment completed the following day, under 21 hours later, including the initial account connection.

Across 132 consecutive days NeuBird has accumulated 1,085 configuration recovery points with no gap in the series, and every capture reports the drift since the last one. In one representative measurement that was 794 changes in a single AWS Region between two consecutive captures, which is the scale of change a hand-maintained library absorbs quietly. Because the reconstruction path is held as code, NeuBird runs no standby AWS estate between incidents.