2026-10-16 · Product & pricing
Why I do not write “unlimited” on the pricing page
For my managed applications the idea was tempting: unlimited resources, and anyone who overdoes it is asked to leave. I decided against it.
My pricing page said “standard resources” — without numbers. That looks weak and is too vague as contract content. The simplest fix seemed to be “unlimited”: no maths for the customer, and for the few who use a lot, a clause saying when they must move to an individual plan — say, above a multiple of the median customer.
Why that does not hold
“Unlimited” with a limit in the small print counts as misleading advertising in Germany, Austria and Switzerland; German courts have already struck down throttled “flat rates”. And a limit that depends on the median of all customers is something the customer cannot know when buying, and it shifts with every new customer. With twenty customers a perfectly normal Nextcloud with 30 GB is suddenly “ten times the median”.
Simply throwing out a customer for using what they were promised is not possible either — only with ordinary notice, and with a refund on annual plans.
What I publish instead
A single set of numbers for every instance: 100 GB storage, 2 vCPU, 4 GB memory, 1 TB traffic a month, daily backups kept for 14 days, unlimited users. Plus three add-ons at a fixed price. At 80 % storage I get in touch; nothing costs extra without consent, the instance simply stops accepting new data.
For almost everyone that is practically unlimited — just honest. And it covers the risk that actually matters to me: not the average, but the one customer who wants to park several terabytes.