We update your legacy system without developers

• Yes, we can adapt the migration target to your desired technology stack.

• Any additional features or customizations outside the original scope will be adjusted separately based on the estimated effort.

• Yes, part of our process is that we will need a copy of your code to perform the migration. If you have special requirements in this regard, we can review them. For example, we can implement our tools on servers or virtual desktops within your network and run all our processes from there, although this will require additional effort and cost. The LLM calls necessary for code understanding and conversion will always be through cloud providers (Google, Azure, AWS).

• We do not currently support local LLMs. The reason is that the quality of the generated code is still significantly better when using frontier LLMs in the cloud.

• Absolutely. We adapt to your existing pipelines and processes, delivering code accordingly.

• We will evaluate and propose the necessary adaptations, communicating any impact on delivery times and costs.

Timelines vary depending on the complexity and size of the application, but generally you can expect:

• 6-8 weeks for configuration
• 1 average-sized application (10 screens, 10 database tables) every 3 days
• The project start date will depend on our workload at the time, with a typical wait time of 1 to 3 months

It is important to note that this timeframe may vary depending on the client’s availability to provide test scenarios, test data, perform their own functional tests, as well as the speed of interaction we may have from the client’s side for any necessary adjustments. In other words, this is our own pace, but we can adapt to yours as needed.