Practice since 2019 · Calvrix Ltd since 2026

Systems
that last.

Calvrix is a platform-engineering practice. Two stacks at depth, the Microsoft enterprise stack and the cloud-native operations stack, held to one precision standard. We design, operate, modernise, and document the infrastructure beneath revenue-critical platforms.

Talk to CalvrixRead the seven-year case
// sample feed// platform.uptime.30d99.987%// payments.gateway.failoverprimary→secondary, 412ms// adr/2025-11-14split read/write ledger paths · merged// migration.dotnet.4_8 → 10in progress, service by service// kube.aks.prod.eu-west142 pods healthy// kube.eks.prod.us-east87 pods healthy// observability.coverage100% of prod paths// settlement.run.dailysucceeded · 14:02:11 UTC// post-incident.review.2025-09-22published, signed off// terraform.plan.prod0 changes · steady state
7+ yearscontinuous platform operation
Multi-storefrontcommerce platform in production
Azure · AWSmulti-cloud, hands-on
AKS · EKSkubernetes, both clouds

The work

Inputs converge. The system resolves.

Calvrix sits at the centre of an enterprise platform, where runtime, infrastructure, audit, and continuity all have to come out correct at the same time.

Most vendors split architecture from operations. We do not. The same discipline that designs the system also operates, modernises, and documents it.

Two practices · one precision standard

Two stacks. Two practices. One precision standard.

Calvrix runs two equally weighted practices, not a main line and a side line. Same engineering discipline, same documentation standard, same operating model, applied across two technology surfaces.

// Practice 01: Microsoft enterprise stack

.NET 10, EF Core, Azure-native infrastructure.

Runtime upgrades, audit-grade workflows, multi-storefront commerce, payment routing, settlement, ledger integrity. App Service, Service Bus, Key Vault, SQL, Functions: the platforms where money is the system of record.

// Practice 02: Cloud-native operations

Kubernetes, Terraform, CI/CD, observability.

AKS + EKS in production, Terraform-as-source-of-truth, GitHub Actions / Azure DevOps pipelines, OpenTelemetry, SLO-driven on-call, FinOps cost discipline. Hands-on SRE, not strategy slides.

// Modernisation: across both stacks

Move forward without breaking continuity.

Live migration from legacy .NET to modern .NET on Azure; lift-and-reshape from VMs into AKS; monolith decomposition behind a service mesh. Project model, dependency model, hosting, packaging, deployment: rebuilt while the business stays online.

// Long-term ownership: across both stacks

Architecture decisions, written down.

ADRs the next engineer can read. Runbooks the next on-call can operate. Cost attribution the next CFO can audit. Terraform the next platform team can extend. Precision before scale, applied across years.

Systems in production

Seven years. One platform. Still running.

One Calvrix anchor engagement began as a deliberately constrained build for a growing commerce business. The system was designed to fit the business stage, not inflate infrastructure spend before the business could carry it.

Seven years later, the platform is still in production, scaled to enterprise revenue, and undergoing live modernisation onto Azure-native infrastructure and modern .NET, without business discontinuity.

Multi-storefrontcommerce platform
7 yearscontinuous operation
Multi-storefrontarchitecture
Multi-gatewaypayment routing
.NET 4.8 → 10live migration in flight
Zero downtimemodernisation underway

The category we refuse

Calvrix is not a cloud reseller, not a staffing agency, not a discovery-call funnel.

We build infrastructure customers can understand, operate, evolve, and own, not infrastructure that creates dependency on us.

CalvrixCloud resellerStaffing agencyIn-house only
Architecture + operationsSame team owns bothArchitecture onlyWhoever is on the benchPossible, often understaffed
Decisions documentedADRs as standardVendor-internalNoDepends on the team
Modernisation w/o downtimeCore disciplineOut of scopeOut of scopeHigh-risk, often deferred
Continuity over years7+ year engagementsContract-by-contractPerson-by-personSubject to attrition
Audit-grade financial workflowsIn productionOut of scopeOut of scopePossible, rarely senior-led

Internal motto

Precision before scale.

Calibrate before commit. Measure before move. Get the architecture correct before scaling the system. The rule that decides how decisions get made, not what they produce.

// motto · for engineers, hires, internal docs

01

Architecture before scale.

The system must match the business stage, not the vendor's ambition.

02

Operations before handoff.

A platform is not complete until it can be operated safely.

03

Documentation before memory.

Decisions must survive the people who made them.

04

Continuity before rebuild.

Modernisation should be continuous, not catastrophic.

Origin · 2019 → 2026

Dove Solutions became Calvrix.

The practice has operated continuously since 2019. Originally Dove Solutions, a platform-engineering team building and operating long-running enterprise systems for revenue-critical workloads.

In 2026 the practice became Calvrix Ltd. The work did not change. The discipline did not change. The name now matches the discipline.

Dove Solutions founded. The anchor commerce platform begins as a deliberately constrained build: sized to the business stage, engineered to outlast it.
Cloud-native practice opens. Kubernetes (AKS, then EKS), Terraform-as-source-of-truth, hands-on SRE: added as a second equally weighted practice.
Anchor platform scales without a rebuild. Still on the original architecture, scaled, not rebuilt. Multi-storefront, multi-gateway, audit-grade.
Live .NET 4.8 → .NET 10 migration begins. Zero-downtime modernisation onto Azure-native infrastructure. The business continues operating throughout.
Calvrix Ltd incorporated. A name that names the discipline: calibration applied at infrastructure scale. Same team, same standard, sharper category.

The name · the motto · the voice

The name is the discipline. The motto is the rule. The voice is the proof.

Calvrix is not a generated word. Every part of it carries engineering meaning, and every part of it earns its place.

// the name

Calvrix

calcalibration
vthe kinetic bridge
rix-rix · the systems suffix

Cal is Latin calx: the counting stone on a Roman board, and the lime that held masonry up. To calculate and to be the foundation, read at once. V is phonetic load-bearing: the name's centre of gravity when spoken. A soft bridge (Calmrix, Calnrix) makes it passive. Rix is Latin -rix, the sovereign suffix, migrated in modern naming from the one who leads to the system that holds the field.

The full derivation, including why the mark is a cross-hair and not a letter, is on the brand page.

// the motto

Precision before scale.

The motto is the operating rule, not the marketing line. Most platforms fail on the same axis: they were scaled before they were correct. Spend grows, complexity compounds, and the system the business depends on becomes the system nobody can change.

Calvrix inverts the order. Calibrate first. Get the architecture, the runtime, the data model, the deployment topology, and the cost shape correct at the current business stage. Then scale. Scale the version that is correct, not the version that arrived first.

// applied to: every architecture review · every modernisation cut · every hire decision

// the brand promise

Systems that last.

Systems, plural: we operate several, side by side, for years. That last: the only property that compounds.

Uptime is a quarter. Durability is a decade.

// the wordmark

The dotless ı, the orange square.

The wordmark spells calvrıx: Latin small letter dotless i. The dot is removed from the type and replaced by an orange square, set above the letter where the dot used to live. That square is the same square at the centre of the mark: the two rhyme, and the rhyme is the system rather than a coincidence.

It reads as a calibration target: the centre point of the architecture diagram, the point all inputs converge on. The orange is used surgically across the system: the dot, the section-label slashes, one accent on each metric card, one rail on each bounded surface, anything genuinely live, and the things you can act on: the primary button, the focus ring. Nothing else. Not ordinals, not bullets, not field labels, not dates. It earns attention by scarcity. The brand is monochrome with one deliberate exception.

// what the brand refuses
  • No discovery calls.
  • No staffing-agency model.
  • No reliability as marketing claim.
  • No round numbers without source.
  • No hype vocabulary (seamless, robust, leverage, transform) anywhere on this site.

Vendor-evaluation answers

The questions a serious procurement team asks.

Is Calvrix a consultancy, an agency, or a vendor?

A platform-engineering practice. We own architecture and operations on long-running enterprise platforms. We are not a staffing house, a cloud reseller, or a discovery-call funnel.

What stack do you operate?

Two practices: the Microsoft enterprise stack (.NET, Entity Framework Core, Azure-native infrastructure) and cloud-native operations (Kubernetes on AKS + EKS, Terraform, CI/CD, observability).

Can you run live migrations without downtime?

Yes: that is core discipline. Our anchor engagement is mid-migration from .NET 4.8 to .NET 10, on Azure-native infrastructure, while the business keeps trading.

How do engagements start?

A direct technical conversation. No discovery call, no sales-qualified-lead funnel. You send the system context; we respond directly with whether the problem fits our level of work.

How is documentation handled?

Every significant architecture decision lands in an ADR. Every operational standard lands in a runbook. Decisions must survive the people who made them.

Are you UK-based?

Yes. Calvrix Ltd is registered in Scotland and continues the practice founded as Dove Solutions in 2019. We work with international customers.

Direct enquiries

If the platform matters, the first conversation is technical.

No sales funnel. No generic discovery call. Send the system context. Calvrix will respond directly and tell you whether the problem fits our level of work.

Talk to Calvrix[email protected]