The Serverless page says 141 related providers. It renders 30, all from the top, and its overview says “30 providers on the network work in this area.” Those 30 have a median Kin Score of 67.5, and none sits below the strong band. The 134 scored records we can resolve from the area’s membership list have a median of 44.4, and 57 of them are thin, emerging or minimal. The 30 is a display cap of ours, and the sentence is a build bug.
The resolvable area, by band
We can only band what the source lists. It names 135 slugs, one of them not a provider record, so these counts cover 134 of the 141 the page claims.
| Band | Providers | Examples (Kin Score) |
|---|---|---|
| exemplar | 17 | Amazon DynamoDB 80.2, Appwrite 78.3, Cloudflare 75.6, Netlify 75.0 |
| strong | 30 | Koyeb 65.5, Vercel 64.5, Neon 58.7, Google Cloud Functions 54.3 |
| developing | 30 | RunPod 54.2, Supabase 48.9, Deno 43.0 |
| thin | 30 | Upstash 37.2, Fly.io 35.0, OpenFaaS 34.4 |
| emerging | 14 | MotherDuck 20.2, 8base 19.9 |
| minimal | 13 | Kinvey 7.0, Fauna 0.0 |
What it tells you
AWS carries a lot of the top. 17 of the 134 are Amazon or AWS records, with a median of 63.1. Everyone else has a median of 42.0. AWS gets a record per service, so it holds a large share of the upper bands. Google’s serverless records sit lower: Cloud Functions and Cloud Run at 54.3, Workflows at 51.5. None of those three is in the rendered 30. That gap is a difference in what the record shows per service, not a verdict on the runtimes.
Agent readiness does not follow the same order. Cloudflare leads at 60.6, then InsForge at 55.0, with a Kin Score of only 58.1. Blaxel is the sharper case, at 33.7 on the Kin Score and 47.1 for agents, which puts a thin record seventh in the area. 40 of the 134 list an MCP server.
Serverless has a graveyard, and it is in the count. 9 providers score 0.0: Binaris, Bit.io, Epsagon, PiCloud, StackPath, Suborbital, Thundra, Fusebit and Fauna. Their records describe them in the past tense, and Fauna’s says the hosted service shut down in 2025. A market map that drops them loses the history, but they should not be read as current choices.
Three more things are ours to clean up. The page’s cohort brief splits its 30 as 10 exemplar and 20 strong, while the band pills on the same page show 18 and 12. Azure Functions has two records, Microsoft Azure Functions at 62.1 and Azure Function Apps at 43.8, and both descriptions cover the same service. And AWS Glue alone holds 203 of the 513 APIs those 134 records count.
Takeaway
Read this page as a shortlist and not as the market. The sample shows exemplar and strong platforms only, while the wider record is a broad middle with a long tail. We should render the full membership or say plainly that the list is a sample. See the live page and the Serverless area.