+48 501 250 220

Your team needs support? We take over a defined part with an agreed result

Your team is at capacity, a specific skill is missing, or you need a second opinion before an important decision? We take over a defined part: a module, the backend for your frontend, an interface, a migration or a code review. We work in your repository and ticket system, and the code and the knowledge stay with you.

Discuss your case Engagement models
  • Code in your repository, tasks in your ticket system
  • In German, Polish and English, in the same time zone
  • Reply within one working day
A team board with four task cards; one card moves on an orange arc to our part in an orange frame; both parts lead down into one repository line with commits, our commit orange

When teams come to us

Support for a team means a defined part of the work with an agreed result: we take it over, we are accountable for the result, and we hand it back in a state in which your team can carry it on.

Your team cannot keep up

The list of tasks grows, a deadline comes closer, and filling a position takes months. We take over a defined package of work, such as a module or a group of tickets with a common goal, and your team stays with its priorities.

A specific skill is missing

ColdFusion and Lucee, PHP with Smarty, Linux, MySQL and MariaDB databases, email deliverability or security: when your team lacks experience in one area, we take over that part and pass the knowledge on with the result.

A second opinion before a decision

Rewrite or keep maintaining, which way to migrate, will the architecture carry the growth: we review the code, the architecture or the plan and hand over a written assessment with risks and options. More on that in the section on the second opinion below.

A separate project for an external provider

An interface to a partner's system, a migration, a document service or a new module that does not have to be built in your team: we deliver it as a project of its own, at a fixed price or on time and materials (engagement models).

Part of the project: your frontend, our backend

Your team builds the user interface and we build the backend with the API, the database and the deployment, or the other way round. The boundary is an interface agreed in writing before the first line of code is written.

A team frame in the middle, around it five icons on orange connectors: an hourglass, a puzzle piece, a line forking into two arrows, a parcel and a frame split in two whose right half is orange

How we share the work with your team

  1. Intro call

    The goal, the deadline and the part you want to hand over. We tell you openly whether and how we can help.

  2. Scope in writing

    What we take over, what stays with you, what the result is and how we check it together.

  3. Access in your tools

    Repository, ticket system and test environment. On our side, one contact person.

  4. Work in small steps

    Changes reach your repository in small portions that your team can review. You see the progress in your ticket system.

  5. Handover

    Documentation in the repository, a walkthrough with your team, and code that has been yours since the first day.

Your frontend, our backend

A split along an interface works when the boundary is settled before both sides write code. So we start with the description of the interface and finish with who runs the part after the launch.

  • The interface first. We describe the endpoints, data formats and error codes together with your team, for example in OpenAPI, and keep the description in the repository.
  • Something to connect to early. A test environment with sample data is available from the start, so that the frontend can be built in parallel before the backend is ready.
  • Changes in the open. Every change to the interface goes through the description and a new version, never through a quiet fix on one side.
  • Acceptance by criteria. For every part we agree how to tell that it works, and we check it together.
  • Deployment and operation settled up front. We write down who deploys, who monitors and who responds to errors after the launch.

We split the work the other way round in the same way, when your team runs the backend and a new frontend for an existing system falls to us, or when we take over a single module or an interface to another system.

A browser window on the left, the description of an interface labelled API in the middle, a server and a database in an orange frame on the right; requests and responses run on two parallel lanes, the lanes to the backend orange

A second opinion before a decision

Before a big decision it pays to have someone from outside the project look at the code and the plan. We review:

  • the code and the architecture of the application, also in ColdFusion and Lucee and in older PHP,
  • a plan to migrate or to rewrite the system,
  • servers and databases, for example the speed of queries,
  • the preparation for a penetration test.

The result is a written assessment with risks, options and an estimate of the effort. The assessment is yours, whoever does the further work. We offer several such reviews as entry products at a fixed price: below and on the page How we work.

A sheet of code, an arrow to a report sheet in an orange frame with orange ticks, and from it two branches to the options A and B

The code and the knowledge stay with you

The most frequent worry about outside support is: what if the knowledge stays with the provider? That is why we work from the start so that your team can take a part back at any time.

  • The code is in your repository from the first day, in Git or SVN, and we keep the tasks in your ticket system.
  • We write the documentation next to the code, in the repository, not in a separate tool.
  • We close every part with a walkthrough with your team: how it works, where its limits are and what makes sense next.

We speak German, Polish and English, in the same time zone as your team.

The main line of a repository with commits runs to the right; an orange branch with three commits leaves it and joins it again; a sheet of documentation hangs on a commit of the main line

A second opinion at a fixed price: a review with a written result

Legacy review

For companies with a system that nobody knows well any more: before an update, before a migration or when changing service provider.

  • Inventory of versions and dependencies
  • Map of application, database, server and email
  • Risk register covering security, support and knowledge
  • Assessment of backups and restores
  • Recommendation “stay, upgrade or migrate” with an options matrix that also covers “move into a container” and “expose as an API”
  • Effort estimate in days

The price covers one system, meaning one application with its database and its server. We price further systems individually.

What the result contains

A written report with inventory, risk register, recommendation and effort estimate. The report is yours.

from €3,800 excl. VAT

Typically 5 working days

Request a legacy review

ColdFusion check

For companies with an application on Adobe ColdFusion or Lucee that want to know whether their installation is still supported and run securely.

  • Version and patch level (Adobe ColdFusion 9 to 2025, Lucee 5 to 7)
  • Reachability of the Administrator and RDS
  • JVM, Tomcat and TLS
  • Backups, scheduled tasks, data sources and outgoing email via cfmail
  • Options for the platform: stay on current patches, upgrade the version or migrate to Lucee

The check does not cover application logic or code. That is what the legacy review is for.

What the result contains

A written list of findings in order of priority, with the options and a recommendation. The list is yours.

from €2,400 excl. VAT

Typically 3 working days

Have your ColdFusion installation checked

Database check: MySQL and MariaDB

For companies whose application depends on a MySQL or MariaDB database and who want to know what happens in a failure and whether yesterday's data can really be restored.

  • Backups: what is backed up, how often and where the copies are kept
  • A restore test on a separate system, with the time it takes measured
  • Replication and resilience: what exists and what is missing
  • The slowest queries and missing indexes
  • Version, support status and configuration
  • Recommendation: backup, replication or cluster, depending on your needs

A cluster such as MariaDB Galera protects against the failure of a server, not against deleted data. That takes tested backups, which is why we start with the restore test. We agree with you on the system it runs on. We change nothing on your production database.

What the result contains

A written report with the result of the restore test, the risks in order of priority and a recommendation with the effort involved. The report is yours. If you wish, we then set up the solution, including a Galera cluster.

from €1,900 excl. VAT

Typically 2 working days

Request a database check

Defined parts from our work

  • A table of rows with a long arrow down all of them labelled ALL and one orange arrow from an index card to a single row labelled ref

    SQL indexes in a shop database: from full scans to microseconds

    A shop database without indexes worked as long as the tables were small. At 500 000 orders and 1.75 million order items every filter and every join came down to a full scan. We measured exactly what the missing indexes cost, added the right ones, and documented the traps that make an index useless even though it exists.

  • A large empty frame labelled RAM 40 GB with a small frame labelled JVM 1 GB inside, full of blocks, orange blocks spilling over its top

    ColdFusion under load: diagnosing and fixing the JVM heap space error

    An Adobe ColdFusion application ran without complaint at low traffic and returned errors and slowed down at peak hours. We reproduced the problem on a real database, measured the exact point at which the JVM heap runs out, and fixed the memory configuration, with the same load test before and after as the proof.

  • A browser, a box labelled Apache and three lanes to PHP, PHP and CFML; the CFML lane and box are orange

    ColdFusion 2025 in production behind Apache: five traps that are not obvious

    We prepared a production installation of Adobe ColdFusion 2025 on Debian 12, behind an Apache 2.4 that already serves several other sites. The installation itself takes 34 seconds. The attention went into the connector and the configuration details that are easy to miss: an error 503 caused by IPv6, mappings that reach into every virtual host, and a profile that quietly adds a debugger.

Questions about support for your team

Can we hand over only part of the project, for example the backend?

Yes. The boundary is the interface: we describe it together with your team before the first line of code is written, and we provide a test environment with sample data from the start, so that the frontend can be built in parallel. We also agree in writing who deploys and who runs the part after the launch. In the same way we take over a single module, an interface to a partner's system or a new frontend for an existing backend.

Do you review code or plans that someone else prepared?

Yes. We review the code, the architecture, a migration plan or a server, and hand over a written assessment with risks, options and an estimate of the effort. The assessment is yours, whoever does the further work. We offer several such reviews at a fixed price; they are on the page How we work.

How does the knowledge stay in our team?

The code is in your repository from the first day and the tasks in your ticket system, so your team sees every change. We write the documentation next to the code, in the repository. We close every part with a walkthrough with your team: how it works, where its limits are and what makes sense next. That way you can carry it on at any time, on your own or with us.

Do you work with Jira, Git and SVN?

Yes, with Git and with SVN. We manage tasks in Jira or in the tool you already use. The code lives in your own repository and therefore stays in your hands.

When can you start?

You will receive a first reply within one working day. When we begin work depends on our current workload and on the scope. We give you a binding answer in the intro call. If it is urgent, the 48-hour emergency assessment starts as soon as we have access to the system.

How good is your German?

Perfect: we speak German natively and fluently. Our engineers have worked with German-speaking clients for years. Meetings, quotes and documentation are written in German; more on the page German-speaking IT partner.

Which part would you like to hand over?

A few sentences about the system, the technology and the part in question are enough. We tell you openly whether and how we can help.

Fields marked optional can stay empty.

Reply by email

For a call back we only need your phone number: emergencies around the clock, otherwise within one working day.

Which system, which technology, what do you want to achieve? Please do not send passwords or confidential documents.

Reply within one working day · without obligation

We use your details only to answer your enquiry. Prownex IT Services Sp. z o. o. is the controller. Retention and your rights are described in the privacy policy.