AAbout us

An engineering company

RIVER KG builds and operates software systems. We work directly with the teams who will run those systems, and we limit our claims to what we can demonstrate in code, infrastructure, and documentation.

Introduction

Our work covers custom software development, cloud and platform architecture, data engineering, security engineering, and long-term technical operation. Engagements range from a single service rebuilt inside an existing estate to a complete platform designed, delivered, and handed over.

We are deliberately narrow in what we take on. We do not sell licences, resell hardware, or operate as a staffing agency. Each project is scoped, designed, and delivered by engineers who remain involved through release and operation.

BMission

To build software that organisations can understand, operate, and change without depending on the people who wrote it.

CValues

Four commitments

Accuracy
A description of a system is only useful if it matches reality. We correct documents rather than defend them.
Restraint
Fewer components, fewer dependencies, fewer abstractions than the problem seems to invite.
Transparency
Risks, unknowns, and mistakes are reported when they are noticed, not when they become visible.
Durability
Code and infrastructure are written for the person who will read them in three years.
Schematic technical drawing of cloud regions and server nodes connected by measured lines
Figure A — System boundary sketch

DEngineering philosophy

How we think about systems

Boundaries before features

The first design question is where responsibilities end. Systems with clear boundaries can be changed in parts; systems without them must be changed entirely.

Data model as the contract

Interfaces change often, data outlives them. We invest most of the modelling effort in schemas, constraints, and invariants that keep records meaningful.

Failure as a design input

Timeouts, retries, partial writes, and dependency outages are described during design. Behaviour under failure is specified rather than discovered.

Automation where it is verifiable

We automate build, test, deployment, and infrastructure provisioning — steps whose correctness can be checked. Judgement stays with people.

EWorking principles

Practical rules

  • 01Scope is written down, including what is explicitly excluded.
  • 02Estimates are ranges with the assumptions behind them stated.
  • 03Every change enters the main branch through review and automated checks.
  • 04Environments are reproducible from configuration held in version control.
  • 05Credentials and infrastructure accounts remain owned by the client.
  • 06Open questions are tracked visibly instead of resolved by assumption.

FQuality standards

What quality means here

Testing
Unit tests for logic, integration tests across boundaries, and regression tests written from real defects.
Review
Changes are read by another engineer, with attention to failure paths, data migration, and access control.
Observability
Structured logs, metrics, and traces added while the feature is built, with alert thresholds agreed in advance.
Documentation
Architecture decisions, runbooks, and environment setup maintained in the repository next to the code.
Performance
Response and throughput budgets defined per interface and measured under representative load.
Accessibility
Semantic markup, keyboard operability, and contrast requirements treated as functional criteria.

GCollaboration approach

Working with client teams

Shared repository
Client engineers have access from day one and can read every commit and pipeline run.
Regular review
Short recurring sessions built around working software in a real environment.
Written decisions
Each significant choice is recorded with context, alternatives, and consequences.
Handover by default
Knowledge transfer is continuous, so that support does not depend on our availability.
Engineers reviewing an ingestion and service architecture drawn across a large office whiteboard
Figure B — Joint architecture review session

HCompany facts

Verified details only

Legal name
RIVER KG
Working language
English
Focus
Software & infrastructure

We do not publish employee counts, client lists, certifications, or founding dates on this website. Any such information is provided directly and only when it can be verified.

IContact information

Details

Company
RIVER KG
Website
riverkg.com