Kespa Software · design, build, rebuild

Software you can keep building on.

We build new applications properly, and rebuild the ones that have become hard to change. Then we stay around to keep them that way.

A typical rebuildIllustrative
$ git diff --stat legacy..rebuild
desktop-app/  VB6 · 2003−48,210
reports/      copy-pasted SQL−6,417

api/         Python · FastAPI+9,734
web/         React+7,912
tests/       run on every change+4,388
deploy/      one command+312
Less code. More tests. Releases you don't dread.
Legacy software rewrite

A legacy scientific application rebuilt for a major Irish university after a public tender. A government department now relies on it, and on us.

Read the case study →
7 years

In service: a secure video platform for a medical training body, handling encrypted recordings of real consultations.

Read the case study →
7 years

Developing and maintaining a rebuilt production system for two major domain registries.

Read the case study →

Where we typically get involved

We'll look at what you have and give you an honest view of the best way forward, even if that isn't a rebuild.

Software holding the business back

It works, but every change is a risk

A codebase only one or two people understand, releases that are slow and fragile, workarounds piling up, and new developers who take months to get going.

  • Find where the complexity and risk really are
  • Restructure, or rebuild the parts that can't be saved, without stopping the business
  • Proper testing, deployment and release processes
Track recordLegacy desktop software rebuilt for the web, legacy C rewritten, and production applications taken over from other teams.
Legacy rewrite →
The last mile of AI-built apps

It almost works. That's the hard part.

AI tools make it easy to build something that nearly works. Security, data handling, testing, performance, deployment and someone who understands the code are where these projects stall.

  • Review and harden what was generated
  • Tests, error handling and a real deployment
  • Hosting and support afterwards, if you want it
Unfinished or failing projects

Started, but never finished

Something was begun and never reached a stable, usable state. We assess what's there, keep what's worth keeping and finish it, or rebuild it properly where that's cheaper in the long run.

New builds, integrations and tools

Built properly from the start

New applications designed for long-term maintainability and security, without over-engineering. APIs between your systems, AI features in existing applications, and CRMs and internal tools shaped around how your business works. We run software too, so we design for how it will be hosted.

How we work

Clear stages, agreed up front.

Assessment

We review the system or idea, identify the risks and agree the best path.

Stabilise or design

We fix the core problems, or design the new system.

Build or rebuild

Where parts can't be saved, we rebuild them properly.

Long-term support

We hand over a stable, documented system, or keep developing and supporting it.

Need it hosted and looked after too? Kespa Systems →

Discretion by default

We never name our clients: not on this site, not in sales conversations, not on social media. Your use of Kespa stays between us unless you choose otherwise. That's why you'll find descriptions here instead of logos.

The people who will build it

Senior developers who have built registry platforms, public-sector applications and secure healthcare systems, and led engineering at some of the biggest names in e-commerce.

Andy

Head of Software Development · Partner

Brings world-class experience in software design and engineering to Kespa, where he leads our software development. Was part of the team that built the CoCCA registry system, used by multiple country-code top-level domains (ccTLDs), then was founding tech lead and director of software engineering at MMX, leading the development of its registry and registrar platforms. Principal Engineer at Jet.com, Associate Director of Engineering at Walmart Global Tech, and VP of Engineering at Thrive Global before joining Kespa. Has built and led engineering teams at global scale, and holds every Kespa project to the same standard.

Ronan

Head of Systems Architecture · Founder

Designs the architecture software runs on: secure, scalable and resilient, following industry best practice, on AWS, other clouds or bare metal. Develops back-end APIs and internal tooling, mostly in Python and FastAPI, and builds the automated pipelines that test and deploy them. On legacy projects he leads discovery, working out how an old system really behaves before anything is changed or rebuilt. Previously worked as a senior software engineer for one of the world's largest domain registries.

Anderson

Front-end Developer

Has built front-end and back-end systems, internal tooling, and custom WordPress plugins used by large domain registrars. Works mostly in React today, with years of PHP behind him. Worked with us on registry systems at MMX before joining Kespa in 2020.

Claudia

Product Owner & QA

Owns quality. Nothing reaches a client until Claudia has tested it against what the client actually asked for, and she keeps testing as systems change. Also sets priorities and is clients' day-to-day contact. With Kespa since 2020.

Kieran

WordPress Specialist

Supports our customers with their WordPress issues, from broken updates to slow sites and misbehaving plugins. Also builds WordPress sites and looks after the WordPress side of our hosting. Worked with us as a contractor for years before joining Kespa in 2022.

Who we're not right for

  • Cheap development hours or junior developers
  • Large offshore-style teams
  • Work where quality and maintainability don't matter

Talk to us

If your software is getting harder to develop, or you have something new to build, tell us about it.

We reply within one working day, and we'll tell you quickly if we're not the right fit.