Changes as commissioned
On the production system we change what you commission.
IT security teams can check here how we access your systems, how we secure that access and when AI is used. The page also explains what happens if someone on our side is unavailable and where our company is registered.
On the production system we change what you commission.
Access runs through VPN, SSH or your remote desktop, from our own machines, so you do not need to provide a device.
We ask only for the rights the task needs and hand access back when the engagement ends.
We secure our access with SSH keys and, where your system offers it, with two-factor authentication.
Before any change we check whether backups exist and whether they can be restored. We record the result in writing.
On request we design network zones, WAF rules and central logs. We prepare for penetration tests, fix the findings and help after an attack.
Our engineers work on your code. We use AI tools there only where you want them. You can rule them out again at any time.
For legacy systems, conventional development is our default: we read, change, test and document the code ourselves.
If someone on our side is unavailable, we arrange cover on request. We also write the documentation on request, and the repository is normally with you, so the code stays in your hands.
The same applies when the collaboration ends: code, access and documentation stay with you. The How we work page describes how we work, and the About page tells you more about the company.
We work on our own hardware. We set up access to your systems through a VPN, SSH or a remote desktop. We need a device from you only if you prefer that.
Our engineers have worked on these types of system:
Selected projects are described in detail on the projects page, among them ColdFusion in production and under load, email deliverability, a shop flooded by bots and SQL indexes in a shop database.
You receive a first reply within one working day. Please do not send confidential documents through the form.