Modernize legacy systems while your team keeps shipping.
I bring old Java applications onto current Java and Spring, on live products, with no feature freeze.
Matt Wojtowicz You work with me directly. 15 years building enterprise Java systems. Companies in my work history
Sound familiar?
What teams usually tell me on the first call.
- Afraid to deploy
- The app hasn't been updated in years. Every change risks breaking something. Deployments are manual and terrifying.
- Can't hire for it
- Nobody wants to work on the old stack. The developers who know the system are leaving. New hires take 6 months to ramp up.
- Consultancies want 12 months
- You're looking at a year-long engagement with a full team. You need one application modernized in 2 to 4 months.
What it looks like in practice
An 11-year-old privacy platform, modernized while regulatory features kept shipping
I upgraded the backend and rebuilt the frontend of a live GDPR compliance platform. No feature freeze, and the same workload now runs on half the servers.
Read the case study →- Java
- 8 → 21
- Spring Boot
- 1.4 → 3.5
- Production Java servers
- 4 → 2
Replaced weeks of manual document coordination with a self-serve intake system. What took multiple people and endless emails now takes one person 10 minutes.
I replaced 8+ hours of daily manual data aggregation with a report ready before the team started work. Took weeks.
Three ways to work with me
Start with one free call. You leave with a written plan.
Strategy Call
30 minutes on your system. Afterward I send you a one-page plan: what breaks first, the order of work, and a rough size. If I'm not the right person, I'll say so.
- ✓ One free 30-minute call
- ✓ A one-page plan in your inbox afterward
- ✓ What breaks first and what to fix first
- ✓ A rough size for the work
- ✓ No commitment and no sales pitch
Targeted Project
One application brought onto current Java and Spring. Scope and timeline agreed up front, usually 2 to 4 months.
- ✓ Fixed scope, agreed before work starts
- ✓ Upgraded in small steps, shipping the whole time
- ✓ Your developers walked through every change
Whole Stack
Several applications, done in an order that keeps the business running. Usually 3 to 6 months.
- ✓ Manual deploys replaced with a repeatable build, test and release process
- ✓ A runbook for each service
- ✓ Support for a period after handoff
15 years of enterprise delivery
"Partnering with Matt over several years at eVestment was a seamless experience. I never had to worry about any project he was involved in. His work was always executed quickly and thoroughly. He effectively managed an entire product line by himself, demonstrating exceptional reliability and expertise."
"During his time at Balto, Matthew consistently impressed me with his expertise in robust, efficient, and scalable solutions for our projects. His proficiency in crafting solutions and AWS made him an invaluable member of our team."
"What stands out is the quality of Matt's solutions. When others might take shortcuts, Matt engineers clean, maintainable solutions that stand the test of time. His code is something you can build on, not something you have to work around."
Hi, I'm Matt.
15 years building enterprise systems. I've worked with companies across financial services, pharma, ad tech, and music rights.
I've watched teams spend months planning upgrades that one focused engineer could finish much faster. Katyella is me doing that work directly, without a six-person team or a year-long plan.
Katyella episodes and migration guides
I talk with guests about what we're building on Katyella, and my written guides cover technical migrations in detail.
Episode 12 · November 19, 2026 · 52:01
We Built an AI That Drafts Prior Auth Letters
All episodes →Book your strategy call
30 minutes on your system. Afterward I send you a one-page plan you can use whether or not you hire me.
If I'm not the right fit, I'll say so and point you to who is.
Book a Strategy CallOr email contact@katyella.com
Modernization plan
- Where you are
- Java 8, Spring Boot 1.5, deployed by hand to WebLogic.
- What breaks first
- Spring Boot 1.5 no longer gets security patches. Two libraries block the Java upgrade.
- Order of work
-
- Get the test suite running in CI
- Java 8 to 17, replacing the two blockers
- Spring Boot 2.7, then 3.x
- Containerize and retire WebLogic
- Rough size
- A targeted project, about 3 months.
Illustrative example. Yours covers your system.