What is system support?
It is keeping a system running and evolving after it goes into production. It includes fixing bugs, upgrading versions, watching performance, backing up and building the adjustments the operation asks for. A system without support ages fast and becomes a risk.
We have systems in continuous evolution since 2019. The oldest one has passed fourteen hundred code deliveries and now has more than 160 database tables, because the client's operation grew and the system kept up. See the port operations case.
When should you modernize instead of rewriting?
Almost always. Rewriting from scratch stalls the operation while the new system gets ready, and it tends to repeat the old one's mistakes. We prefer to modernize in parts: upgrade the base, isolate the most troublesome module, rebuild it and move to the next. The operation keeps using the system the whole time.
One example is the offshore passenger transport case, where a single-client system is being redesigned as a platform for several operators.
How does a security review work?
We read the code and build a matrix of route, action, profile and relationship to the record. The goal is to find actions the screen hides but the server accepts. Findings come out with a priority and a proposed fix, and the acceptance rule is simple: a denied request changes no data, attaches no files and sends no emails.
The same review covers personal data. ID numbers masked on public pages, records kept out of logs, consent recorded and each profile's access limited to what it needs.
What infrastructure do you operate?
AWS, Google Cloud, Cloudflare and the client's own servers, with automated deployment and containers. We set up error and uptime monitoring, automatic backups and a recovery playbook.