CraneDev

Senior software agency

Built to ship. Built to last.

A senior team that takes systems from architecture to production, then stays on them. No handover to people who have never seen the code.

Book a callSee the work

Proof

Numbers from production, not from a deck.

  • 42

    Systems in production

  • 180ms

    Median p95 after migration

  • 99.98%

    Uptime across managed services

  • 9 yrs

    Median engineer experience

Services

How we work, and what each engagement leaves you with.

Four ways to engage. Each one ends with something you own and can run without us.

  • Architecture and discovery

    2–3 weeks

    We map the system you have against the one you need, and write down why.

    What you get: A written architecture, a risk list, and a sequenced plan you own.

  • Build to production

    8–16 weeks

    A senior team takes the plan to a running system, in your repo from day one.

    What you get: A deployed service, tests, runbooks, and the CI that ships it.

  • Rescue and migration

    6–14 weeks

    For systems that work but cannot be changed safely any more.

    What you get: Incremental migration with a rollback at every step, no big-bang cutover.

  • Run it with you

    Ongoing

    We stay on the system after launch instead of handing it to strangers.

    What you get: On-call rotation, monthly reliability review, and a shrinking backlog.

Selected work

Systems we built, and the numbers that moved.

Every card opens the same three lines: the problem, what we built, and what it measured afterwards.

All work

Testimonials

What clients say after we hand over.

  • “They rebuilt our ledger without a single day of downtime, then stayed on for the six months it took us to trust it. That second part is the rare bit.”

    Dana OkaforCTO, Northwind Pay

  • “We had three teams argue about the ingest design for a quarter. CraneDev shipped a working version in nine weeks and the argument stopped.”

    Marcus FeldVP Engineering, Atlas Health

  • “The handover was a repo we could actually read, with the reasoning written down. We have added to it for a year without calling them.”

    Priya RamanHead of Platform, Relay

Clients

Teams we’ve shipped for.

  • Northwind Pay
  • Atlas Health
  • Relay
  • Harbor Logistics
  • Sentinel
  • Meridian

Process

How a project runs.

  1. Read the system

    Week 1

    We read the code and the incidents before proposing anything. No discovery theatre.

  2. Agree the shape

    Weeks 2–3

    A written architecture with the trade-offs stated, so disagreement happens on paper.

  3. Ship in slices

    Weeks 4+

    Something runs in production early and keeps running. No integration phase at the end.

  4. Hand over, or stay

    Ongoing

    Your team owns it with the reasoning written down — or we keep the pager. Your call.

Open source

Code you can read before you call.

The repositories we maintain in public, with what each one does. Stars and push dates come straight from GitHub.

All repositories

Contact

Tell us what you are building.

You will get a reply from someone who would work on it, within one business day. If it is not a fit we will say so and point you somewhere better.

hello@cranedev.com

The system, what is wrong with it, and what you want to be true instead.

Talk to the people who would do the work.

Bring the system you already have. We will tell you where we would start, what we would leave alone, and how long the first release takes.

Book a call