The company that turned "no servers" from a slide-deck buzzword into an actual deploy command - one serverless.yml file at a time.
A plain black-and-white mark for a plain black-and-white idea: the machines are still there, you just stopped looking at them. Founded 2015 by Austen Collins, San Francisco.
There is a genre of software company that exists because one person got tired of doing something by hand. Serverless Inc. is the cleanest example you will find. In 2015 a developer named Austen Collins was wiring up AWS Lambda functions the way everyone did back then - manually, painfully, one IAM policy and API Gateway route at a time - and he wrote a tool to stop having to do it. He called it JAWS. Then he renamed it the Serverless Framework, which is both more descriptive and more marketable, and posted it to GitHub.
The pitch was almost aggressively unglamorous: write a configuration file called serverless.yml, run one command, and your cloud functions are deployed across accounts, stages, and regions. No servers to provision, no infrastructure to babysit. This is the part worth pausing on, because "serverless" is a slightly dishonest word. There are, of course, still servers. Amazon owns them. You just never see them, never patch them, and never get paged at 3 a.m. because one of them fell over. The whole business is the layer of abstraction that lets you pretend the servers are not there.
That abstraction turned out to be enormously popular. The open-source project collected more than 25,000 stars on GitHub, which for an independent project is the kind of number that makes venture capitalists return your calls. Trinity Ventures led a $3 million seed round in 2016. Lightspeed Venture Partners led a $10 million Series A in 2018. Total raised: $13 million, which is not a lot by the standards of the cloud-infrastructure gold rush, and that turns out to be part of the story too.
Because here is the interesting tension. Serverless Inc. is a small company - roughly 17 people - that named and shaped a category the hyperscalers now compete inside. Amazon built its own competing tools (SAM, CDK). HashiCorp's Terraform and Pulumi crowd the same infrastructure-as-code space. And yet the Serverless Framework kept showing up in production at EA Sports, Coca-Cola, Nordstrom, Expedia, and Reuters. When you have defined the vocabulary everyone else uses, you get a seat at a table much bigger than your headcount would suggest.
The most instructive chapter came in 2024, when the company shipped Version 4 and, with it, a genuinely novel pricing decision. The framework stays free for individuals and organizations earning under $2 million a year. Above that threshold, you are asked to buy a credit-based subscription, where one credit maps to one deployed service instance. But - and this is the part that reads like a thought experiment escaped from an economics seminar - there is no audit, no revenue verification, no gate. It runs on the honor system. Big companies are trusted to notice they are big and pay accordingly.
Predictably, monetizing an open-source project is never frictionless. When V3 support formally ended on December 31, 2024, the community forked it into a project called oss-serverless and pledged five years of maintenance. You can read that as a rebuke, or you can read it the way open-source maintainers eventually learn to: as proof that the thing you built mattered enough for people to fight over who gets to keep it alive. Both readings are correct. That is usually how it goes.
The open-source CLI. Describe your functions and resources in serverless.yml, deploy to AWS Lambda (and beyond) with one command, roll back just as easily.
Commercial layer for monitoring, observability, secrets, CI/CD, and team collaboration across serverless apps. Free tier, paid above.
Hybrid developer mode (local-to-cloud function forwarding), multi-cloud flexibility, HashiCorp Vault integration, built-in CI/CD, and the new commercial license.
Higher-level, reusable building blocks for deploying entire applications and infrastructure without reinventing the wiring each time.
Bars are illustrative and scaled for readability. Revenue is an external estimate, not a company-reported figure.
Austen Collins founds Serverless Inc. and renames his AWS Lambda project.
Trinity Ventures leads a seed round; the framework ships its 1.0 release.
Lightspeed Venture Partners leads, bringing total funding to $13M.
The company expands beyond the CLI into commercial observability and reusable blocks.
Paid subscriptions above $2M revenue, hybrid dev mode, and Vault integration arrive.
V3 maintenance stops Dec 31, 2024; the community launches oss-serverless with a 5-year plan.
| Round | Amount | Date | Lead Investor |
|---|---|---|---|
| Seed | $3M | Oct 2016 | Trinity Ventures |
| Series A | $10M | Jul 2018 | Lightspeed Venture Partners |
| Total | $13M | - | - |
The infrastructure-as-code space is crowded. The Serverless Framework shares oxygen with tools from Amazon itself and from well-funded rivals:
The Serverless Framework - an open-source tool for deploying applications to AWS Lambda and other function platforms - plus a commercial dashboard for monitoring and CI/CD.
Yes for individuals and organizations under $2M in annual revenue. As of V4 (2024), organizations above that threshold buy a credit-based subscription.
Austen Collins, in 2015. He created the framework (originally JAWS) and is recognized as an AWS Serverless Hero.
$13M total: a $3M seed led by Trinity Ventures (2016) and a $10M Series A led by Lightspeed Venture Partners (2018).
Developers worldwide plus enterprises including EA Sports, Coca-Cola, Nordstrom, Expedia, and Reuters. The project has 25,000+ GitHub stars.