Hosting and cloud

Used here, in this category

• Cloudflare Pagesserves
  Evidence: .github/workflows deploy step, wrangler pages deploy

All 22

Alphabetical. Checked on 2026-09-04; anything that did not answer says so.

• Adaptable the domain does not resolve
  Template-driven deployment of applications and databases. The domain no longer resolves.
  Gone: the domain does not resolve.
• AWS
  The cloud that set the vocabulary. Nearly everything else in this catalogue either runs on it or is defined against it.
  Everyone else's baseline.
• Azure
  Microsoft's cloud, strongest where an organisation already runs on Windows, Active Directory and Office.
  Wins on what the enterprise already bought.
• Beam
  Sandboxes, queues and model inference with fast cold starts, sold on how quickly a container becomes ready.
  Competes on boot time.
• Cycle.io
  A control plane that provisions infrastructure and runs distributed applications without requiring an operations team.
  Aimed at teams too small to hire a platform engineer.
• Digital Ocean App Platform
  DigitalOcean's managed application hosting, deploying from a repository without cluster management.
  The simple tier of a simple cloud.
• DigitalOcean
  A cloud that competed on comprehensible pricing and documentation rather than on breadth, now pushing inference too.
  Won developers by being possible to understand.
• Fly.io
  Runs applications and now agent sandboxes close to users, with virtual machines rather than shared containers.
  Gives the agent a whole computer.
• Google Cloud Platform
  Google's cloud. Strongest in data, machine learning and the parts of Kubernetes it originally wrote.
  Wrote Kubernetes, then had to compete on everything else.
• Heroku
  The platform that invented the modern deploy: push a branch, get a running application. Everything after it is a reaction.
  Defined the category, then lost it on price.
• Kinsta
  Managed WordPress and application hosting on Google's infrastructure, sold on performance and support.
  Premium WordPress hosting, priced accordingly.
• Koyeb
  Serverless deployment across CPUs, GPUs and accelerators in many regions, without cluster management.
  GPUs without a Kubernetes cluster.
• Netlify
  Static hosting with build pipelines, edge functions and preview deploys. One of the two that defined the category.
  Made 'push to deploy' the default expectation.
• Platform.sh
  Managed hosting with cloned environments per branch. The address now leads to Upsun, its successor product.
  Continued under a new name.
• Propel
  A serverless ClickHouse platform for customer-facing analytics, without operating the cluster.
  ClickHouse without the operations burden.
• Qoddi
  Application hosting positioned directly as a Heroku replacement, across several runtimes.
  Built for people leaving Heroku.
• Quix
  Stream processing in Python for sensor and test-rig data, aimed at hardware engineering.
  Streaming for the factory, not the feed.
• Railway
  Deploys applications, databases and services from a repository with infrastructure inferred rather than configured.
  Made the config file optional.
• Reflex
  Builds full web applications in pure Python, compiling the front end so no JavaScript is written.
  Web apps for people who do not want to leave Python.
• Render
  Application hosting for services, databases and cron, positioned between a platform-as-a-service and raw cloud.
  Heroku's shape without Heroku's pricing history.
• Vercel
  Hosting built around Next.js, which it also maintains. Now sells itself as infrastructure for agents as well as pages.
  Owns the framework and the place it runs.
• Zeabur
  Deployment with an agent that handles the infrastructure side, positioned as the operations half of assistant-written code.
  An agent for the part after the code is written.

Other shelves