What we build

Four kinds of load.

Most of what a business needs from software falls into one of these. If yours doesn't, say so — the survey week is where we find out.

Complete truss · Typically 8–16 weeks

Web applications

Customer portals, booking systems, dashboards, line-of-business apps. Built server-rendered or as a single-page app depending on which one your team can still maintain three years from now.

  • TypeScript
  • React
  • PostgreSQL
  • Auth & roles

King post & tie · Typically 6–10 weeks

Internal tools

The spreadsheet your operation actually runs on, turned into something with permissions, a history of who changed what, and no formula that breaks the moment somebody sorts a column.

  • Audit trail
  • Bulk import
  • Reporting
  • SSO

Spliced span · Typically 4–8 weeks

System integration

Getting your CRM, accounting, billing, and warehouse to agree on the facts. Queues, retries, idempotency, and a reconciliation report you would be happy to hand an auditor.

  • REST & webhooks
  • Queues
  • Reconciliation
  • Monitoring

Braced member · Typically 3–8 weeks

Legacy rescue

An application nobody wants to touch. We map it, put a test harness around the parts that earn money, and make it safe to change again — usually without a rewrite.

  • Test harness
  • Refactoring
  • Runbooks
  • Upgrades

What we build with

We pick boring, well-documented tools on purpose. The best technology decision is usually the one your next engineer already knows.

  • TypeScript
  • React
  • Node.js
  • Python
  • PostgreSQL
  • Redis
  • Docker
  • Terraform
  • AWS
  • GitHub Actions
  • Playwright
  • OpenTelemetry

Our own work

Two builds, written up.

The products we run ourselves, from the problem each one answers to the decisions behind the build.

Case study · manaarchive.com

How we built ManaArchive

ManaArchive is the Magic: The Gathering collection tracker Kingpost Software builds and runs itself. What it had to answer for collectors, traders and sellers, and the decisions that shaped the build.

Case study · storatix.com

How we built Storatix

Storatix is the self storage management software Kingpost Software builds and runs itself. What a storage operation needed from it, and the decisions that shaped the build.

Case study · selfstoragehosting.com

How we built Self Storage Hosting

Self Storage Hosting is the cloud access control and facility website service Kingpost Software builds and runs itself. Why an office PC is a weak link in a storage gate, and the decisions that shaped the service and the site that sells it.

Questions

Before you call.

What does a project cost?

Every engagement starts with a fixed-fee survey week. That produces a written scope and a firm price before you commit to a build, so you are never asked to approve a number that came out of a first conversation.

Who owns the code?

You do, from the first commit. The repository lives in your organization, we work inside it, and nothing about handover requires our cooperation.

Do you work alongside our existing team?

Often. Your engineers review our pull requests and we review theirs. We write documentation as though we were leaving next month, because eventually we are.

What happens after handover?

Thirty days of included support for anything that turns out to be ours. After that most clients move to a small retainer, and some need nothing at all — which is the intended outcome, not a failure.

How small is too small?

If a week of work would fix it, tell us and we will say whether it is worth hiring anyone. We would rather point you somewhere useful than take a project that should have been a spreadsheet formula.