What Are ERP.net Apps

An ERP.net App is any application, integration, or service that connects to an ERP.net instance to extend, customize, or interact with its business data and functionality.

ERP.net Apps are the foundation of the ERP.net ecosystem.

They allow organizations, partners, and developers to create additional capabilities without modifying the core ERP.net platform.

Definition and Purpose

ERP.net Apps are external or internal software components that communicate with an ERP.net instance through its public APIs.

Each app performs a defined business or integration purpose, such as synchronizing data, automating a process, or providing a dedicated user interface.

An app:

Operates outside of the ERP.net instance, but connects to it securely
Uses the standard ERP.net APIs that are part of every instance
Is recognized by the system through a Trusted Application entity
Authenticates and authorizes through the built-in ERP.net Identity

Apps are used by businesses to adapt ERP.net to their specific needs, integrate it with other systems, or deliver tailored digital experiences.

Key Characteristics

Aspect	Description
Ownership	Apps can be developed and managed by a tenant, a partner, or published to the ERP.net Marketplace.
Access	Each app must be registered as a Trusted Application in the ERP.net instance to be recognized and authorized.
Interaction	Apps communicate with the instance using APIs that are part of the ERP.net platform.
Security	Access control and authentication are handled by the built-in ERP.net Identity and system policies.
Deployment	Apps can run anywhere - on-premises, in the cloud, or embedded in another service.
Lifespan	Apps can be enabled, disabled, or updated at any time without affecting the instance core.

How Apps Fit into the ERP.net Platform

Every ERP.net instance can connect with multiple apps.

Each app acts as an independent client that requests access to the instance, performs operations through APIs, and obeys the platform's access and auditing policies.

Conceptually:

flowchart TB
  app1([Web Store App])
  app2([Supplier Portal App])
  app3([Reporting Service])

  subgraph instance["ERP.net Instance"]
    direction TB
    idp([ERP.net Identity])
    api([ERP.net APIs])
    data([ERP.net Data])
    api --> data
  end

  app1 -->|Auth| idp
  app2 -->|Auth| idp
  app3 -->|Auth| idp

  app1 -->|API Calls| api
  app2 -->|API Calls| api
  app3 -->|API Calls| api

Each app:

Authenticates through ERP.net Identity inside the instance
Uses APIs that are part of the same instance
Reads or writes data according to its granted permissions

App Lifecycle (High-Level)

Design - define the app's purpose and functionality.
Register - create a Trusted Application entity in the ERP.net instance.
Develop - implement logic that connects to the ERP.net APIs.
Test - connect to a sandbox or test environment to validate functionality.
Deploy - make the app available to users or customers.
Maintain - update scopes, manage credentials, and monitor usage.

This lifecycle applies equally to internal tools, partner integrations, and marketplace apps.

Learn More