Prophet 21's Latest Architecture Explained

Prophet 21's latest architecture introduces a middleware server that sits between clients and the database, moving business logic out of the old desktop 'fat client' and enabling API-based integration. It supports twice as many concurrent users per server as the legacy fat-client model, adds web and hybrid client options, and is optimized for deployment on Microsoft Azure.

Why Prophet 21's architecture needed an update

Prophet 21's original architecture, built around a desktop fat client, could not scale to meet the connectivity and mobility expectations distributors now face. Supply chain disruption and shifting customer expectations over the past several years pushed the platform toward a cloud-ready redesign.

The rework focused on making the system more scalable, interoperable, and accessible across devices, while keeping the distribution-specific functionality that made Prophet 21 useful in the first place.

The middleware server and what it changed

The core architectural change introduces a middleware server that acts as an intermediary between clients and the database. Business logic that used to live in the desktop fat client now runs in this middleware layer, which is the foundation for API-based integrations.

Communication between client and middleware happens over SSL, so users connect through a web connection and certificate without needing direct network access or a VPN. This middleware server also supports roughly double the concurrent users that a terminal server running the traditional fat client could handle, and larger customer bases can run multiple load-balanced middleware servers.

Web, hybrid, and desktop client options

The new architecture supports three client types, each suited to a different way of working.

Epicor is gradually retiring the desktop client: it will no longer release new versions or fixes for it, and going forward new P21 features will only appear in the web and hybrid clients. That makes migrating to the newer client types necessary both for continued support and for access to future functionality.

• Web Client: browser-based access from PC, tablet, or mobile device, no installation required
• Hybrid Client: installs like a Windows application but connects directly to the middleware server for the desktop feel with modern backend access
• Desktop Client: the legacy fat client, now being phased out of active development

New capabilities enabled by the redesign

The updated architecture unlocked several features that were difficult or impossible under the old fat-client model, most of them built around giving users faster access to Prophet 21 data outside the traditional interface.

• Enterprise Search: a single search field giving remote employees access to Prophet 21 data
• Dashboards: user-specific data pushed to smartphones, tablets, and browsers
• Business Activity Queries: point-and-click, drag-and-drop mapping of P21 data to other applications
• Epicor Virtual Agent: an AI-driven digital agent that processes commands and offers behavior-based recommendations
• Mobile Proof of Delivery: mobile tools for faster pickups and deliveries built on Epicor Kinetic Design
• TrackAbout integration: tracking for portable returnable assets like cylinders and containers used by industrial gas distributors

Deployment options under the new architecture

Customers moving to the new architecture have more than one deployment path to choose from. Epicor's SaaS option keeps the application under Epicor's management, which some customers prefer and others are less confident about.

For distributors who want cloud benefits without giving up direct control, private cloud hosting combines the new architecture with full Prophet 21 functionality and avoids the upfront hardware investment of an on-premise install. Running Prophet 21 on Azure removes the burden of maintaining servers directly and gives employees system access from anywhere.

Frequently asked questions

Is Epicor discontinuing the Prophet 21 desktop client?

Epicor is phasing it out gradually. It will not release new versions of the desktop client or issue further fixes for it, and new Prophet 21 features going forward are being built for the web and hybrid clients only. Customers on the desktop client will eventually need to migrate to retain support and gain access to new functionality.

Does the new Prophet 21 architecture require a VPN to connect remotely?

No. Connections between the client and the middleware server use the SSL protocol, so users need only a web connection and a certificate rather than direct network access or a VPN tunnel. This makes remote and mobile access simpler to set up and manage.

What is the difference between the hybrid client and the web client in Prophet 21?

The web client runs entirely in a browser and works from a PC, tablet, or mobile device with no installation. The hybrid client installs like a normal Windows application and connects directly to the middleware server, giving users the familiar desktop feel while still running on the modern architecture. Both receive new features going forward; the legacy desktop client does not.