Stack9 builds software systems for clients who need them to work.

Engineering, integration and compliance technology. We specify in writing, build with tests, document the system and hand over the source code.

Start a projectSee services

What we do

We build the system, connect it to what you already run and make it stand up to an audit.

  • Engineering

    Custom software built to a written specification. Web applications, internal tools, back-office systems and APIs. You get the source code, the tests and the deployment scripts.

  • Integration

    Connections between systems that were never designed to talk to each other. ERPs, banks, payment gateways, government portals, legacy databases and third-party APIs. Data migration with reconciliation reports.

  • Compliance technology

    Software for processes that regulators audit. Audit trails, reporting, KYC and record-keeping, access controls and data retention. Built for banks, insurers, healthcare providers and licensed businesses.

What you can hold us to

to reply to your first message
2working days
of discovery before any quote
1week
between releases you can test
2weeks
of defect fixes after go-live, at no charge
30days

How we work

The systems we build record who did what and when. So does our delivery process. You can show an auditor both.

  1. Specification before code

    Every project starts with a written specification: what the system does, what it does not do and how we will know it works. You sign it off before we build.

  2. Tests are part of the deliverable

    Automated tests ship with the code and run on every change. A feature without a test is not finished.

  3. You own the code

    Source code, infrastructure configuration and documentation live in a repository you control from day one. We hold nothing back at handover.

  4. Progress in writing

    You get a written progress note every week: what shipped, what is blocked, what comes next. We record every decision, change and sign-off, so nobody has to remember them.

Who we work with

Banks, insurers, healthcare providers and other licensed businesses that need software a regulator can inspect. Companies with an ERP, a legacy database or a payment gateway that has to exchange data with something newer. Teams whose last software project ran late, ran over or never went live.

We work from Sri Lanka, with clients at home and abroad. The work runs on shared repositories, written specifications and scheduled calls, so nothing depends on being in the same room.

Notes on building software that has to work.

Practical guidance for buyers and technical leads.

  • Integration

    Data migration: reconcile before you switch

    A migration is finished when both systems agree and someone has signed to say so, not when the script exits. This is how to plan one so that the night of the switch is dull.

  • Engineering

    How to write a specification a supplier can quote against

    A supplier can only fix a price for work that is written down. This guide covers what to put in the document, what to leave out and how to handle what you do not know yet.

  • Integration

    The quiet ways an integration fails

    The expensive integration failures raise no error. Both systems report success and the data is wrong. Here are eight of them, how each one surfaces weeks later and the check that catches it on the day.

Tell us what you need built or fixed, and we reply within 2 working days.

Start a project