Pervidi is a flexible, 20-year-old configurable inspection toolkit used across FM, healthcare, oil & gas, transport, and more. Core is a finished lifting, rigging, and height-safety platform with the compliance frameworks and service-company workflow already built.
Built for Lifting Inspections. Not Configured for Them.
Pervidi is a generic toolkit you adapt to your business. Core arrives already shaped for lifting, rigging, and height-safety service companies — with LOLER, ASNZ, and ASME compliance, batch inspection, and unlimited customer portals on day one.
Which one is right for you?
A straight call. We'd rather you self-select the right fit than push the wrong tool.
Choose Pervidi if…
- You need on-premise or self-hosted deployment for regulatory or data-sovereignty reasons.
- You run a generic, multi-domain inspection program — FM, EHS, contractor audits, lifting — all in one platform, and the lifting piece is one part of a wider use case.
- AI image defect detection and voice-to-report are essential to your roadmap today, not nice-to-haves.
- You have internal teams who can invest months in configuring forms, certificate templates, and workflows for your industry.
Choose Core if…
- Your business is lifting, rigging, or height-safety inspection — and the platform should arrive ready for that.
- You want LOLER, ASNZ, ASME, and LEEA compliance frameworks pre-built, not modelled from scratch.
- You want customer-facing online equipment registers as a feature you can sell and retain accounts with.
- You inspect at field volume — hundreds of similar items per visit — and need batch capture, not 200 individual forms.
- You want to be productive on day one of implementation, not month three of configuration.
Three reasons inspection businesses switch to Core
Vertical-ready, not configurable-to-vertical
Pervidi pitches itself as a toolkit — same product across many industries with very different processes. To inspect a chain sling, harness, or crane on Pervidi you configure forms, build certificate templates, and model the compliance logic yourself. Core ships those as native objects. Chain sling, harness, fall-arrest, crane, hoist, eye bolt, shackle, and beam-clamp templates load on day one. The compliance frameworks (LOLER, ASNZ, ASME, LEEA) are reflected in form structure, certificate format, and approval levels — not findable in a template library.
The service-company motion is the product, not a use case
Pervidi can be configured to support a service-provider workflow, but it isn't built around it. Core models the full loop natively: quote → schedule → multi-branch dispatch → restrictive competency rules → on-site inspection → branded customer portal → service charges → invoice. Customers are first-class objects, not metadata on a checklist. Branches, technicians, and customer-facing reminder cadences are part of the data model, not configuration.
Faster time to value, not a multi-month configuration
Pervidi reviews emphasise customisation depth — and the substantial up-front configuration that goes with it. A new Pervidi customer is in a configuration phase. A new Core customer is running real inspections in their first week. For a service company waiting on customer-deliverable certificates, that difference is the difference between revenue this month and revenue next quarter.
Side-by-side: Core vs Pervidi
Capability, where each platform lands, and what the difference means in practice.
| Capability | Core | Pervidi | What this means |
|---|---|---|---|
| Pre-built lifting forms and certificates | Out of the box | Configure or commission | Weeks of setup saved for a lifting inspection company. |
| LOLER / ASNZ / ASME logic | Native (frameworks shape form, certificate, approval) | Must be modelled | Compliance frameworks are first-class in Core. |
| Service-company workflow | Native | Configurable | Customer-facing scheduling and billing built in. |
| Customer portal | Unlimited, included, branded | Available | Every customer of yours gets a branded portal at no per-user cost. |
| Multi-inspect batches | Native | Limited | Inspect 200 chain slings as a batch, not 200 forms. |
| Restrictive competencies | Enforced at scheduling | Tracked as data | Competency rules become scheduling constraints in Core. |
| On-premise / self-hosted deployment | Cloud only | Cloud or on-premise | Pervidi's edge for air-gapped or sovereignty-constrained buyers. |
| AI image analysis | Roadmap | Available (2024) | Pervidi has a head start here. |
| Voice tagging / speech-to-report | Limited | Available | Useful for hands-busy inspections. |
| Public Capterra / G2 review depth | Named case studies + testimonials | Small review base | Different evidence types — peer reviews vs named customers. |
Pre-built lifting forms and certificates: Weeks of setup saved for a lifting inspection company.
LOLER / ASNZ / ASME logic: Compliance frameworks are first-class in Core.
Service-company workflow: Customer-facing scheduling and billing built in.
Customer portal: Every customer of yours gets a branded portal at no per-user cost.
Multi-inspect batches: Inspect 200 chain slings as a batch, not 200 forms.
Restrictive competencies: Competency rules become scheduling constraints in Core.
On-premise / self-hosted deployment: Pervidi's edge for air-gapped or sovereignty-constrained buyers.
AI image analysis: Pervidi has a head start here.
Voice tagging / speech-to-report: Useful for hands-busy inspections.
Public Capterra / G2 review depth: Different evidence types — peer reviews vs named customers.
Pervidi packaging, pricing, and review details verified against public sources as of May 2026. Spotted something out of date? Tell us and we'll correct it.
Why Core, in five lines
The same five things matter no matter which competitor you're evaluating.
Built for the inspection service business
Quote → schedule → inspect → certify → bill is the workflow. Most competitors stop at 'inspection completed'.
Multi-region compliance in one platform
LOLER, ASNZ 2550, ASME B30, and LEEA Code of Practice ship together — not as separately purchased modules.
Unlimited customer logins
Every one of your customers gets a branded portal to view equipment and certificates — no per-portal-seat charge.
Multi-inspect for batch capture
Inspect 200 chain slings as a single batch with shared metadata. Drill into defects only.
Restrictive competencies enforced
Only certified technicians can be scheduled to certain inspection types — competency becomes an operational rule, not just a data field.
From operators who switched
“Core has modernised our business and given our customers the oversight of their legal requirements that they were looking for.”
Director, Scotia Handling Services — migrated 300+ customers onto Core in three months
Read the case studiesFAQ
Pervidi can be configured to run LOLER checklists, but it doesn't ship a LOLER ROTE certificate, lifting-specific registers, or UK regulatory vocabulary out of the box. Core ships those as native objects — the LOLER framework shapes form structure, certificate format, and approval logic by default.
See it on your data, not a generic demo
We'll show you Core Inspection against the workflow you run today — including how a switch from Pervidi would actually look on your operation.