j-Platform represents Logo's move from its traditional client-server architecture to a modern web + cloud architecture. Java-based, microservice-architected, with web and mobile access. But it's still in a maturing phase and doesn't offer function equivalent to that of current Tiger 3 users.
01. Technical Architecture
j-Platform is Java-based and uses a RESTful API architecture. The web interface is developed with Angular, and the mobile apps are native. Microservice deployment with Docker and Kubernetes.
02. Cloud and On-Premise Installation
Two options:
- Logo Cloud: SaaS on Logo's own cloud infrastructure
- Private Cloud / On-premise: on your own server
The cloud SaaS uses a subscription model, on-premise a perpetual-license model.
03. Module Scope
As of 2026, the modules available in j-Platform: accounting, current accounts, stock, sales, purchasing, basic production. Not parallel to all modules in Tiger 3; some special modules (payroll, advanced production) are limited.
04. Migration Path
Logo offers migration tools for moving from an existing Tiger 3 or Netsis to j-Platform. But full data parity often requires additional development.
05. Who Is It For?
j-Platform suits these profiles: those looking for a new ERP (not existing users), those wanting a modern interface and mobile access, those with heavy multi-branch/remote work. For existing Logo users, migration may still be premature.