How We Work | NeuraBloq

Working on a retired framework demands a particular discipline: nothing upstream will save you, so every claim has to be verified locally. Our approach comes down to a few working rules.

Say what the situation is

Apache MXNet is in the Apache Attic. It receives no releases and no security patches, and that is the premise of every engagement — not a detail to soften. We don't pretend the framework is viable long-term, and we don't disparage it either: MXNet systems were built by capable teams on what was then a well-supported framework. The job is to respect what's running while building the road out.

Assess before committing

Porting effort is wildly variable and mostly invisible from the outside. We start engagements with enough assessment to know which kind of problem each model is — clean conversion, layer-by-layer re-implementation, or retraining — before anyone commits to a plan or a budget. When we quote effort, it comes with the evidence that produced the estimate.

Parity is the definition of done

A ported model is the same model or it isn't done. Every port carries a numerical-parity harness — same inputs through old and new, compared at documented tolerances, over inputs that cover the distribution's edges. When faithful conversion isn't achievable, we say so and switch to a retraining plan validated against production metrics, rather than shipping a lookalike and hoping.

Parallel runs, not big-bang cutovers

Infrastructure migrations run the new path next to the old one on the same traffic, with outputs, latency, and failure behavior compared before cutover — and the old path kept available for rollback until you retire it deliberately.

Honesty about retraining costs

The most common failure in framework migrations is an optimistic conversion estimate that quietly becomes a retraining project at three times the budget. Where weight conversion won't hold, we say it as early as the evidence allows. Sometimes the honest recommendation is that a model should be retired, not ported; we make that call explicitly rather than billing through it.

How we engage

All work is hourly time and materials — senior US engineers, as project engagements or staff augmentation. No fixed-price packages, no milestone pricing: scope, staffing, and timeline are agreed through an initial conversation and revisited as the work teaches us more. You see who is working, on what, and why.