Skip to main content

Engine map

Eleven engines, one system

In Pipeline-E's CORE, an engine is a module: it owns its own screens, responsibilities, and delivery pace—so licensing can move faster than finance, for example—while staff and the public still sign into one product. That separation limits ripple effects when one area changes. Each engine can scale its workload independently as demand grows.

For data, an engine may use the shared CORE database with strict boundaries between engines, or use its own database when your agency needs stronger isolation, compliance firewalls, or different backup and retention rules—connected back through the same supported integration patterns.

Honeycomb view on the homepage

Engine list