WFD Engines

Focused software.
No monolith required.

Each WFD Engine provides a specific capability and can be licensed independently. The common design language and integration patterns make them more powerful when several are used together.

StandaloneBuy only the Engine your solution needs.
ComposableCombine Engines without turning them into one inseparable platform.
Partner readyUse them inside WFD-led, customer-led or partner-led solutions.

WFD Email Engine

Control what enters.

Ingest from custom addresses, existing mailboxes or forwarded mail. Extract attachments and linked documents, preserve useful email context and prepare files for downstream automation.

  • Existing mailbox support
  • POP / IMAP connectivity
  • Attachment and download-link handling
  • Useful sender/domain metadata
  • Document preparation and normalisation

WFD Routing Engine

Configurable workflow and orchestration.

Initiate and coordinate other Engines, third-party services and human tasks through an extensible plugin/node architecture.

  • Standalone workflow
  • Document approval
  • Process orchestration
  • Extensible node architecture
  • Planned and custom nodes

WFD Match Engine

Match imperfect data with confidence.

Combine multiple matching signals and return ranked, scored candidates so the surrounding workflow can decide whether to automate, review or escalate.

  • Configurable matching strategies
  • Multiple evidence signals
  • Ranked candidate results
  • Direct Core or optional Proxy patterns
  • Host application stays in control

WFD Accounts Engine

A reusable accounts domain.

Give applications a consistent way to work with accounts information without building a new bespoke integration every time.

  • Suppliers and master data
  • Purchase orders and lines
  • Invoices and VAT data
  • Bulk and import patterns
  • API-led integration

WFD Integration Engine

Integrate once. Add targets through plugins.

Expose one integration interface while target-specific plugins handle the details of ERP, finance, document and other systems.

  • Data and document operations
  • Target plugins
  • Reusable integration contracts
  • ERP and document system examples
  • Works independently

WFD Content Engine

One route to content wherever it lives.

Inventory and search multiple repositories, migrate content when needed, provide an optional WFD repository and make content accessible to AI through focused interfaces.

  • Existing repositories
  • Cross-repository search
  • Migration capability
  • AI-accessible content
  • Full-text and summary indexing

WFD Cardiograph

Operational visibility from cradle to grave.

Monitors present operational sensors for dashboards and reporting. The same model can extend beyond WFD components to external systems and REST APIs.

  • Near-time visibility
  • True Monitor plugins
  • Any REST API monitor
  • Personal/shared dashboard direction
  • AI-accessible operational context

The point of the ecosystem

WFD doesn't require WFD.

That sounds contradictory. It is actually the design principle.

Email Engine can use existing mailboxes. Content Engine can sit over existing repositories. Integration Engine talks to third-party systems. Cardiograph can monitor technology outside WFD. Routing Engine can orchestrate external services.

Built to fit in. Built to work together.

Standalone or together

Use the Engine the solution needs.

Licensing and solution design can start with one Engine and expand only when there is a reason to.

Talk to WFDPartner opportunities →