PRICING BUILT AROUND YOUR OPERATION

Flexible Pricing for Verified Workforce Operations

Kelsor Verify is designed around a modular commercial model so your organization can license the workforce capabilities it needs without paying for a rigid, one-size-fits-all workflow.

Final pricing is provided based on workforce size, licensed modules, operational requirements and usage factors. No public price is shown while packaging and unit economics remain under validation.

  • ✓ Modular commercial structure
  • ✓ Licensed is not the same as enabled
  • ✓ Security is never an optional add-on
COMMERCIAL MODELNo public price
01
Core PlatformFoundation for workforce operations
+
02
Active WorkforceCommercial sizing based on active use
+
03
Licensed ModulesLocation · Safety · Evidence · more
+
04
Usage FactorsStorage, messaging or evidence volume when applicable

Exact commercial terms are defined during quoting and may evolve as Kelsor Verify validates packaging with real customers.

A MODULAR COMMERCIAL MODEL

Pay for the operational capabilities your organization actually needs

Kelsor Verify is not designed as a single rigid bundle that forces every organization into the same workflow. Commercial access is organized in broad modules, while policies determine how those capabilities participate in each Site, Job, Role or employee context.

WHAT SHAPES YOUR PRICE

Four factors influence the commercial configuration

Kelsor Verify’s planning model combines a platform foundation, workforce scale, licensed modules and variable usage where it creates real infrastructure or service cost.

01

Platform Foundation

The core platform provides the organizational and workforce foundation needed to operate Kelsor Verify.

  • Organization and user administration
  • Employees, Sites and Jobs
  • Basic scheduling
  • Attendance
  • Core audit and structural security
02

Active Workforce

Commercial sizing is intended to reflect employees who actively participate in the platform rather than treating every historical record as the same billing unit.

  • Designed around active use
  • Supports growing field teams
  • Contractual definition to be finalized
  • Historical records governed separately
03

Licensed Modules

Organizations can license additional operational capabilities according to the problems they need to solve.

  • Location
  • Safety
  • Evidence
  • Incidents and Communications as available
04

Usage Factors

Some capabilities can create variable infrastructure or provider costs and may participate in pricing when applicable.

  • Evidence storage
  • Package generation and egress
  • Messaging volume
  • Retention or other high-usage services

PLATFORM & MODULES

Start with workforce operations, then add the controls you need

The commercial structure is intentionally broad. Kelsor Verify avoids turning every individual capability into a separate micro add-on.

CORE PLATFORM

Workforce operations foundation

Foundation

Core is the operational base for managing employees, Sites, Jobs, schedules and attendance.

EmployeesDepartmentsSitesJobsBasic SchedulingAttendanceCore AuditAdmin & Settings

LOCATION

Verify location when the workflow requires it

Location capabilities can support Site verification and work-event context without making continuous tracking the default.

  • GPS
  • Geofence
  • Device controls
  • Photo verification

SAFETY

Apply work authorization and pre-work requirements

Safety capabilities connect requirements to the work context before an employee is authorized to proceed.

  • Work Authorization
  • Safety Gate
  • Induction
  • Questions
  • Qualifications
  • Certifications

EVIDENCE

High-value module

Preserve critical workforce history in a form that can be checked later

Evidence is more than advanced audit. It combines versioned history, cryptographic integrity, independent seals and verification workflows for materially relevant workforce events and corrections.

  • Advanced Audit & versioned corrections
  • Tenant-scoped Integrity Ledger
  • Cryptographic hash chaining
  • Daily / periodic independent seals
  • Evidence Packages with manifests and hashes
  • Verification Portal

Designed for organizations that need more than editable timestamps — they need a verifiable history of what was recorded and what changed.

INCIDENTS

Document operational and safety incidents

Incident management expands Kelsor Verify beyond attendance when a business needs structured documentation of what occurred.

  • Accidents
  • Near Miss
  • SOS
  • Evidence uploads
  • Corrective Actions
MVP+ / availability by phase

COMMUNICATIONS

Deliver operational messages through configured channels

Communications can support alerts and operational workflows through external delivery channels when licensed and enabled.

  • Email
  • SMS
  • WhatsApp
  • Push
  • Webhooks
MVP+ / availability by phase

BUSINESS

Connect verified work to commercial operations

Business capabilities are planned to convert approved workforce information into useful customer and billing workflows without turning Kelsor Verify into a general ERP.

  • Customers
  • Contracts
  • Rates
  • Verified Billable Hours
  • Invoice Drafts
Later phase

EVIDENCE AS A HIGH-VALUE MODULE

Not just audit logs. Verifiable history backed by cryptographic integrity.

For organizations where workforce records may later need to support factual review, the Evidence module adds a deeper integrity and verification layer around materially relevant events.

01Critical EventAuthorization · location · safety · attendance · incident · correction
02Audit & VersioningActor · timestamp · original value · correction · reason
03Hash ChainCritical events can be linked through cryptographic integrity references
04Independent SealA periodic reference can preserve the reached ledger state outside the ordinary operational path
05Evidence Package & VerifySelected records, manifests, hashes, ledger data and seals can be checked later

WHAT IT CAN COVER

Critical workforce events, not every click

The integrity layer is designed for materially relevant events such as work authorization, relevant location results, safety checks, Clock In, Clock Out, incidents, important notifications and approved corrections. It is not intended to cryptographically record routine page views or harmless interface activity.

WHAT AN EVIDENCE PACKAGE CAN BRING TOGETHER

Operational records plus verification context

Depending on scope, an Evidence Package can include attendance, location, safety, incidents, audit history, ledger records, seals, photos, documents, SHA256SUMS and verification metadata.

WHAT THE BUYER IS REALLY PAYING FOR

Stronger factual review when records matter

The value is not the hash algorithm itself. The value is preserving a traceable history in which relevant changes remain reviewable and later inconsistencies can become detectable.

Important claim boundary. Verification can support checks for consistency against available hashes, manifests, ledger information and seals. Kelsor Verify does not claim that records are impossible to alter, automatically legally admissible or guaranteed to prove every underlying fact.

LICENSED ≠ ENABLED

Buying a capability does not force it into every employee workflow

Kelsor Verify separates commercial entitlement from operational activation. A module can be available to the organization without being active everywhere.

Policies then determine whether an enabled capability applies to a particular Site, Job, Role or employee context.

01LicensedYour subscription permits the capability.
→
02EnabledYour organization decides to activate it.
→
03ApplicablePolicy determines when the control participates.

SECURITY IS STRUCTURAL

Core platform security is not sold as an optional add-on

Business modules can be licensed selectively. Structural security cannot. A customer should not be able to turn off foundational controls in exchange for a lower price.

✓

Tenant Isolation

Organization boundaries remain part of the SaaS security model.

✓

Authorization

RBAC and server-side access controls remain structural.

✓

Core Audit

Critical actions maintain baseline auditability.

✓

Secure Sessions

Session protections are part of the platform security baseline.

✓

Encryption & TLS

Production security requirements apply independently of modules.

✓

Backups & Rate Limiting

Operational resilience and abuse controls are not optional.

DIFFERENT OPERATIONS. DIFFERENT CONFIGURATIONS.

The right package depends on how your field workforce operates

These examples illustrate module combinations, not fixed public plans or final commercial tiers.

FIELD ATTENDANCE

Time and attendance across Sites

For an organization that primarily needs employees, scheduling, attendance and basic Site operations.

Core

LOCATION-AWARE OPERATIONS

Attendance with Site verification

For businesses that need to associate relevant work events with authorized Sites or geofence policies.

CoreLocation

CONTROL + SAFETY

Work authorization before Clock In

For operations where certifications, Safety Gate or pre-shift requirements determine whether an employee may start work.

CoreLocationSafety

VERIFIABLE OPERATIONS

Workforce records with verifiable integrity

For organizations that need more than standard audit logs: versioned history, cryptographic integrity chains, independent seals, Evidence Packages and verification workflows for critical workforce events.

CoreLocationSafetyEvidence

PRICING TRANSPARENCY

Why there are no public prices on this page yet

Kelsor Verify is still validating commercial packaging, unit economics and the contractual definition of active workforce usage. Publishing numbers before those decisions are closed would create false precision.

The current objective is to quote customers based on their real workforce model and use those engagements to validate a sustainable structure before publishing standard prices.

NOT YET FIXED

  • Final public price points
  • Definitive packaging tiers
  • Trial duration and limits
  • Contractual Active Employee definition
  • Retention differences by plan or sector
  • Variable messaging and storage thresholds

HOW TO GET PRICING

We first understand your workforce operation

A useful quote starts with the operational problems Kelsor Verify needs to solve, not with adding random features to a cart.

01

Workforce

Understand team size, roles and how many workers actively use the platform.

→
02

Operations

Review Sites, Jobs, scheduling, attendance and field-work requirements.

→
03

Modules

Identify which commercial modules actually solve the operational need.

→
04

Usage

Estimate messaging, evidence, storage or retention needs when relevant.

→
05

Proposal

Build a commercial configuration around the operation.

FREQUENTLY ASKED QUESTIONS

Kelsor Verify pricing FAQ

How much does Kelsor Verify cost?

Kelsor Verify does not currently publish fixed public prices. Commercial proposals are based on workforce scale, licensed modules, operational requirements and relevant usage factors while the final pricing and packaging model is being validated.

Is Kelsor Verify priced per employee?

Workforce scale is expected to be one component of the commercial model, but the final contractual definition of an Active Employee has not yet been fixed. Pricing is also expected to reflect modules and applicable usage factors.

Do I have to buy every Kelsor Verify module?

No. Kelsor Verify is modular by design. Organizations can license broad capability modules according to operational need instead of being forced to use every available function.

What is the difference between Licensed and Enabled?

Licensed means the organization’s subscription permits a capability. Enabled means the organization has chosen to activate it. An enabled capability still participates only when the applicable policy and workflow require it.

Is security a paid add-on?

Foundational platform security is not treated as an optional commercial add-on. Tenant isolation, authorization, core audit, secure sessions, encryption where applicable, backups and rate limiting belong to the structural security baseline.

What does the Evidence module add beyond Core Audit?

Core Audit provides baseline reviewability for critical actions. The Evidence module adds deeper integrity and verification capabilities, including versioned corrections, a tenant-scoped Integrity Ledger, cryptographic hash chaining, independent seals, Evidence Packages and verification workflows for materially relevant workforce events. It is not designed to hash every click or page view.

Can we start with Core and add modules later?

The modular architecture is designed to support adding licensed capabilities over time without forcing unrelated modules into the workflow. Exact commercial upgrade terms will be defined in the applicable proposal or subscription terms.

Will disabling a module delete our historical records?

Losing or disabling access to a module should block new operations where applicable, but it is not designed to silently destroy previously generated history. Historical access remains subject to retention, permissions, export rights and contractual obligations.

Does Kelsor Verify offer a free trial?

Trial duration and limits have not yet been finalized. If a trial or pilot is available for your organization, the scope and conditions will be explained before onboarding.

Are Incidents and Communications available in every package?

Incidents and Communications are planned as modular capabilities introduced according to product phase and customer need. Availability should be confirmed as part of the current commercial proposal.

How do I get a Kelsor Verify quote?

Book a demo or contact sales. The quoting process reviews workforce scale, Sites and Jobs, operational requirements, modules and relevant usage so the commercial configuration reflects the way your business actually works.

BUILD THE RIGHT CONFIGURATION

Tell us how your field workforce operates.

We will help map your operational needs to the Kelsor Verify modules that make sense for your organization.

Scroll al inicio