Aripone

Modernization practice

Move it while it runs.

Off .NET Framework, Java or the monolith, without a big-bang rewrite. Old and new run side by side behind one versioned API, and a strangler façade moves one slice at a time, so you keep shipping throughout.

Book a scoping call See the assessment

  1. 01 / 03 Façade

    Put one API in front.

    A versioned API goes in front of the old system first. Every consumer calls it, and old and new run side by side behind it for a stated period. Target infrastructure is defined as code before the first workload lands on it.

  2. 02 / 03 Routes

    Move one route at a time.

    The façade sends each route to one side. A route moves when its phase is ready, and every data step carries a verification (row counts, checksums, a comparison job) and a rollback.

  3. 03 / 03 Gate

    Each phase waits for its gate.

    A gate is measurable, for example thirty days of matching results. Retiring the old component is a planned step, dated by when its last consumer moves, with a freeze window and notice for partners and customers.

Traffic passes the façade while routes move one at a time to new services. Phase 3 waits for its gate.

What breaks

Why migrations stall.

The brief is usually "we cannot hire for the old stack and we cannot stop shipping." What stops a migration is rarely the code. It is what nobody wrote down:

  • No full restore has been tested, and nobody knows how long one takes.
  • One person holds the decision logic, and it is not captured as tests.
  • Nobody can list every API consumer, or the version each one calls.
  • Reporting reads production directly.
  • Runtimes past their support end date, and libraries with no upgrade path.
  • Deploys nobody can repeat, and a rollback nobody has exercised.
Strangler façade, route by route.
RoutePhaseGoes to
/quotesPhase 1New service
/customersPhase 1New service
/policiesPhase 2New service
/claimsPhase 2New service
/billingPhase 3Legacy, at its gate
/reportsPhase 3Legacy, at its gate

New service: 4 of 6 routesLegacy .NET: 2 of 6 routesGate: 30 days of matching results

One versioned API in front, each route sent to one side. The roadmap documents the façade routes for each phase; phases 1 and 2 have moved, and phase 3 waits for its gate.

What we do

Make it recoverable, then move it in phases.

Every phase is priced from the assessment's findings, so the price is fixed before work starts.

01 / 02 Fixed price

Phase 0: prerequisites

Infrastructure as code, CI, a tested restore and application-level monitoring, so the migration is recoverable and observable before anything moves.

See the assessment

02 / 02 Fixed price per phase

Migration Program

Phase by phase, with change control and a gate at the end of each. Phase 1 is written up in the assessment as a fixed-price scope.

Every fee on the pricing page

Method

How a migration runs.

  1. 01 / 04 2 or 3 weeks

    Assess

    We inventory every application, service, job, database and integration, give each one a disposition, and apply the 26-item readiness checklist to the estate.

  2. 02 / 04 Report

    Plan

    A target architecture, a risk register and a phased roadmap written so any team can execute it, with phase 1 as a fixed-price scope.

  3. 03 / 04 Fixed price per phase

    Build

    Phase 0 first, then the migration phase by phase. Each phase has a gate with measurable criteria, and each data step has a rollback.

  4. 04 / 04 Yours

    Hand over

    The team that will own the modernized estate is named in the assessment and works alongside us. The old component retires on a planned date.

Assessment

Modernization Assessment

Two or three weeks, fixed fee, and every engagement starts here. The roadmap is written so that any team can execute it.

What you keep

  • An estate inventory with a disposition per component.
  • A target architecture and a risk register.
  • A phased roadmap.
  • A one-page executive summary your board can decide from.

Published fee

$16,500One application and its data

$24,500An estate

Half on signature, half on delivery. We don't bill by the hour.

Book a scoping call Every fee

Case study

Off three stacks, without a freeze.

A reinsurance platform moved from .NET, Java and pre-framework JavaScript to TypeScript, one route at a time, while the product kept shipping. Delivered by our principal, Rey Narvaez, in regulated production before Aripone was formed.

Read the case study

Self-check

Score it before you call.

Fourteen questions from the readiness checklist, three minutes, no code access needed. Scored in your browser; nothing is sent. It tells you whether a migration can start safely today and which prerequisites are missing.

  1. 01

    Modernization Readiness Scorecard

    14 questions · 3 min

Example result

59/ 100Exposed

Do these first

  1. Data. Run a restore into a fresh environment and time it before anything else.
  2. Team and knowledge. Pair the expert with a second engineer and capture the logic as tests.
  3. Integrations. Inventory consumers from gateway or server logs; list partner notice periods.

Illustrative example, not a client's data.

Every part settled into one system that keeps running.

Scoping call

Tell us about the estate.

Bring the stack you can't hire for. In 30 minutes we'll tell you whether the assessment is worth it.

Book a scoping call [email protected]