All products
Enterprise integration · EAI / ESB

The integration engine
for the enterprise.

CORE Engine connects your systems with sandboxed plugins, chains them into workflows, and watches every message in real time. Multi-tenant from the first line of code, Azure-native, and fluent in plain English thanks to a built-in AI assistant.

.NET 10EF Core 10SignalRAzure Service BusAzure OpenAIBlazor
300+Source files across 7 projects
19Tenant-scoped domain entities
3SignalR hubs: engine, designer, monitoring
0Build warnings. Zero errors.
Capabilities

Everything is a plugin. Everything is a message.

Integration logic lives in plugins. Plugins are triggered by files, schedules, API calls or other plugins, and their output routes automatically to subscribers.

Multi-tenant by design

Row-level isolation with a tenant ID on every entity and global query filters enforced by the ORM. One database, many customers, no leaks.

Sandboxed plugins

Each plugin runs in its own collectible load context with a hard timeout and per-plugin concurrency. Hot-reload a new version without restarting the engine. A plugin SDK for third parties, and a marketplace to publish to.

DAG workflow engine

Workflows are directed acyclic graphs of trigger, action, condition, transform, delay and output nodes. Validated for cycles and reachability, executed in topological order.

Visual designer

Drag nodes onto a canvas, wire them up, set properties per node type. Collaborative editing over SignalR, so two engineers can work the same workflow live.

Triggers of every kind

File monitors, cron and interval time monitors with skip logic, REST and API-key calls, and publish/subscribe between plugins. A guard service restarts monitors that fall into an error state.

Real-time monitoring

Live engine health, throughput and a streaming log in the browser. Message queue with status filters, retry, and retention cleanup on a schedule.

Architecture

From trigger to subscriber in one picture

Clean Architecture: the domain has zero dependencies, the application layer speaks CQRS, and infrastructure is where Azure lives.

CONSOLE & API ENGINE (WORKER) AZURE Blazor consoleDashboard · Designer · Monitoring · AI REST APIJWT + API keys · Swagger SignalR hubsEngine · Designer · Monitoring AI assistantAzure OpenAI or Anthropic TriggersFile monitorsTime monitorsAPI · Pub/Sub Message queueSQL-backed · JSON envelope ChannelsChannel<T> dispatch Plugin sandboxAssemblyLoadContexttimeout · concurrencyhot reload WorkflowsDAGtopologicalexecution Azure SQL Service Bus Blob Storage Redis cache App Service
Domain

Entities, value objects, events, repository contracts. No dependencies.

Application

CQRS commands and queries with validation, logging and tenant pipeline behaviors.

Infrastructure

EF Core, interceptors for audit, tenant and soft delete, AI providers, Azure services.

API · Worker · Web

REST and hubs, background services, and the Blazor console. Plus a plugin SDK for partners.

AI integration

Describe the workflow. Get the workflow.

The AI assistant turns a sentence like "when a CSV lands in the inbound folder, validate it, transform it to JSON and post it to the ERP" into a runnable workflow graph, then suggests optimizations once it has seen the execution history.

  • Provider switching in configuration. Azure OpenAI (classic or Foundry endpoints) or Anthropic Claude, chosen per deployment without a code change.
  • No AI SDK lock-in. Providers are called over plain HTTP, so upgrades and new vendors are a small adapter, not a migration.
  • Intelligent routing. The same models can classify and route messages that do not fit a fixed rule.
  AI Assistant
When an order CSV arrives, validate it, convert to JSON and post it to the warehouse API. Alert me on failures.
WORKFLOW · 6 NODES
File triggerValidate CSVConditionTransform → JSONHTTP outputAlert email

Saved as Order Intake. Want me to add a retry with backoff on the HTTP node?

Modernization

Built as a ground-up rebuild of a legacy ESB

CORE Engine replaces a .NET Framework 4.6.1 integration platform that ran on Remoting, stored procedures and a Windows Forms manager. Same job, thirty years newer.

Legacy platformCORE Engine
.NET Remoting callbacksREST API + SignalR hubs
SQL stored proceduresEF Core 10 with compiled queries and migrations
Manual threads and thread poolsChannels, background services, async end to end
Windows Service on a boxAzure App Service or Container Apps
XML messagesJSON envelope, XML kept for backward compatibility
Plugin DLLs dropped in a folderNuGet-packaged plugins and a marketplace catalog
Single tenantRow-level multi-tenancy on every entity
Windows Forms managerWeb-based visual workflow designer
No AINatural-language workflow creation and intelligent routing
The console
DashboardMessage queueLive monitoringWorkflow designerWorkflowsPluginsPlugin marketplaceFile monitorsTime monitorsAI assistantPublishers & subscriptionsTenants & API keys

See CORE Engine on your data.

We will walk you through the console, wire up one of your real integrations in a sandbox tenant, and talk honestly about what it would take to migrate.

info@eideinteractive.com