MATLAB →
PYTHON.
Any math, any domain. Audit, risk matrix, pilot module, full migration. From science to production-grade Python with proper testing and CI.
Research code that started as a one-engineer prototype hits a wall: nobody else can run it, licences cost more than the team, deployment is impossible. We move the math to Python — but more importantly, we leave behind tests, CI, and a codebase the next hire can read.
| Service | MATLAB → Python migration |
| Start | 1-week paid audit · fixed fee |
| Pilot | 2–4 weeks · fixed scope |
| Migration | Rolling · milestone-billed |
| Currency | EUR |
| Pre-NDA | Not required for first email |
| Engineer | Evgeny Istomin · solo |
| Location | Remote · CET |
Quality, not throughput.
- → You have a MATLAB codebase that one or two people understand.
- → The math is correct; the engineering is the bottleneck.
- → You're hiring Python engineers and need a runtime they can actually work in.
- → Licence costs are starting to look like an extra headcount.
- → You want tests and CI as part of the deliverable, not as a follow-up project.
- × You want a "wrap-it-and-pray" shim around MATLAB — we won't ship that.
- × The math is unspecified and the audit would discover most of the project.
- × Simulink models with hardware code generation — that's a different practice.
- × Fixed-bid full migration with no audit. We start with the audit, always.
- × Pure "take it offshore and supervise" engagements.
AUDIT · PILOT · MIGRATE.
You can stop after any phase. Most clients stop after the audit, run the pilot internally, then come back for the bulk migration.
Audit
Read the MATLAB, document the math, identify risk hotspots. We talk to the original author when possible, run the existing test suite (if any), and produce a written report you can hand to procurement.
– Risk matrix per module
– Recommended port order
– Effort estimate ±20%
Risk matrix
Each module classified by math complexity, test coverage, downstream dependencies, and porting risk. The matrix decides what's worth porting first — and what is better left in MATLAB or rewritten from spec.
– Go / no-go recommendation
– Spec-rewrite candidates flagged
Pilot module
Port one self-contained piece end-to-end. Tests against the original MATLAB outputs, CI green on day one, documented public API. Proves fit and gives your team a working template.
– pytest + hypothesis suite
– GH Actions CI green
– Sphinx API docs
Full migration
Port the remaining modules at a known velocity. Weekly demos, signed milestones, code review with your team. We stop when the MATLAB licences can be cancelled — or earlier if the spec says so.
– Numerical-equivalence test gates
– Migration playbook
– 30-day post-handover support
Handover & coaching
Your team owns the result. We coach if you want — pair on the first internal changes, set up the code-review patterns, document the gotchas we found along the way.
– Code-review rubric
– Internal walkthrough video
– Engineering on-call: 30 days
NOT JUST NUMPY.
Math
Testing
CI / hygiene
Delivery
FAQ.
How much does a 1-week audit cost? +
Fixed fee in EUR. We quote in the first email reply once we understand the scope. No discount for promise of follow-up work.
Do you sign NDAs? +
Yes, after the first email exchange. We don't sign NDAs before hello — it wastes everyone's time when the fit isn't there.
Will you port Simulink? +
No. Pure-script MATLAB only, and any Simulink-generated C/C++ helpers if they sit in the same repo. Hardware code-gen is a separate practice we do not run.
Numerical equivalence — how do you prove it? +
Property-based tests with hypothesis, golden-output fixtures against the MATLAB outputs, and a numerical-tolerance gate in CI. We document the tolerance per module.
Can you work under our existing Python conventions? +
Yes. We'll match your linting, packaging and CI choices unless they are actively painful — in which case we flag it before the pilot starts.
Who actually writes the code? +
Evgeny Istomin. The engineer named on the proposal is the engineer writing the commits. No juniors, no offshore subcontract.
OPEN A FILE.
Tell us about your codebase — size in lines, domain, current pain. We reply within two working days with questions, a suggested call time, or — if it's clear we're not the right fit — an honest no.
Alpisto d.o.o. — Slovenian LLC, EU VAT registered (SI91102227). Invoiced in EUR via standard reverse-charge for B2B clients within the EU. NDAs welcome after first email.
START WITH
THE AUDIT.
Send a paragraph about the codebase — size in lines, domain, current pain. We'll reply in ≤ 2 working days with either a quote or an honest no.