Skip to content
05 · ENGINEER-WRITTEN

Software.

Custom engineering apps, pipelines, tools.

Overview
Software written by engineers for engineers. Data pipelines, bespoke calculators, dashboards, desktop tools.

We write software for ourselves first. ChainSolve. the Rust + WebAssembly block-graph calculator. is the largest thing we’ve shipped, but the pattern is the same at smaller scale: if the tool doesn’t exist, build it. If it’s too slow, rewrite it in something that isn’t.

Data pipelines, bespoke calculators, dashboards, CAD automation, desktop tooling. Our engineers write the code. It reads like the engineering it supports, because the same people are doing both jobs.

Process

How we'll run the programme.

01
Requirements
Understand the actual task the tool will replace. the spreadsheet, the macro, the outsourced script. Capture inputs, outputs, and the edge cases that made the old thing fragile.
02
Architecture
Pick the smallest stack that works. Tauri desktop, static web + Worker backend, WASM compute, or a spreadsheet plug-in. the architecture is the cheapest lever.
03
Build
TypeScript, Rust, Python. Tests first where bugs are expensive. Internal preview at every milestone. You see it behave before it ships.
04
Hand-off
Docs that engineers read, deployment that engineers run. Source committed to your repo, not ours. Hand-off or ongoing maintenance. your call.

The stack

Language · runtime · use case.

Feature Language / Runtime Primary strength When we reach for it Us
TypeScript TypeScript Product velocity, type safety, ecosystem Web apps, API routes, data pipelines with moderate compute
Rust Rust Performance, memory safety, WASM compilation Compute-heavy modules, desktop tooling, anything latency-critical
WebAssembly WASM Near-native speed in the browser, zero install In-browser solvers, calculators, offline-capable engineering tools
Python Python Rapid analysis, ML/data ecosystem, CAD scripting Data pipelines, CAD automation, one-off analysis scripts

IP & licensing

The things people ask before signing.

Who owns the code?

You do, unconditionally. All work product is assigned to you at delivery. We retain no licence, no right-to-reuse clause, and no obligation to give us credit.

Do you use open-source dependencies?

Yes, selectively. We document every dependency with its licence. If a licence is incompatible with your intended use (e.g. GPL in a proprietary product), we flag it at architecture review and substitute.

Can we review the code before final delivery?

Yes. We commit to a shared private repository from day one. You have read access throughout the engagement, not just at handover. No black-box sprints.

What if we want ongoing maintenance after delivery?

We offer a retained maintenance agreement at a fixed monthly cost. Alternatively, the hand-off documentation is written so your own engineers can maintain the code without us.

Start here

Send us a brief.
We reply within one working day.