The AI boom has fundamentally changed how startups think about infrastructure. What was once a relatively straightforward cloud scaling journey has become far more complex, as companies now balance GPU-intensive workloads, rapidly evolving AI models, compliance requirements, and rising operational costs. For many startups, the challenge is no longer simply getting a product to market. It is keeping cloud operations sustainable while scaling fast enough to compete.
At the same time, AWS has evolved into far more than a hosting platform. For startups building AI-native products, it has become an orchestration layer for everything from deployment pipelines to generative AI governance. According to Automat-it CEO Ziv Kashtan, the startups that scale most successfully are the ones that treat cloud architecture as a strategic advantage rather than an afterthought.
The Hidden Cost Of Scaling Too Fast
“Early on, we saw that rapidly growing startups often let their cloud spend outpace their revenue,” Kashtan says. That observation shaped Automat-it’s strong emphasis on continuous FinOps optimization as part of its AWS managed services approach.
The company, an AWS Premier Partner specializing in startups, has supported thousands of companies as they move from MVP to production. What began as a DevOps-focused business has evolved into an AI services company helping startups operationalize increasingly complex AI workflows on AWS.
The 💜 of EU tech
The latest rumblings from the EU tech scene, a story from our wise ol’ founder Boris, and some questionable AI art. It’s free, every week, in your inbox. Sign up now!
Kashtan says one of the biggest misconceptions founders have is believing that migrating to AWS alone guarantees efficiency.
“Lift and shift is good enough,” he says, describing a common mindset among startups. “AWS is like Lego. You can build anything on it. But you can also miss out on all the good stuff easily.”
Another misconception is that managed services are inherently more expensive than building everything internally. According to Kashtan, startups often underestimate the hidden costs of maintenance, patching, downtime, and inefficient resource management.
The pain usually emerges when startups move from early execution into true scaling mode. Suddenly, AI inference costs spike, deployments become increasingly fragile, and engineering teams spend more time dealing with outages than building products.
“In practice, this can look like spiraling AI and GPU costs, where startups struggle to maintain sustainable unit economics,” Kashtan explains.
Why DevOps Maturity Matters
One of the most consistent architectural mistakes Automat-it sees is startups delaying operational discipline until later stages of growth. Teams often skip multi-account AWS landing zones, rely on manual provisioning through the AWS console, or deploy monolithic systems that become difficult to scale.
“We often see teams manually provisioning resources via the AWS Web UI rather than relying on Infrastructure as Code,” Kashtan says.
For high-growth startups, DevOps maturity becomes directly tied to speed and resilience. Mature CI/CD pipelines, automated testing, and Infrastructure as Code enable startups to deploy faster while reducing operational friction.
Kashtan argues that the most effective startups embrace “outcome over output,” outsourcing undifferentiated infrastructure management so internal teams can focus entirely on proprietary innovation.
“When DevOps is mature, engineering teams are freed up to focus entirely on their core product,” he says.
That operational maturity also increasingly applies to AI workloads. Many startups rush to production with impressive AI demos, only to discover that production-grade observability, governance, and cost control are significantly harder problems to solve.
What A Well-Optimized AWS Environment Looks Like
According to Kashtan, well-optimized startup environments on AWS share several common characteristics.
They prioritize Infrastructure as Code from day one using tools like Terraform or AWS CDK. They implement multi-account strategies for security isolation and compliance readiness. They embrace elastic compute environments such as Amazon EKS Auto Mode or Amazon ECS on Fargate to reduce operational burden and optimize costs.
In AI environments specifically, Automat-it advocates for multi-tiered model strategies using Amazon Bedrock, where simpler tasks are routed to lower-cost models while premium models are reserved for more advanced reasoning workloads.
“Teams make the mistake of using a single, premium LLM for everything,” Kashtan says. “A multi-tiered model strategy dramatically improves efficiency.”
Automation also plays a growing role in reducing operational overhead. Kashtan points to cloud cost management, CI/CD pipelines, compliance evidence collection, and agent orchestration as areas where AWS-native automation can significantly reduce engineering burden.
A Twelvefold Reduction In AI Infrastructure Costs
One example Automat-it highlights is its work with mokSa.ai, a video intelligence startup facing unsustainable infrastructure costs.
The company’s original architecture relied on one AI model per dedicated GPU instance, resulting in costs reaching $353 per camera per month. Automat-it re-architected the platform using Amazon EKS and implemented NVIDIA GPU time-slicing to allow multiple AI models to share virtual GPU resources simultaneously.
“The result was an incredible twelvefold cost reduction, down to just $27 per camera monthly, while keeping inference times well under their required 500ms threshold,” Kashtan says.
The AWS Landscape In 2026
Looking ahead, Kashtan believes AWS will continue evolving into a managed orchestration layer for Agentic AI systems, abstracting away much of the infrastructure complexity startups currently struggle with.
“With stringent regulations like the EU AI Act taking effect in August 2026, AWS’s built-in governance and traceability tools will become vital survival mechanisms for high-risk startups,” he says.
For founders building on AWS today, his advice is ultimately straightforward: “Focus on your core product and partner for the rest.”
