Product · Open source

Nexus

A clear interface that gives the whole business, not just the developers, a view of the flows between your systems. See at once if something is stuck, debug it and rerun it with one click. Under the hood, Nexus is a .NET framework that orchestrates, monitors and safeguards the processes. Open source and free for our clients.

Documentation ↗

Type: Framework for .NET (6+)
Who it is for: Developers & business
License: Apache 2.0, open source
Status: In production at clients

The interface

This is what it looks like.

A clear admin UI where the whole team can follow the flows in real time, at the desk or on a phone.

Nexus admin UI: overview of system health for jobs, queues and functions — **Overview.** System health across jobs, queues, functions and integrations, with whatever needs attention gathered at the top.

Nexus admin UI: job view with scheduled, queue-driven and on-demand jobs — **Jobs.** Scheduled, queue-driven and on-demand jobs, with status, last run and the option to restart right away.

What is Nexus?

In an e-commerce solution, events constantly trigger flows and data has to move between systems. When an order is placed it needs to go to the ERP and the OMS, to the recommendation engine and BI, and an order confirmation has to go out. Doing all of that at the moment the customer hits buy is neither sustainable nor safe, and if one step fails, that step has to be rerunnable in isolation.

Nexus is a .NET framework that takes care of everything around it: scheduling, queues, retries, error handling and monitoring. Developers get to focus on one flow at a time while Nexus holds the whole together. Whatever gets built becomes visible, monitorable and safeguarded automatically.

Visibility for the whole business

One of the strengths of Nexus is that it makes the flows visible to non-technical people too. Through the web interface anyone can log in, quickly see that the order export is failing, do basic troubleshooting themselves or rerun the job with one click. Health checks can be shown on a screen in the office, so the whole team can act the moment something does not look right.

Everything is reachable programmatically as well. Beyond the interface, Nexus exposes its functions over an HTTP API and over MCP, so AI tools and agents can inspect jobs, queues and health checks, and act when needed.

Who it is for

For development teams and architects who want to build one flow at a time and trust that the whole holds together, and for businesses that want visibility and control over their integrations without being locked in. Nexus can be embedded in an existing application and run locally with no external dependencies.

Nexus runs in production at some of the best-known e-commerce companies in the Nordics, among them Lyko, Cervera, Kjell & Company, Thule, Nordic Nest and Ark.

Core use cases

What teams use Nexus for.

Jobs & functions

Run in the background

Schedule jobs and run methods in the background with automatic retries. Scale out across several servers as volume grows.

Functions, jobs & scheduling

Queues

Handle message flows

SQL and in-memory queues with versioning. Process in batches or one at a time, with extreme throughput when needed.

Queues out of the box

Visibility

Visible to the whole business

Admin UI, HTTP API and MCP support for AI agents, health checks into Slack and Teams, and one-click reruns of failed jobs, not just for developers.

Monitoring & troubleshooting

Client quote

What clients say.

We have complex flows spanning several companies and systems, and Nexus lets us build new integrations quickly without losing control. The visual, accessible UI also means the whole team, not just the developers, can act when something does not look right.

Nexus solves our needs very well and is now an established component in our blueprint for developing new products and services where we apply the Transactional Outbox integration pattern.

Emil SvebeusCTO, Lyko

Related cases