We build software, and the systems it runs on. Without compromise.

A trade business needs to take bookings and send invoices. An engineer needs a Linux server that stays up. Somebody just wants a small tool that does one job properly. We build for all three. A rare, elite team of top-tier specialists with 20+ years of experience, working right across the range, from the hardware to the application, everything.

InterfacesWeb and mobile appsDashboardsREST APIWebflowNginx
SoftwarePythonGoRustZigJavaScriptC and C++
ServicesDockerKubernetesTerraformAnsibleCI pipelines
NetworkCGNATVPNFirewallRoutingLoad balancing
PlatformLinuxsystemdUNIXWindows ServerBootable ISOs
HardwareServersRaspberry PiSTM32ArduinoESP32
20 years of experience
167 Technologies in use
Takumi team
23 Countries delivered to
01

Who we build for

Three kinds of customer. The work differs, the standard does not.

01

Trades and small businesses

Booking, job tracking and invoicing that works on a phone in a van. Software your customers will open, and software you will keep using.

  • Web and mobile apps
  • Payments
  • Scheduling
  • Dashboards
02

Engineering and infrastructure

Linux servers, network, cloud, and the software that runs on them. Systems that have to keep working when nobody is watching.

  • Linux
  • Networking
  • Cloud
  • Databases
03

Ordinary people

A small tool for one specific job. It does that job, it needs no manual, and it does not ask for an account you do not have.

  • Small tools
  • Automation
  • Scripts
02

What we build

Six areas, each with a page of its own. Most projects touch three or four of them at once.

01

Linux and systems

The largest part of what we do. Linux servers, routers, storage and virtualisation, plus the embedded boards that run the same software on a fraction of the hardware. Built to stay running, and recovered when they stop.

  • Linux
  • systemd
  • OpenWrt
  • Proxmox
  • KVM
02

Networking and security

Carrier grade NAT at the kernel level, private cloud networks, VPN tunnels that hold up under NAT rebinding, and server hardening that gets measured instead of assumed. Offensive work is done in an educational and research context, where the legal boundary is clear.

  • Networking
  • CGNAT
  • VPN
  • Firewalls
  • SSH hardening
03

Software development

Applications, services, and the scripts that hold a process together. Data systems, trading engines, and work on existing codebases, written in whichever language already runs where the code has to live.

  • Shell
  • Python
  • PHP
  • Java
  • JavaScript
04

Cloud and DevOps

Infrastructure defined in code, and pipelines that report what broke instead of only reporting that something broke. Terraform across major providers, Kubernetes and Docker on top, and backups with a restore test attached.

  • Terraform
  • Kubernetes
  • Docker
  • Ansible
  • Jenkins
05

Automation and AI

Workflows that remove a manual step, and the machine learning and vision work that has to run on hardware too small to be generous about it. Anything scheduled here reports its own failures.

  • n8n
  • Python
  • OpenCV
  • Machine learning
  • Raspberry Pi
06

Video and television

FFmpeg encoding pipelines with adaptive bitrate output, live audio paths, and the player applications that decode the result on Samsung, Fire TV, Android TV, VEGA OS, and Philips sets. The player and the manifest it reads are two ends of one contract.

  • FFmpeg
  • ABR
  • HLS
  • Icecast
  • Tizen
03

Who we build it for

Named, because a claim you cannot check is not worth much.

04

Selected work

Real projects, described by what was built and what it had to survive.

05

What clients say

Left exactly as written. Nothing added and nothing softened.

06

Questions and answers

Answered plainly, because the answer is usually what sends the enquiry.

What do you build?

Mostly Linux, and the software that sits on it. Servers, routers, storage and virtualisation, plus applications, cloud infrastructure, and video encoding and player work. A typical week might contain a Proxmox node that dropped out of a cluster, a server that stopped booting after an array event, and an FFmpeg pipeline that has to emit a specific set of renditions.

Do you build for trades businesses?

Yes. Booking, job tracking and invoicing are the things that come up most, usually as a web app that works on a phone as well as a desktop. We start from how the work already happens rather than from a template, because a trade that runs on paper and a trade that runs on a scheduling package have very different days.

Can you build something for someone who is not technical?

Yes. If you can describe what you want to happen and what is in the way, that is enough to start. You do not need to know what language it should be written in, and you will not be asked to pick one.

How do you price?

Fixed price when the scope is clear, hourly when it is not. Most work is fixed price once I have had a short look at what you are running. You get the number before the work starts, and it does not change without me telling you why first.

What do you need from me to start?

A description of what is happening, access to the system in question, and any deadline that is real. If you are not sure what the problem is, that is fine and normal, and it is part of what the first conversation is for. If there is a server involved, the error message and a screenshot are worth more than a long written description.

How long have you been doing this?

20+ years of experience. The earliest work I still hold records of is BlackBerry application development, followed by web applications and open source work through the late 2000s. Linux has been the constant throughout, in one form or another, long before it became fashionable to list it.

Do you work with hardware that is out of support?

Yes, and often there is no alternative. Kernels and distributions reach end of life on the vendor's schedule, not yours, and plenty of equipment keeps running for a decade afterwards. Work on kernel 4.19 is routine here, and so is building firmware for a router model that has been off sale since 2019.

Do you do remote work only?

All of it is remote, and it has always been. Clients have been in India, Germany, Austria, Italy, Canada, the United States, Australia, and elsewhere. Timezone overlap is the practical constraint rather than location.

Will you work under an NDA?

Yes, and I would rather you had one if the system is commercially sensitive. Most of the work is infrastructure, so there is rarely source code to protect, but there is almost always a hostname, an IP range, or an architecture diagram that should not be public.

07

Start a project

Before you send

Tell us what you are trying to do and what is in the way. A plain description of the job is enough to start a conversation. If a server is involved, the error message and a screenshot are worth more than anything you could write about it.