01
The monolith that became a career risk
One deployable, twenty years of logic, no tests anyone trusts. Changing a billing rule means touching checkout, reports, and a nightly job nobody owns.
IBEX FORCE · Since 2010
SolvingtheUnsolvable
The systems nobody wants to touch. We take legacy monoliths, stalled migrations, and production apps that cannot go down — and turn them into clean APIs, independent services, and cloud platforms your team can actually run.
Full-stack · Legacy → services · Azure / AWS · Production CI/CD
Our capacity is intentionally selective. We consider a limited number of new engagements based on project fit, scope, and timing — so each one gets senior, dedicated attention.
The brief we keep getting
Complicated is the job.
There are many problems in life. We cannot solve them all. We can solve this class of them — specifically, the web systems that have become too important, too tangled, or too abandoned to leave alone.
02
The migration that stalled after the vendor left
A half-moved estate on Azure or AWS. Pipelines that only one person understood. Production still pointing at the old box “just for now.”
03
The app that works until anyone has to change it
A desktop tool with no vendor. A jQuery UI that cannot hire. SOAP endpoints the new mobile app cannot speak. The business is fine — until it isn’t.
What we take on
Unconventional work, owned end to end.
We are a software company first. When a custom solution needs an on-site counterpart — networking, hardware, a controlled environment — we will build that too. It is never the product. It is how some products actually ship.
01
Monolith extraction
Split a legacy application into independent services without a big-bang rewrite. Bounded contexts, clean REST boundaries, production that stays up.
02
Cloud landing
Move production workloads onto Azure or AWS with CI/CD that survives the cutover — GitHub Actions, Bitbucket Pipelines, and the unglamorous work of making Friday deploys boring.
03
API & platform rebuild
Replace tangled backends and aging frontends with structured APIs and a TypeScript stack your team can extend — Angular, React, Vue, .NET Core, Laravel.
04
Product rescue
Take over a stuck web or mobile codebase, stabilize it, then modernize in place. Including the case nobody catalogs: an unsupported desktop system extracted and rebuilt as SaaS.
05
Complex solutions
Software plus the physical setup it depends on. Custom on-site environments, networking, and hardware when the solution cannot live in the browser alone. Offered as part of the engagement — not as a separate IT shop.
Selected work
Confidential by default.
Client names stay off this site. What you see is the shape of the problem and the work — enough to know if we have done your kind of hard thing before.
Education & recreation
Class operations platform
A live product for studios and schools that run on schedules, enrollments, and tuition — restructured from a monolith into modern services without taking the business offline.
Read the case
Print & workshop operations
Shop-floor production workflow
A multi-year modernization of a job manager used all day by print and workshop teams — first making a hostile legacy UI usable, then replacing it with a component-based app operators actually asked for.
Read the case
Distribution & manufacturing
Three-sided corporate ordering network
An order lifecycle that starts with a distributor anywhere in the world and ends on a factory floor — three purpose-built sites, one system, years of production ownership.
Read the case
Product rescue
Unsupported desktop system, rebuilt as SaaS
A vendor-abandoned desktop application with business logic trapped on workstations. We analyzed the system, extracted its database and internal processing, and rebuilt the whole thing as a custom SaaS web application.
Read the case
How an engagement runs
Contain the blast radius. Then move.
We do not freeze the business to make the architecture pretty. Production stays up. Extraction happens in slices. Tests and pipelines are part of the handoff, not a sequel.
01
Diagnose
Map the real system — not the diagram on the wall. Data, deploy path, the jobs that fail silently, the person who still knows the SOAP contract.
02
Contain
Find the blast radius. Put a fence around what can change now versus what has to wait. If the desktop app is the source of truth, we extract before we invent.
03
Extract
Services, APIs, and cloud landing in slices. Old and new run together until the old path is boring enough to turn off.
04
Hand over
Pipelines, tests, and documentation a team can run without us. Dedicated senior attention through the cutover — not a bench that rotates off the account.
Monolith
Billing
Identity
Jobs
Reports
UI
API
Billing
Identity
Jobs
Reports
Web
Services
Capabilities
The stack we actually ship in.
Not a résumé dump. These are the tools that show up in the work — grouped the way an engagement uses them.
Languages
- TypeScript
- C#
- PHP
- SQL
- JavaScript
Frontends
- Angular
- React
- Vue
- Next.js
- Tailwind
Backends
- .NET Core
- Laravel
- Node
- REST APIs
Data
- SQL Server
- PostgreSQL
- MySQL
- Supabase
Mobile
- Ionic
- React Native
Cloud & delivery
- Azure
- AWS
- Vercel
- Docker
- GitHub Actions
- Bitbucket Pipelines
Fit
We are not a generalist shop.
We take
- Hostile legacy and partial rewrites
- Systems with no tests and no vendor
- Monoliths that have to keep running
- The project the last team walked away from
- Software that needs a custom on-site counterpart
We don’t take
- Logo and brochure marketing sites
- No-code landing pages
- Staff-aug with no ownership
- Work we would have to fake seniority on
Ways to work together
Project is the default. The others are on the table.
Most engagements are a defined project. If the shape is different, we will say so — and we will not stretch a project into a retainer to keep a seat warm.
Project
Defined scope, clear deliverables.
Retainer
Ongoing strategic support.
Project recovery
Direction for stalled or troubled projects.
Embedded design lead
Senior leadership within your team.
Before the call
Straight answers.
How does an engagement start?+
A confidential brief. We read it, we ask a short set of questions, and we tell you whether the work is a fit. If it is, a scoped proposal follows. We do not sell a discovery process that exists to bill discovery.
Remote, hybrid, or on-site?+
Remote-first. When a solution needs a custom on-site setup — networking, hardware, a controlled environment — we show up for that part. The software work does not require a seat in your office.
Who owns the code?+
You do. Repositories, pipelines, and cloud accounts stay in your name. We work inside your systems unless you ask us to stand up a temporary one.
Will you sign an NDA?+
Yes. Case studies on this site are anonymized on purpose. Nothing from a brief is used in marketing without written permission.
What does week one look like?+
Access, a working map of the system, and the first containment decision — what we will not touch yet. You should know, in days, whether we understand the actual problem.
Do you only do software?+
Software is the company. Complex solutions sometimes require networking, hardware, or a custom on-site environment. We will take that on when it is required for the system to work — not as a standalone IT offering.
Next
Tell us the unsolvable part.
We take fewer engagements so the ones we take get dedicated senior service. If the work is a fit, you will hear that quickly. If it is not, you will hear that too.
Start a confidential brief