Use cases

A web hosting provider that puts online shops on its front page is recorded as marketing itself for online shops, whether or not it is the best place to run one. Most providers claim several use cases. Who it sells to is audience, which is kept separate because a side project and a government department can want the same software and will never want the same contract.

16 values in use. 53 records do not record this field.

• CMS sitesWhere the site is edited, not just deployed.102 records
• Headless CMSTwo things to host, not one.5 records
• Online shopsThe pages that cannot be cached.57 records
• Web appsAn application, not a site.63 records
• API backendsNobody is looking at it.70 records
• Dashboards and admin panelsFew users, expensive pages.4 records
• Internal toolsNobody outside will ever see it.22 records
• Static sitesNo runtime to go wrong.26 records
• Campaign and landing sitesBrief life, sudden traffic.44 records
• PortfoliosCheap, quiet, and rarely touched.40 records
• Side projectsReal, unpaid, and possibly temporary.55 records
• AI and LLM appsSlow requests, and the model is not here.28 records
• Background jobs and queuesThe work that outlives the request.33 records
• Data pipelinesBatch work, not page views.17 records
• Game serversNot a web workload at all.7 records
• Learning and experimentsFor the version that gets deleted.9 records