Permora

Every permit expiry and inspection date across your jobs, on one board and in your own calendar — bought once for the whole crew.

The problem it solves

Electrical, plumbing, HVAC, and general contractors juggle permits and inspections across every active job — and the tracking usually lives in a truck-cab notebook or a spreadsheet. A missed re-inspection stalls the job; an expired permit can mean re-applying and re-paying. Construction-management SaaS solves this as a side feature, priced per user, per month, forever.

• Inspection dates and permit expiries scattered across jobs, with no single alert board
• Failed inspections that need a re-inspection nobody scheduled
• Per-user monthly SaaS pricing for what is, at its core, structured record-keeping

Every feature

• The permit itself, on the permit record. PDFs up to 10 MB — the actual permit, the inspection report — stored under a minted name, decided by the file's bytes, and served back with the recorded type. The file picker says "photo or report" because that is what arrives.
• Calendar feeds you can revoke. Expiries and inspections as token-guarded .ics feeds your calendar subscribes to — and a revoke button per feed, so a contractor who left stops seeing your schedule immediately. Rotating and revoking are separate acts, as they should be.
• Jobs by trade. Organize work as jobs — electrical, plumbing, HVAC, or general — each with site address, client, and status.
• Permits per job. Track each permit's AHJ/jurisdiction, type, number, application/issued/expiry dates, fee (kept in exact cents), and status.
• Inspections with one-click re-inspection. Schedule inspections per permit with type, date, inspector, and result — and turn a failed or partial result into a linked re-inspection in one click.
• Exact date-math alert board. Overdue inspections, permits expiring in configurable 60/30/7-day windows, and active jobs with no next inspection scheduled — all computed exactly, leap-year and DST-safe. Alerts on the dashboard, and by email once a day to the office and each job's lead.
• Per-job PDF report. A dependency-free PDF of the full permit and inspection history for any job — for the client, the GC, or your records.
• Hardened CSV exports. Permits and inspections export to spreadsheet-safe CSV, hardened against formula injection, with fees kept numeric.
• 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.
• Alerts that reach the truck. Once a day, one email to the office with every permit about to lapse or already expired, tomorrow's inspections, overdue inspections, and live jobs with nothing booked. Name a job lead and they get the same email for their own jobs. Nothing goes on a quiet day, and everyone has a stop link. Off until you switch it on, through your own email server.
• Pull-by dates. Record the date a permit has to be pulled by; until it is issued it is in the daily alert, and a passed one stands out.
• AHJ comments and corrections. Log what the plan reviewer or inspector asked for, close each one with how it was addressed, and get a nudge on the follow-up day.
• Your own checks before the inspector. Saved check lists for a rough-in or a final, ticked off on the inspection; the evening before, the alert says how many are still open.
• Jobs from Jobora. Run jobs in Jobora? Bring them into Permora once each, with the site address, so every permit starts from the job.
• Get permit deposits back. Record the deposit a permit leaves with the AHJ and the day the work finished. Thirty days later (you choose), Permora reminds you to request the final inspection, or, once it has passed, to ask for the refund. Closed jobs included.
• 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 Permora, 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 Permora, 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 Permora, 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 Permora 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 Permora, 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.4: the jobs import keeps its permit dates. The jobs import's preview used to count every row with a name as ready, and an expiry that is not a real date was dropped without a word. Now the preview runs the import's own checks, and such a date is refused and named.
• Own It 3.3: a reminder to get the permit deposit back. 3.3 is the detail that decides whether a tool fits a working day. For Permora, it is the permit deposit: record what the AHJ holds and the day the work finished. Thirty days later (you choose), Permora reminds you to request the final inspection, or, once it has passed, to ask for the refund, closed jobs included.
• Own It 3.2: the permit alerts reach the job lead. The 3.2 wave sent reminders out in your own name. For Permora, that meant one email a day to the office, and to each job lead for their own jobs, listing every permit about to lapse or already expired, tomorrow's and overdue inspections, and live jobs with nothing booked. Pull-by dates, AHJ comments closed with how each was addressed, your own checks before the inspector, and jobs brought in from Jobora came with it.
• Own It 3.1: the paperwork on the record. The 3.1 wave gave the catalog ways to reach the other side of the transaction. For Permora it meant the permit document on the permit record and calendar feeds your own calendar subscribes to, each one revocable. Permora emails no one outside your team.
• Own It 3.0: works for your AI, not just for you. MCP tools read permits and inspection histories, pull the expiry report, record permits, book inspections and record findings — and an inspection is decided once: the re-inspection chain is built by the same function the button calls, so an agent cannot spawn a follow-up from a passed inspection.
• Own It 2.0: API, 2FA, backups, dark mode. Permora 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.