The Processor

The engine that runs your digitised processes.

A production-grade automation runtime. Event-driven, retry-aware, fully audited. Reads signed events from your systems, executes the right actions, writes a complete trail of every step. Included with every engagement that digitises a process — and bound, by design, to the specification it runs.


01 / What It Does
What it does

One runtime. Every workflow.

The Processor is the layer between your systems — CRM (Customer Relationship Management), billing, product backend, internal databases, messaging — and the documented processes you want them to follow.

Absorbs the work spikes

When 80 customers all hit a renewal date the same week, the Processor queues every renewal, processes them through workers in parallel, and your team never sees the surge.

Never loses work

A third-party API (Application Programming Interface) hiccup doesn’t lose a job — it gets retried, automatically, until it succeeds or escalates to a human. Audit logs prove every step.

Tells you before customers do

A separate watchdog monitors queue depth, failure rates, and downstream API health. You hear about a problem on Friday morning, not from a customer support ticket on Monday.


02 / Architecture
Architecture

Event-in. Action-out.

The Processor is built around the same architectural pattern that powers high-throughput payment systems and message brokers. Events come in from anywhere; actions go out to everywhere; in between, a queue and a worker fleet absorb spikes, isolate failures, and never lose work.

EVENT SOURCES Your CRM Signed webhooks · real-time Your internal services Encrypted job requests Scheduled triggers Daily · monthly · quarterly QUEUE Signed · deduplicated Nothing dropped WORKER FLEET Worker 1 — service A Worker 2 — service B Worker 3 — service C … scales horizontally ACTIONS Your billing Create · update · sync Your CRM Mirror · enrich Notifications Email · alerts AUDIT LOG · OBSERVABILITY · RETRY · ALERTING Every job’s input, output, and timing recorded · Health monitor watches the runtime · Operations are zero-downtime
The Processor receives events, queues them, executes them through workers, and writes a full audit trail of every step.

03 / How Services Get Built
What you actually own

One plain-language definition becomes the running system.

Every process NordOps digitises for you is captured in a single file, written in plain language — the steps, decisions, and rules that make up how the process works. It isn’t documentation sitting next to the system; it’s the definition the system is built from. Change the definition, and the system is rebuilt to match. Three things follow:

01 · Definition Process definition

One plain-language file per process: the steps, decisions, integration points, business rules, and what’s deliberately out of scope. The single source of truth.

02 · Generation The Processor builds it

Reads the definition as its brief and builds the service that runs it — doing exactly what the definition allows, and nothing more.

03 · Runtime Service in the Processor

Plugs into the Processor and inherits queueing, retries, audit logging, monitoring, and alerts. Always true to its definition.

Want the system to do something new? Change the definition — you can take it in any direction you like. What it won’t do is act beyond what you’ve defined. It does exactly what it says on the tin: everything you ask of it, and nothing you didn’t.


04 / The Architectural Difference
The architectural difference

A development agency delivers code. NordOps delivers a system that does exactly what it says.

An agency delivers code that is allowed to do whatever the developer thought sensible at the time. Six months later, no one quite knows what the system does, and any audit of “is this following our policy?” becomes a forensic exercise.

The Processor delivers a service that stays true to its plain-language definition. When you ask how a process works, the answer is the definition — always. Changes aren’t engineering tickets handled in private; they’re edits to the definition: tracked, reviewable, and re-buildable by any capable team, including your own.

What you get

  • Documentation that cannot drift from the system — because it generates the system
  • Answers in one plain-language file, current by definition
  • Changes by editing the definition and reprocessing — not developer tickets
  • Full source ownership at handoff — the Processor, the services, the process definitions, and the infrastructure
  • 60-day build warranty included on the entire delivery

05 / What You Own
What you own at handoff

Every layer. Forever.

The Processor is included with every NordOps engagement that digitises a process. It is not a separate purchase or a hosted service. At final handoff, the full source transfers to you and you own it — the runtime, the services, the process definitions, and the infrastructure — outright.

Runtime source code

The Processor itself. Modern JavaScript, Node.js LTS (Long-Term Support). Containerised for any infrastructure.

All deployed services

One service per digitised process, generated from its definition. Plugged into the runtime, ready to run.

The process definitions

The plain-language source of truth for every digitised process — the file each one is built from. Versioned and owned by you.

Infrastructure manifests

Docker, Compose, environment templates, deployment scripts. Reproducible from a clean checkout.

The Admin Portal

Renders Process Library views, monitors service status, manages access. Standard with every engagement.

60-day build warranty

From final handoff. Bug fixes and critical vulnerability patches at no charge. Optional maintenance picks up afterwards.

See the Processor running live.

A 30-minute discovery call includes a walkthrough of the Processor at the reference deployment and a first read on which processes in your business would benefit from being digitised.

Book a 30-minute call