Amplify hits a design cliff
Jason Lengstorf, VP of Developer Experience at Netlify, on Jamstack's anti-monolith approach
The real risk in Amplify is not getting started, it is what happens when a team outgrows the preset path. Amplify is built to spin up a full stack app quickly with hosting, CI/CD, previews, auth, and data services wired into AWS. That works well until a product needs a custom workflow or nonstandard service mix, at which point the team has to drop from a simple wrapper into raw AWS primitives and untangle whatever was auto configured underneath.
-
Amplify is opinionated by design. AWS positions it as a code first full stack workflow with hosting, secrets, auth, data, staging deploys, and developer sandboxes. That is powerful for standard app shapes, but it also means the abstraction has a defined edge.
-
Netlify is drawing a different line. Instead of handing teams the underlying cloud setup once they need something custom, it keeps the deployment layer stable and lets teams attach outside services as needed. In practice that means Git based deploys, previews, rollbacks, and edge logic stay the same even as the stack around them changes.
-
This is why Jamstack vendors often look more like workflow products than cloud bundles. The value is not only hosting pages on a CDN. It is removing the day to day chores of configuring infra, tracing bills, managing rollbacks, and stitching review into release, which are exactly the jobs teams inherit when the wrapper disappears.
The category is moving toward thicker abstractions, not thinner ones. AWS is adding more full stack conveniences inside Amplify, while Netlify is pushing more of the app lifecycle into one managed workflow. The winner will be the platform that lets teams ship complex apps without ever forcing them to become part time cloud mechanics.