Safora
Replace the paper food-safety diary with flagged deviations, manager sign-off and an inspection-ready PDF.
For kitchens and food businesses that keep daily checks. Often replaces FoodDocs, SafetyCulture or Trail.
Single license $79 · Extended license $179 · paid once, yours for good
What it does
An out-of-range reading cannot be saved without a corrective action, so every deviation has a recorded response.
Temperatures, core temperatures, cooling, deliveries, cleaning, and opening and closing checklists.
A printable PDF pack and a CSV for any date range, ending with your inspection folder.
Your HACCP plan, allergen matrix, staff training and certificates beside the temperature diary.
See which days had every check done and every reading in range.
A manager signs off each day's records with notes. A closed day can be signed off as closed, with a reason.
Record product, batch and use-by at the delivery check. When a recall arrives, search the batch.
After a grace period you set, the manager is emailed once per unverified breach. Verifying the action stops it.
This check, this often, by this time. A check counts as done only when a reading exists.
One email a day with the checks due and anything left open. Off until you switch it on.
The day view marks a checklist ticked unusually fast, so the manager signing off can ask.
Also: sensor readings over the API, CSV import with a dry run, and an installable phone app.
What Safora deliberately doesn’t do.
- Single-tenant: one business per installation (staff share the one instance, with roles).
- Safora documents your records; it does not connect out to fridge probes or IoT sensors. A probe that can make an HTTP request can post readings to the REST API: an out-of-range one is stored as an open breach, red until a person records the corrective action.
- It does not submit anything to any authority; it produces records you keep and present.
- Not legal advice, and not a certificate of compliance. The thresholds are HACCP-aligned defaults you can change; the bank-holiday list is England & Wales — one-off royal holidays, Scotland and Northern Ireland differ.
- Email goes through your own SMTP server; the open-breach chase is off until you switch it on.
What renting costs instead
1 month of FoodDocs costs what Safora costs once.
Read Sep 3, 2026 · source4 months of SafetyCulture (iAuditor) costs what Safora costs once.
Read Sep 3, 2026 · sourceThe full comparison: every rival, what each does better, and who should stay with them →
Replacing one of these? FoodDocs alternative · SafetyCulture (iAuditor) alternative · Trail alternative
Release history
For Safora, 4.1 makes two changes that every app gets. What’s new in 4.1 →
For Safora, 4.0 means updates from inside the app: the Updates page checks for a new release with your license key, verifies Ownware's signature, takes a backup and… What’s new in 4.0 →
The equipment import's preview used to count a fridge whose minimum is above its maximum as ready, and the import then skipped it. What’s new in 3.3 →
For Safora, the 3.2 wave put the rest of the inspection folder beside the temperature diary: your HACCP plan, an allergen matrix, staff training, certificates with…
The 3.1 wave gave the catalog a way to reach the other side of the transaction: counterparty email through your own SMTP server, calendar feeds your own calendar…
Scheduled checks say this check, this often, by this time — and a check counts as done because a reading exists, never because somebody ticked a box; a check counts as…
Safora 2.0 adds the 2.0 owner layer.
What’s in the zip
The tree as the zip ships it — the working leftovers the packager deletes are not listed
- .htaccess
- API.md
- Dockerfile
- LICENSE.txt
- QUICKSTART.txt
- README.md
- assets/
- bin/
- config.sample.php
- controllers/
- deploy/
- index.php
- install/
- manifest.json
- offline.html
- router.php
- src/
- sw.js
- tests/
- views/
src/FoodSafety.php: a real module, the first 24 of 444 lines
Chosen as the largest module in src/ that is not one of the shared cores — this product's own logic, not a file every product carries.
<?php
/**
* FoodSafety.php — THE compliance core Safora stands behind (fully covered by tests/run.php,
* offline). Nothing here touches the database or the network. Every food-safety rule the
* product enforces — temperature ranges, cooking/reheating/cooling limits, delivery checks,
* the "corrective action required when out of range" rule, per-day green/amber/red status,
* and the °C/°F conversion — lives here as pure, deterministic functions so it can be proven
* in isolation and reused identically by the web UI, the seeder, and the audit exporter.
*
* Canonical storage rule: every temperature is stored in degrees Celsius. The chosen display
* unit (°C or °F) only affects rendering and the parsing of user input.
*
* Positioning: Safora is a record-keeping and compliance-documentation tool. The thresholds
* below are sensible HACCP-aligned defaults (and are configurable per business); they do not
* constitute certification of compliance or professional food-safety advice.
*/
declare(strict_types=1);
final class FoodSafety
{
/** Float comparison slack so a reading exactly on the limit counts as in range. */
private const EPS = 0.0001;
/* HACCP-aligned defaults (all °C). Every one is overridable in Settings / per equipment. */Runs on: Two-minute web installer, PHP 8.1+ with MySQL or SQLite; demo mode ships roughly two weeks of pre-baked sample records. Tested on PHP 8.3. Or run it in Docker: the Dockerfile is in the zip.
Technical owners can install it with one line and their license key: curl -fsSL https://ownware.io/install.sh | sh -s -- safora <your license key>
Nothing is obfuscated or encoded; what you read is what runs. Manual · API · the test run
Which license do I need?
It comes down to how many installations you need. Running your own business on one site is the Single license. A second domain of your own, or sites you build or run for other people, is the Extended license.
- Install it on one domain or subdomain you own or operate
- Change the source however you like for that installation
- Run your own business on it commercially, client work included
- Re-download the current build any time from your buyer portal
- A second site, or an installation you hand to a client as theirs, needs the Extended license
- No reselling, redistributing or sublicensing the source
- Not for offering it to other people as a hosted service
- Everything the Single license grants
- Install it on as many domains as you own or operate — no cap on the number
- Up to ten client installations, one per client project, handed over or hosted for each client; for more, buy another Extended license
- White-label: remove or replace the product name and logo in the screens of client installations
- Still no reselling or redistributing the source itself
- Running it as a multi-tenant service others sign up for needs a SaaS agreement
Every download carries the full terms as LICENSE.txt. The complete wording is on the terms page.
After you buy
The app’s Updates page installs a new release with your license key, with the release’s signature checked and a backup taken first. Your download link always serves the current build. Download again any time from your order page or the buyer portal; there is no renewal fee.
Email support for installation and for defects in the code as delivered: a person reads and answers every message. It does not cover custom development or server administration. What support covers
Refunds are handled by Lemon Squeezy as merchant of record, case by case. EU consumers keep the statutory 14-day right until delivery starts. Refund terms
It keeps running: your server, the full PHP source, no license check that can fail. If no stable release is published for 365 days, the domain limit lifts; after three such years your copy becomes MIT-licensed. The terms have the exact wording: continuity.
Questions
Is this a legal guarantee of compliance?
Will this run on shared hosting?
Is the audit PDF a real PDF?
We work in Fahrenheit — is that supported?
Does it connect to wireless probes or IoT sensors?
What happens when a breach is left open?
Is Safora a subscription?
What exactly do I get for the money?
Can I get the diary out for an inspection?
Does this make my kitchen compliant?
Why pay for Safora over a free checklist app?
Covered in these guides
- What's new in Own It 3.3
- The restaurant ops stack, bought once: the food-safety diary, the menu into the till, and the review you ask for
- Hotel inspection checklists: what an iAuditor-style form app does, and what a register does instead
- iAuditor alternative for hospitality: room, kitchen and fire checks on software you own, not per seat per month
- What's new in Own It 3.1
- What a Six-Person Café Pays for Software Every Year — Line by Line
Also covered in: Per Seat or Per Site? The Food-Safety Software Pricing Question That Decides Your Bill · From spreadsheet to system: when a business tool pays for itself · Rent vs. own: the real 3-year math of business SaaS.
More about Safora
Replace the paper food-safety diary with auto-flagged deviations and a PDF and CSV export for any date range.
The problem it solves
Food businesses keep daily records such as fridge and freezer temperatures, cooking and reheating temperatures, cooling times, delivery checks, cleaning schedules and opening and closing checklists. Safora records all six. Most still use a paper diary that gets coffee-stained, falls behind, and is a scramble to find when an inspector walks in. Paper has no way to flag a fridge that ran warm, and no way to prove a corrective action was taken.
- Paper diaries that fall behind and go missing on inspection day
- No proof that a corrective action was taken for an out-of-range reading
- No at-a-glance view of a month's checks
Every feature
- Chases the breach nobody closed. An out-of-range reading whose corrective action nobody verified is the row an inspector opens the book on. After a grace period you set, Safora emails the manager exactly once per breach — by button or by cron — and verifying the action is what stops the email.
- A closed day is not a missing record. Sign a day off as closed, with a reason, and it stops reading as red on the compliance calendar. Closing a day leaves an unverified deviation red: an unverified deviation stays red whatever the sign-off says, and the reason travels into the audit PDF.
- Automatic deviation flagging. An out-of-range reading cannot be saved without a corrective action, so every deviation has a recorded response.
- Green/amber/red checks calendar. See which days had every check done and every reading in range, driven by real rules for checks done and readings in range.
- Six record types. Covers fridge/freezer/hot-hold temperatures, cooking/reheating core temps, cooling logs, delivery checks, cleaning, and opening/closing checklists.
- Manager daily sign-off. A manager signs off each day's records with notes attached.
- Audit-ready export. Export a printable PDF pack and a CSV for any date range to share at an inspection.
- Installable mobile app (PWA). Add it to a phone or tablet home screen straight from the browser — a full-screen app served from your own server, with no app store involved. Business data is not stored offline on the device; what you see is read live.
- The whole inspection folder. Your HACCP plan, allergen matrix, staff training and certificates beside the temperature diary, and all of it at the end of the audit PDF.
- Recall-ready deliveries. Record product, batch and use-by at the delivery check; when a recall notice arrives, search the batch and see when it came in and who checked it.
- A morning digest, if you want one. One email a day with the checks due and anything left open. Off until you switch it on.
- Updates from inside the app. The Updates page installs a new release with your license key: Ownware's signature is checked, a backup is taken first, and the app puts the previous version back by itself if the update is interrupted or the database step or start-up check of the new version fails. It never checks by itself.
- Backups by themselves. Automatic backups, an optional copy to S3-compatible storage you own, and a weekly check that the latest backup reads back. The Health page names anything that needs attention.
- Own It 4.0.1 — fixes and an up-to-date manual. For Safora, 4.0.1 fixes an installer that had lost its styling and a command-line update that ended in an error after putting the previous version back. Its manual, FAQ and QUICKSTART now cover everything 4.0 added, including two Nginx rules that keep the data folder private. Your license covers it: press Check for updates on the Updates page, or download it from your order page.
- Own It 4.0.2 — the installer opens on every host. For Safora, 4.0.2 fixes a fresh install on an Apache host: the one-page setup at /install/ looped back to itself and never opened, and now it opens. Your license covers it: press Check for updates on the Updates page, or download it from your order page.
Release notes in full
- Own It 4.1: client installations and your other tools. For Safora, 4.1 makes two changes that every app gets. An Extended license bought from October 4, 2026 covers up to ten client installations, one per client project: hand each one over to the client or host it for them, with the client's logo and colors from the app's branding settings. The API reference now shows how to connect Safora to Zapier, Make or n8n, using its own webhooks and API key. Your license covers the update: press Check for updates on the Updates page, or download it from your order page.
- Own It 4.0: it updates and backs itself up. For Safora, 4.0 means updates from inside the app: the Updates page checks for a new release with your license key, verifies Ownware's signature, takes a backup and puts the previous version back by itself if the update is interrupted or the database step or start-up check of the new version fails. A new install can start with a sample business and remove it in one click; backups run by themselves, with an optional offsite copy and a weekly check that the latest one reads back; and the Health page says whether the install is looking after itself.
- Own It 3.3: the import preview tells the truth. The equipment import's preview used to count a fridge whose minimum is above its maximum as ready, and the import then skipped it. Now the preview shows it as skipped before you confirm.
- Own It 3.2: the whole inspection folder. For Safora, the 3.2 wave put the rest of the inspection folder beside the temperature diary: your HACCP plan, an allergen matrix, staff training, certificates with their expiry dates, and deliveries recorded with product, batch and use-by, with a recall log. The audit PDF now ends with all of it, the day view marks a checklist ticked unusually fast so the manager signing off can ask, and a morning digest of the checks due is off until you switch it on.
- Own It 3.1: it writes to the people you serve. The 3.1 wave gave the catalog a way to reach the other side of the transaction: counterparty email through your own SMTP server, calendar feeds your own calendar subscribes to, attachments filed where the paperwork belongs, and export presets other people's software imports. Each outbound feature ships switched off and runs on your own credentials; a failed send is recorded, and the action that triggered it stands. What this app gained is listed at the top of this section.
- Own It 3.0: works for your AI, not just for you. Scheduled checks say this check, this often, by this time — and a check counts as done because a reading exists, never because somebody ticked a box; a check counts as done only when a reading exists, not when a box is ticked. Subscribe to the due list from Outlook, Google or Apple Calendar. A manager can confirm each corrective action afterward, several at once in one step.
- Own It 2.0: API, 2FA, backups, dark mode. Safora 2.0 adds the 2.0 owner layer. Upgrade by replacing the files — the database migrates itself, and it is still the same one-time purchase.
Browse self-hosted: Compliance software · Restaurant & café software · Hotel & hospitality software