Knowledge base

IT is a great and exciting world to be in.
All who have passion for it will understand why we have created these pages.
Here we share our technical knowledge with you.
ProgrammingAICloudManagementMobileDB & AnalysisSafetyOtherArchitectureTips

Cloud development


Libor Beenyi (CTO), Jana Cilli (CMO)

We have decided to transfer development to the Cloud. If your company faces such a decision, we offer you a list of arguments ‘for and against’ that we considered when migrating to the Cloud. We will also share our experience with practical implementation. We will be glad if this information is beneficial to you, in case your company approaches such milestone.


 Why migrate your software development to the Cloud?

  • Potential - if you create solutions in Cloud, you can constantly keep in touch with modern technologies. If the market is affected by some technological innovation in the future, there is much higher chance that your solution will be compatible with it, if you are in the Cloud.
  • Flexibility – response time to changes and trends in IT is lower, if you have your solution in the Cloud. Of course, it is also related to the ability of your company to respond flexibly to business opportunities.
  • Integration – integration can be done in parts to avoid the risk of badly chosen technology. If a tool is found to be inadequate after half a year, it can be replaced.
  • Visibility -  DevOps philosophy presupposes the cooperation of individual members of the project team. The Cloud enables it from technological point of view. The work of each project member is compiled into one transparent unit accessible to everyone. Everyone sees what they have contributed and what are the benefits of their work. All of this in real time.
  • Increasing development efficiency - has a direct impact on reducing the cost of SW development.

What to be aware of before migrating to the Cloud?

  • Phasing is essential, otherwise we can practically kill the development with one tiny problem
  • Beware of intercontinental transfer data - these are additionally charged
  • Communication in the team is crucial. People need to be prepared to use new tools or use existing tools in a different way
  • Adopt and adapt - some internal processes will need to be changed
  • Prepare for rollback - every phase must be evaluated in relation to price and benefits

What will be the parts of your Cloud migration project?

Transferring source codes and introducing a “feature branch“ model
Work visualisation (bugs, tracking tasks from sprint/scrum)
Controlled migration of products to the Cloud
Transfer of continuous integration server into the Cloud
Automated testing in the Cloud
Automated deployment


Text 2
Text 3
Text 4


Text 5
Text 6
Text 7
Text 8
Text 9

Other articles


Find out more

Knowledge base

Quick start

Contact us for a free consultation on your business needs!
After the discussion we will perform mapping of the processes and analyse the current state.
You will receive variety of scenarios to choose from discribing different ways how to solve your issue.
Contact us