Services

Software, cloud and data work for growing businesses

We build the systems a business runs on, host them properly and turn their data into reports people use. Most clients start with one of these and stay for the second.

01

Web, mobile and desktop apps

We build the systems a business runs on: billing, HR, bookings, stock and customer portals. Web apps in Laravel, NestJS and React; phone apps in Flutter; desktop apps in Tauri that keep working when the internet drops and sync when it comes back.

  • LaravelLaravel
  • NestJSNestJS
  • ReactReact
  • Next.jsNext.js
  • FlutterFlutter
  • TauriTauri

What you get

  • Product scope, screens and a fixed price before code
  • Web apps, admin panels and REST APIs
  • Flutter apps for Android and iOS
  • Offline-first desktop apps with local SQLite
  • Payment, SMS and email integrations
  • Handover with documentation and tests

Where we have done it

02

Cloud and DevOps

We set up and run infrastructure on AWS and Cloudflare: build pipelines, containers, databases, backups, DNS and monitoring.

  • AWSAWS
  • CloudflareCloudflare
  • DockerDocker
  • GitLabGitLab
  • GitHubGitHub
  • NginxNginx

What you get

  • AWS accounts set up with least-privilege IAM
  • CI/CD on GitLab, GitHub Actions or CodeBuild
  • Docker images and repeatable environments
  • Cloudflare DNS, Pages, Workers and SSL
  • Backups, alerts and uptime checks
  • Cost reviews for existing AWS bills

Where we have done it

03

Data engineering and reporting

Most of the businesses we meet keep their numbers in spreadsheets or in an old system nobody wants to touch. We design the database, move the data across with checks at every step, and build the reports and dashboards that replace the monthly spreadsheet.

  • PostgreSQLPostgreSQL
  • MySQLMySQL
  • RedisRedis
  • PythonPython
  • SQLiteSQLite
  • pandaspandas

What you get

  • PostgreSQL and MySQL schema design
  • Data migration from Excel and legacy systems
  • Sync between offline clients and a central database
  • Sales, payroll and stock reports
  • Scheduled exports and data pipelines
  • Redis caching for busy endpoints

Where we have done it

04

AI in your product

We add language models to products where they save real time: assistants that answer from a company’s own documents and cite them, tools that draft and check, and pipelines that turn a request into finished work. We use Claude, OpenAI and DeepSeek and keep the provider swappable.

  • ClaudeClaude
  • OpenAIOpenAI
  • PythonPython
  • FastAPIFastAPI
  • ReactReact
  • Node.jsNode.js

What you get

  • Assistants grounded in your documents, with sources
  • Embeddable chat widgets for your website
  • Provider failover between Claude, OpenAI and DeepSeek
  • Automation that runs a person’s checklist
  • Cost and usage limits per customer
  • Evaluation sets so answers stay correct

Where we have done it

Three ways to work with us

Pick the one that fits the work. Many projects start fixed-scope and move to a support plan after launch.

Fixed-scope project

A new app, a migration or a rebuild with a clear end. We agree screens, scope, price and dates after discovery, and bill by milestone.

Good for a first version, a website with a back office, a move to AWS.

Monthly team

A small team of engineers working on your product every week, on a monthly rate, with a two-week release rhythm.

Good for products that change every month and teams that need extra hands.

Support plan

Hosting, monitoring, backups, security updates and a set number of hours for fixes each month, with an agreed response time.

Good for software that is live and needs looking after.

How a project runs

The same four stages for a two-month app and a year-long platform. Only the length of each changes.

  1. 1

    Discovery One to two weeks

    We talk to the people who will use the software, map how the work happens today and list what must be true on launch day.

    You get Written scope, screens for the main flows, a fixed price and a timeline

  2. 2

    Design One to three weeks

    Screens for every page and state, checked with real users where we can, and a data model the reports will need later.

    You get Clickable screens and a database plan you can keep

  3. 3

    Build Two-week releases

    We ship to a staging link every second week. You test it, we fix what you find, and the next release starts.

    You get Working software, tests, and notes on what changed

  4. 4

    Launch and support Ongoing

    We move data across, train the people who will use it and stay on call for the first weeks. Then the support plan takes over.

    You get A live system on your accounts, documentation and handover

How we ship software

The rules every project follows, whatever its size.

Code review on every change

No change reaches the main branch without a second engineer reading it.

Automated tests

Business rules such as billing, payroll and permissions have tests that run on every push.

One pipeline per project

Build, test and deploy run the same way each time, on GitLab, GitHub Actions or AWS CodeBuild.

Staging before production

Every release runs on a staging copy first, with realistic data.

Secrets kept out of code

Keys live in AWS Systems Manager or Cloudflare secrets, with least-privilege access.

Backups you have tested

Nightly backups, and a restore we have actually tried.

Your accounts, your code

Repositories, cloud accounts and domains are in your name from the start.

Documentation at handover

How to run it, how to deploy it, and where everything lives.