CloudCore is what we hand a new project on day one: workflow orchestration, document handling, dashboards, identity, audit trails, integrations and deployment patterns, built and operated since 2008, on Microsoft Azure. That foundation is why we can ship complex operational systems in weeks instead of quarters, and why every system we deliver is on the same production‑hardened plumbing.
COMPLIANCE ISO 27001 · POPIA information security & SA data privacy aligned
The same compartments power every system we ship. Inputs come from email, web, mobile, API and supplier portals. CloudCore’s workflow engine, document store, KPI cache and integration bus do the work. Downstream sinks are accounting systems, payment gateways, manufacturer warranty portals, IMEI registries and Azure storage.
Runs 24/7, evaluating rules, routing tasks, sending notifications, generating documents, triggering follow-on processes. A PO over threshold holds for senior approval while routine orders pass through. The engine doesn't wait for a button click.
Midnight price activation, payment-provider polling, daily/weekly/monthly reports, overdue-case monitoring. Background work runs on configurable intervals while the team sleeps.
Every invoice, PO, delivery receipt, service agreement, loan-device form and shipping label stored in Azure with a unique reference. Time-limited download links via email, SMS or push. Linked permanently to the transaction it supports.
Interactive charts and summary panels that refresh automatically in the background. Source definitions cache the numbers; filters scope by region, unit, period. Four tiers (site, manager, district, national) from the same framework.
Access via pools and business-unit hierarchies. Role-based control. MFA. Distinct Dev / Test / UAT / Live stages. Every action logged for audit and compliance. Not a permissions matrix someone configures once. It reflects the organisation's actual structure.
Xero, Pastel, SnapScan, PayGate, Apple GSX, MobiCode, Unit4, Bookeo, email, SMS, push and Google Maps, each wired in as a workflow activity with retry, not a pass‑through script. AI integration is core capability: bespoke AI tools that pre‑process documents into workflows (the Feedem invoice processor handles ~30,000 invoices a month), and AI services called inside workflows directly (Gemini powers structured paper review in our exam‑paper system). Provider‑agnostic by design.
Starting from a blank repository on a fixed‑fee project is where most enterprise software delivery goes wrong. Identity, audit, document handling, workflow orchestration and integration plumbing have to be invented before anyone can write the actual business logic. CloudCore is the answer to that problem: every Exclr8 project inherits the foundation, fully production hardened, before scope work begins.
Workflow engine, document store, KPI framework, integration bus, identity, audit, all already built and operating. Project scope shrinks to the business logic that’s actually unique to your operation.
Because the platform is in place, the first sprint produces something a stakeholder can use and react to, not documentation. Course‑corrections happen in week one, not month four.
Authentication, retries, audit trails, environment promotion (dev → test → UAT → live), error monitoring: the patterns CloudCore uses are the same ones it has used in production for over a decade.
We don’t hand the system to a third party at go‑live. The same team that designed the workflow runs it, patches it, and evolves it as your business changes. Relationships measured in years.
Every CloudCore engagement moves through the same five stages. Each stage has a clear outcome, a clear hand‑off and a clear sign‑off. We don’t disappear at go‑live: stage 5, operate, is part of every engagement by default.
New capabilities are added as discrete, testable units. The platform's own features (notifications, document management, KPI dashboards, administration) are delivered through the same architecture as custom business logic. There is no gap between "platform code" and "your code."
When we build a system for a client, we don't start from a blank page. We start from CloudCore, and spend our time on the logic that makes that client's business unique. A procurement system inherits the same workflow engine, document store and dashboard framework as an order management system or a service tracking platform. The difference is what each does with the foundation.
Neutronix: the modern .NET edition of CloudCore. Built on .NET 10 with an enhanced KPI framework, native push notifications and a refined module architecture. The default edition for new builds.
VNext: the original .NET Framework edition of CloudCore. Powers several large-scale production systems today: procurement at 1,000+ sites, multi-channel order management, device repair across countries. Stable, trusted, running 24/7.
| Neutronixmodern .NET edition | VNextbattle-tested edition | |
|---|---|---|
| Who it’s for | New builds where you want the latest runtime, native push, and the enhanced KPI framework. | Existing CloudCore deployments and clients who value the long production track record on .NET Framework. |
| Runtime | .NET 10 on Microsoft Azure | .NET Framework on Microsoft Azure |
| Module architecture | Refined modular DI, modules self-register at startup | Original modular composition, production-tested for over a decade |
| KPI framework | Enhanced source/cache model with scheduled refresh | Original KPI framework, customised per system |
| Native push notifications | Built into the platform, per-user preferences by event | Email + SMS native; push via per-system integration |
| Typical project size | From a single workflow to a multi-module enterprise platform | Multi-module enterprise systems running mission-critical operations |
| In production | XEN4 · C3 · growing portfolio | OMS (N1) · Feedem · LoveTech · long-running deployments |
30,000 supplier invoices a month across 1,000+ sites, with automated best-buy comparison, credit derivation and four-tier management dashboards.
Five order channels, automatic margin enforcement, production queuing, quality-control gates, route-planned same-day tripsheets.
Phone call to invoiced booking in under a minute, with accounting sync, payment reconciliation, QR codes and WiFi voucher generation.
Every repair from drop-off to collection. Manufacturer diagnostics, trade-in processing, 14 background processes running around the clock.
CloudCore is the business automation platform that Exclr8 builds every client system on. It is a working enterprise foundation (workflow engine, document store, KPI dashboards, security, integrations) running on Microsoft Azure, designed and maintained in Cape Town, South Africa.
The platform is CloudCore, one word. It's commonly searched as “cloud core”, “cloudscore”, “cloud core ai”, “cloudcore systems” or “cloudcore meaning”. All refer to the same Exclr8 product.
AI integration and bespoke AI tool development is a core Exclr8 capability. We deploy AI two ways around CloudCore systems: (1) as sidecar tools that pre‑process documents into the workflow. For example, our production AI invoice processor handles around 30,000 supplier invoices a month for a national caterer, pre‑allocating each line against the corresponding purchase order so the Invoice Allocation workflow surfaces only exceptions; and (2) as workflow activities called inside CloudCore directly: Google Gemini powers structured paper review in our exam‑paper management system. Both patterns are provider‑agnostic; every AI call is wrapped with retry, audit and exit conditions, so swapping a model or vendor is a config change rather than a rewrite.
CloudCore comes in two framework editions. CloudCore VNext powers production systems today. CloudCore Neutronix is the modern .NET edition with an enhanced KPI framework and refined module architecture, the default for new builds.
Microsoft Azure, in the Azure South Africa North region. Push notifications, Blob Storage, App Service, Azure Functions, SQL Database, all native Azure services. Why cloud rather than on-premise? See cloud vs on-premise.