Technology

Proven tools, chosen for the job.

We pick technology for maintainability and fit with what you already run, not for novelty. This is the stack we build with most often.

01 — How we choose

How do we decide what to build with?

Fit with what you run

We favour tools that integrate cleanly with your existing systems and team skills.
Maintainable for years

Mature, well-documented technology that other engineers can pick up and support.
Open standards first

Standard protocols and formats keep your data portable and your options open.
Right-sized

Infrastructure that matches the load you have, with a clear path to grow.

02 — Stack

Interfaces for customers, staff and partners.

React: Interactive interfaces for web applications and dashboards.
Next.js: Web applications and sites that need server rendering and routing.
TypeScript: Typed JavaScript across front end and back end for safer change.
Flutter: Mobile and kiosk interfaces from a single codebase.

Business logic, integrations and the APIs that connect systems.

.NET: Enterprise services and integrations, especially alongside Microsoft-based systems.
Node.js: APIs, webhook handlers and integration services.
Python: Automation, data processing and AI workloads.
GraphQL: Flexible APIs for front ends that combine data from several sources.

Reliable storage for records, queues and caches.

Repeatable environments and deployments.

Models and protocols for practical automation.

Model Context Protocol: Controlled access for AI assistants to business systems.
TensorFlow: Training and running machine-learning models.
LLM APIs: Language models for assistants, agents and document processing.

Taking and reconciling payments online and in store.

Describe the problem in a few sentences. We will reply with an honest view of whether and how we can help.