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.
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.
Integration logic lives in plugins. Plugins are triggered by files, schedules, API calls or other plugins, and their output routes automatically to subscribers.
Row-level isolation with a tenant ID on every entity and global query filters enforced by the ORM. One database, many customers, no leaks.
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.
Workflows are directed acyclic graphs of trigger, action, condition, transform, delay and output nodes. Validated for cycles and reachability, executed in topological order.
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.
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.
Live engine health, throughput and a streaming log in the browser. Message queue with status filters, retry, and retention cleanup on a schedule.
Clean Architecture: the domain has zero dependencies, the application layer speaks CQRS, and infrastructure is where Azure lives.
Entities, value objects, events, repository contracts. No dependencies.
CQRS commands and queries with validation, logging and tenant pipeline behaviors.
EF Core, interceptors for audit, tenant and soft delete, AI providers, Azure services.
REST and hubs, background services, and the Blazor console. Plus a plugin SDK for partners.
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.
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 platform | CORE Engine |
|---|---|
| .NET Remoting callbacks | REST API + SignalR hubs |
| SQL stored procedures | EF Core 10 with compiled queries and migrations |
| Manual threads and thread pools | Channels, background services, async end to end |
| Windows Service on a box | Azure App Service or Container Apps |
| XML messages | JSON envelope, XML kept for backward compatibility |
| Plugin DLLs dropped in a folder | NuGet-packaged plugins and a marketplace catalog |
| Single tenant | Row-level multi-tenancy on every entity |
| Windows Forms manager | Web-based visual workflow designer |
| No AI | Natural-language workflow creation and intelligent routing |
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