Stacks we support
The older technologies we are willing to take on
If your software runs on something on this list, we can look at it. If it is not on the list, write to us anyway.
Tier A: supported in our plans
Common stacks we take on as a matter of course. They fit inside a Support Plan after a Takeover Assessment.
In our plans
PHP, WordPress and Laravel
Older PHP applications, WordPress sites with custom plugins and themes, and Laravel and CodeIgniter apps whose builder is gone.
In our plans
Python 2, Django and Flask
Python applications on end-of-life versions, including Python 2 code, older Django releases and Flask services.
In our plans
ASP.NET and .NET Framework
ASP.NET Web Forms and MVC applications and other .NET Framework software running on aging Windows servers.
In our plans
Java, Struts and Spring
Java web applications built on Struts, older Spring releases or application servers that have not been updated in years.
In our plans
Ruby on Rails
Rails applications on older Ruby and Rails versions, often with gems that have been abandoned.
In our plans
Node.js and Express
Node.js services and Express apps on old Node versions with large trees of packages.
Tier B: by arrangement
Older stacks we take on by arrangement. We scope each one in writing, and may bring in a specialist for part of the work.
By arrangement
Classic ASP
Classic ASP and VBScript sites that still run business processes on older Windows servers.
By arrangement
Visual Basic 6
Desktop applications written in Visual Basic 6 that a business still depends on.
By arrangement
ColdFusion
ColdFusion applications on older Adobe ColdFusion or Lucee servers.
By arrangement
Delphi and Object Pascal
Delphi applications, often desktop programs with a long history and a loyal user base.
By arrangement
FoxPro and Visual FoxPro
Visual FoxPro applications and the data tables they keep.
By arrangement
PowerBuilder
PowerBuilder applications with DataWindow-based screens and database back ends.
Tier C: by arrangement
Specialized and long-lived platforms, supported by arrangement after a first conversation. We will tell you plainly if we are not the right fit.
By arrangement
COBOL and mainframe
COBOL programs and batch processing on mainframes or emulated environments.
By arrangement
RPG and IBM i (AS/400)
RPG programs on IBM i systems, often called AS/400, running core business functions.
By arrangement
Fortran
Fortran codes used for calculation, modeling and scientific or engineering work.
By arrangement
Perl and CGI
Perl scripts and CGI programs that quietly run forms, reports and back-office jobs.
By arrangement
Lotus Notes and Domino
Lotus Notes and Domino databases and workflows that hold business records.
By arrangement
Oracle Forms and Reports
Oracle Forms and Reports applications on older Oracle application servers.
By arrangement
Microsoft Access
Microsoft Access databases and front ends that grew into daily business tools.
Not on the list?
Tell us what your software runs on. We reply by email and say honestly whether we can help, whether someone else is a better fit, or whether you do not need help yet.
Tell us what you have
In two weeks we know it, document it, and keep it running. Send a few lines about your software and we will reply by email.