Modernize a critical application
Recover scattered business rules, resolve differences and modernize progressively without losing business meaning.
Scope a modernization →
SPECIFICATION FIRST · AI AGNOSTIC · SECURE BY DESIGN
Keep business knowledge executable as code changes.
Modernize critical applications, build new business software and experiment with governed agents from an explicit specification. With logiCells, your business model remains a durable reference — not documentation scattered across code.
Observed — existing code
if Order.Status = Draft and Order.LineCount > 0 and Customer.IsActive then Confirm(Order) # counts lines, not whether they are valid
Make explicit
Explicit — approved rule · BR-ORD-014
ValidLine(line) := not line.cancelled and line.quantity > 0 CanConfirm(order) := order.state = Draft and order.customer.isActive and exists line in order.lines: ValidLine(line)
Execute
Executed — decision and trace
order CMD-4471 · 2 lines → CanConfirm REJECTED line 1 ....... cancelled ✗ line 2 ....... quantity 0 ✗ # the legacy code would have confirmed it rule BR-ORD-014 v3 · trace r-8f21
Illustrative example in simplified notation, taken from the running case of the modernization guide.
Progressive application modernization
New business applications
Durable executable specifications
One secure shared Runtime
USE CASES
Three entry points. One platform.
Start with a real business problem, a measurable proof, then the right deployment path.
Build a business application
Describe concepts, relationships, actions and processes as an executable model. Code and interfaces can evolve without redefining the domain.
Discuss a new application →Explore governed agents
Test agent actions bound to rules, confirmation steps and business provenance in a controlled Lab. Production performance still needs qualification.
Request a Lab demo →THE PLATFORM
A durable specification. One platform. One secure Runtime.
logiCells Platform (LP) brings business models, knowledge foundations and application execution into one architecture. Applications rely on a common proprietary Runtime foundation; published SDKs and ABIs connect existing systems and code.
The model stays executable
Concepts, relationships, rules, views, actions and processes explicitly define business behavior.
Knowledge remains governable
Conceptual structures and H-Logic are embedded in LP. Very-large-scale workloads require validation on the delivered build.
Code stays connected
Supported APIs, ABIs and SDKs connect libraries, business applications and existing systems.
THE METHOD
Legacy code is evidence, not the definition of the business.
Copying an existing system also copies its defects. Our method separates what the code does from what the business approves, and makes every difference explicit before production is touched.
Discover
Analyze code, data and execution traces to identify candidate rules, each linked to its source.
Validate
The business owner decides on concrete scenarios: behavior to keep, to correct or to retire.
Make explicit
The approved rule becomes part of the model, versioned and covered by acceptance tests.
Modernize step by step
Run alongside the legacy system, route traffic progressively, then retire the old code once the evidence is in.
HOW TO WORK WITH LOGICELLS
Choose the engagement model for your project.
LGC grants the logiCells licence. Delivery and integration can be carried out by your team or independent partners.
Enterprise team
Qualify a business scenario, run a controlled proof and deploy one or more applications under appropriate rights.
Discuss a POC →Integrators, IT service firms and independents
Design, deliver and support client applications. Keep your own services revenue; each independent application needs its dedicated Client Runtime entitlement.
Explore the integrator pathway →Software vendor / OEM
Embed supported Runtime capabilities in a third-party product. Industrial Runtime redistribution (OEM) requires a separate agreement. Running several applications on a common platform follows Standard or higher entitlements.
Discuss OEM integration →Are you a developer, introducer or integrator? Explore partner paths →
DISTRIBUTE AND REUSE
From business model to deployable application.
Reusable modules and an application’s execution rights are separate. Self-service payment and activation flows require operational validation.
Publish through the Store
Publish or acquire free and paid applications and modules subject to each component’s rights. Store checkout is a target flow and must not be treated as live until confirmed.
Direct white-label distribution
Combine models, code and modules into an identified application, then distribute it under your brand. A dedicated Client Runtime entitlement is required per independent application and end customer; activation terms must be validated.
ENTITLEMENTS AND EDITIONS
One Runtime, entitlements for every stage.
Developer for non-production development and testing; Solo for one eligible own-use production application; Client Runtime for customer deployments; Standard and above for multi-application platforms.
Developer
For individuals and teams: build, test and demonstrate without production use. One Developer certificate is planned per registered developer, with five concurrent sessions each, even on different projects. Technical enforcement remains subject to acceptance.
Understand Developer →Solo
Includes Developer and adds one production application for the holder’s own needs, where the individual or business has exactly one person, owners and employees combined.
Understand Solo →Client Runtime
One entitlement per identified application and end customer. Chargeable from the first concurrent user, without a user ceiling.
Qualify an entitlement →Standard
Multi-application platform with unlimited concurrent users. Alpha targeted for November 2026; production and support commitments require acceptance of the delivered build.
Evaluate Standard →Professional
Advanced delivery and tooling features subject to the acceptance of the actual release.
Discuss requirements →Enterprise
Enterprise scope and contractual commitments to be confirmed; initial release targeted in 2027.
Discuss your needs →Pricing and availability dates will be communicated after contracts, delivered builds, payment and activation flows have been validated.
Non-contractual pre-release: terms planned from November 2026, subject to final LGC approval and actual availability.
LOGICELLS LIBRARY
Books and guides
Browse the documents in their current working editions. The PDFs are provided without modification.
Application Modernization Guide
Recovering, structuring and operationalizing business knowledge.
Developer guides are available on the Community site →
Turn your use case into a concrete proof.
Modernization or a new application? Tell us about your current systems, business rules and the outcome you need to prove.
Distribution or partnership? Indicate the applications, end customers and distribution model you are considering.
Prefer email? contact@logicells.com