Stable reference data
Soapie uses a bundled oil catalog so saved formulas stay tied to a known version of the data instead of drifting behind the scenes.
Trust
Soapie is built to be workshop-safe, not growth-hack first.
The product has a simple stance: keep the calculator legible, keep the records local, and do not surprise the maker in the middle of actual work. That trust model shapes the app and the site.
Local-first records
Recipes, batch history, cure tracking, and inventory are designed to live on device unless you explicitly export them or enable future sync features.
No paywall during active work
The launch pricing stance is deliberately workshop-safe: the app should not interrupt a real batch to force an upgrade.
Readable methodology
The app is meant to expose its assumptions, not hide them, so users can understand how totals, property ranges, and cost snapshots were derived.
Where to go next
If you want the product story, start with the feature pages. If you want the legal or data posture, go to privacy and terms. If you want the monetization stance, the pricing page explains why free is intentionally useful before Pro shows up.