Logo Netsis 3

The Netsis family (acquired by Logo) remains a distinct ERP lineage with its own installed base — particularly strong in certain regions and manufacturing segments — and its own integration story.

Why agents care

• Integration: the classic surface is NetOpenX (historically a DLL-based interface, with service wrappers in newer deployments) rather than the Logo Objects layer used by Tiger/GO. An agent product targeting "Logo customers" is really targeting two integration stacks, not one.
• Practical consequence: treat Netsis as a second adapter in any multi-tenant agent architecture — same use cases, different plumbing. Teams that discover this mid-project lose weeks.

Boundaries

Version and deployment variance across the Netsis base is wider than in the Tiger/GO world; integration discovery per customer is a real work item, not a checkbox.

Related: Integration Surfaces — How Agents Read and Write Logo · Logo Tiger 3.