BakeValue: recipe costing without a subscription

Why do recipe costing apps use subscriptions?

Many web and software-as-a-service products keep running infrastructure for every active customer. A typical service may need a registered domain, hosted application, database, account system, backups, logging, monitoring, and incident response. Vendor bills recur, and the work continues after launch.

A subscription can be fair when customers continuously use an operated service. But it is not the only responsible way to fund software. The price can follow the architecture instead of following an industry habit.

That distinction matters here. We develop and publish BakeValue, so this is an explanation of our own product decisions. It is not a claim that every other bakery-pricing app uses the same infrastructure or has the same costs.

How does BakeValue work without a subscription?

BakeValue's primary job is to help home bakers calculate product prices. Ingredient purchases, inventory, recipes, labor, packaging, overhead, and margins are stored and calculated on the iPhone or iPad. Normal use needs neither an internet connection nor a Kashi Works account.

Users do not sign up for BakeValue. There is no Kashi Works registration flow, password recovery system, account database, or authentication service to build, secure, and maintain. The core workflow also needs no hosted customer database or custom sync API. BakeValue has no ads, analytics, or tracking.

Privacy and pricing meet at the same engineering decision. Keeping the core product on the device limits the data we handle and removes a common recurring per-user infrastructure cost. That gives us room to offer Free permanently and sell Pro once.

Apple provides the optional sync layer

Bakers who want the same data on an iPhone and iPad can enable private iCloud sync. BakeValue uses Apple's CloudKit service rather than sending that data through infrastructure operated by Kashi Works.

Apple's CloudKit documentation says data in a private database counts against the user's iCloud storage quota. Apple provides 5 GB of iCloud storage at no charge, shared with the user's backups, photos, files, and other app data.

In real-world use, BakeValue records occupy kilobytes rather than gigabytes. Even a heavy BakeValue user is very unlikely to approach the 5 GB allowance through this app alone. The practical limit is whether other data has already filled the user's shared iCloud storage.

So the precise claim is not that BakeValue has no backend. Apple operates CloudKit. The accurate claim is that BakeValue has no Kashi Works-hosted app-data backend. CloudKit also has quotas and rate limits, and sync depends on an iCloud account, available storage, and connectivity.

How does CloudKit avoid recurring infrastructure costs?

The relevant difference is infrastructure. BakeValue does not need a separate hosted customer database, account service, sync API, backup system, or monitoring stack. CloudKit provides the optional private sync layer without a recurring per-user database bill from Kashi Works.

Because synced records stay in each user's private iCloud database, Kashi Works does not maintain customer-data hosting, backups, or authentication infrastructure for sync. Apple handles that layer through the user's existing iCloud account.

That is the cost BakeValue's architecture avoids: a custom hosted service whose bill can grow with usage. Removing that subscription-shaped expense makes a one-time purchase practical.

The promise is simple: no required BakeValue subscription

BakeValue Free remains available for core use. Pro is an optional one-time unlock: $9.95 through September 15, 2026, then $19.99 starting September 16. Both tiers include private iCloud sync without a separate monthly BakeValue fee.

Our architecture leaves room for that model. The core app runs locally, Apple provides the optional private sync layer, and Kashi Works does not operate an app-data backend for each customer. Product economics follow product engineering.

For a feature and price comparison with a subscription alternative, see BakeValue vs CakeCost.