Skip to main content

Portfolio roadmap · verified 11 August 2026

Direction made visible. Dates earned by release evidence.

This roadmap explains portfolio sequence and current evidence. It is not a promise that every implemented capability is commercially released, and it does not assign dates before supportable scope exists.

Focused products

Four entry points, four honest stages.

Kelavon Tasks

Structured task and audit management

Available

Released and obtainable now.

Details

Kelavon Compare

Evidence-linked document comparison

In development

Active implementation; not offered for operational use.

Details

Kelavon Pallet

Pharmaceutical pallet planning

Early access

Working software offered to a limited group with stated limitations.

Details

Kelavon Review

Evidence-led batch review

Design partner

The workflow is being completed with selected customers.

Details

Kelavon Monitor

Regulatory and literature monitoring

Early access

Working software offered to a limited group with stated limitations.

Details

Active suite proof

Depth is concentrated where real operational models already exist.

Kelavon Quality

A bounded quality workflow is the recommended first enterprise design partnership: begin with quality events and follow-up, then expand only where evidence and deployment support the next step.

Review capability status

Kelavon Life Sciences

Quality and regulatory foundations are the strongest suite proof. Safety, Review, Pallet, Monitor and controlled-output work create bounded entry points at different stages.

Review capability status

Kelavon Retail

Store-edge POS, inventory, purchasing, customers, employees and reporting have meaningful software proof. Hardware, fiscal and platform support remain release gates.

Review capability status

Future suites

Reserved architecture, not empty products.

Commerce, People and Finance remain public portfolio direction. Each needs a validated buyer, bounded first workflow, supported jurisdiction and an evidence-backed release sequence before deeper product pages or pricing appear.

Kelavon Commerce

A future suite for catalogue, orders, fulfillment, returns and customer operations.

Catalogue · Orders · Fulfillment · Returns · Customers

Kelavon People

A future suite for employee, organization, responsibility and workforce workflows.

Employees · Organization · Onboarding · Leave · Training relationships

Kelavon Finance

A future suite for ledger, payables, receivables, cost control and reporting.

Ledger · Payables · Receivables · Cost centres · Financial reporting

Release discipline

Code completion does not change the badge by itself.

“Available” is reserved for an offer a customer can actually obtain, operate and get support for under current published terms.

  • A supported build or deployment package exists
  • Security and data behavior match the published claims
  • Commercial terms, support ownership and recovery paths are ready
  • Qualification dependencies and customer responsibilities are explicit
  • The public status is reviewed against the actual release state

Influence the sequence

A concrete workflow is more useful than a roadmap vote.

Describe the decision, evidence, handoffs, current tools and deployment constraints. That is how a planned area becomes a bounded design-partner offer.