Software keeps running long after its assumptions stop holding. An upstream API renames a field. A vendor retires an endpoint. A client that can’t be rebuilt still expects the old shape of the data. The source is lost, frozen, belongs to someone else, or simply isn’t worth reopening. Something has to sit in between and bridge the gap.
Aftermarket borrows its idea from cars. A whole industry of parts and independent repair shops grows up around products their makers don’t own. Aftermarket is that for software: a family of open-source developer tools that repair, adapt, test and preserve software after release, without changing its source.
The Pitch in Four Numbers
- 565 tests, all passing.
- 12 of 12 old client checks passing through AfterAPI.
- 12 of 12 old shop reports reading the same through AfterSchema views.
- 0 third-party dependencies.
The Toolkit
It started with AfterPatch, a small Go reverse proxy configured in YAML that repairs HTTP traffic with rules you can read and review: rewrite an endpoint, fix a header, rename or reshape a JSON field, all without touching the service behind it. The family has grown from there:
- AfterAPI keeps an old client working after its whole API is replaced.
- AfterTest records real traffic as test fixtures, with credentials stripped out.
- AfterDiff replays recorded traffic against two versions of a service and lists the differences. Its live shadow mode compares a new version on real traffic while clients still get their answers from the old one, and the candidate can never slow down or break what clients receive.
- AfterConfig changes vendor JSON, YAML, TOML or .env config without editing the files.
- AfterHook sends a signed webhook when a file, folder, endpoint or database table changes.
- AfterGuard puts rules in front of an old app that has no login and rejects requests they don’t allow.
- AfterSchema keeps old reports and scripts working after a SQLite database changes shape.
- AfterBridge serves an old app’s CSV exports and SQLite files as a read-only JSON API.
More are planned, including one called Afterlife, and a few research ideas sit behind those. They arrive one at a time.
How It Works
Every tool sits beside the software, never inside it. A proxy between client and server. A view over a database. A watcher on a folder. The original stays exactly as it was, which means you can remove the fix as easily as you added it, and you can review the rules like any other change. The whole family ships with no third-party dependencies.
Who It’s For
- Teams with old clients that can’t be rebuilt, like mobile apps in the field, embedded devices and partner integrations.
- Anyone hit by a vendor API change they didn’t ask for.
- Companies running legacy apps whose exports and databases still matter.
- Teams releasing a new service version who want to see how it behaves on real traffic before switching.
Limits
Aftermarket fixes the edges of software, the traffic, the config and the data, not the logic inside. A bug deep in the code still needs the code. Only part of the planned family is out so far, and each tool covers a specific job instead of trying to be a platform.
The Four-Question Screening
Every project featured here gets the same four questions, the way you’d screen a startup idea.
1. Where is the money in it?
The tools are open source under Apache 2.0, with no paid tier yet. Legacy software is one of the biggest hidden costs in IT. Companies pay heavily to keep old systems running, to integrate them with new ones and to avoid rewrites. The paid paths are support and long-term maintenance for the tools that end up in production, consulting to design the fixes, and a managed version of shadow testing and traffic recording for teams releasing new service versions. Like the car aftermarket, the money is in keeping things running.
2. What real problem does it solve?
Software that can’t be changed but has to keep working. Rebuilding an old client or rewriting a legacy app is slow and risky, and often not possible at all. A small fix at the edge gets it working again today.
3. The technology in plain words
When a new wall socket doesn’t fit an old plug, you don’t rewire the lamp. You buy an adapter. Aftermarket makes adapters for software: little pieces that sit between two programs and translate, filter or record what passes between them, so the old one keeps working.
4. Moat and differentiation
API gateways and service meshes can do some of this, but they’re big platforms built for new systems. Aftermarket is a set of small, focused tools for old ones, each doing one job with readable rules. The family structure is the edge: one place to go for every “keep this old thing working” problem. The moat that can grow is that catalogue and a reputation for fixes that are safe to drop in, like a shadow mode that’s tested never to hurt live traffic.
Why It Matters
Most software in the world isn’t new. It’s running, it’s depended on, and it’s slowly breaking as everything around it changes. Tools that keep it working without a rewrite save a great deal of money and risk.
Follow the Project
Start with the quick start, browse the use cases and the roadmap, read about AfterDiff’s live shadow mode, or get the code from the Aftermarket repository on GitHub. Aftermarket is listed with the other open-source projects on SoftDevStudio.com, and more featured projects are in the Projects section.