Platform selection
We assess the maturity of the project, the activity of the community and the availability of specialists on the market.
Open does not mean free: the saving on licences is offset by the demands of maintenance.
We assess the maturity of the project, the activity of the community and the availability of specialists on the market.
Implementation on the chosen platform, using ready made components where they fit.
Deployment, environment, automation of builds and updates.
Control of vulnerabilities in the libraries used, since in open projects they are public and known to everyone.
A description of the architecture and the decisions, so that another developer can pick the project up.
A procedure for updating the platform and its dependencies, without which the project ages quickly.
Timelines are comparable with commercial platforms. The saving shows up not in development but in the absence of per user payments.
We look at the task and select a platform. Sometimes an open analogue of the required quality simply does not exist.
We check on a limited area that the platform really covers the requirements.
Implementation with a priority on using proven components.
Sources, documentation, instructions for deployment and updating.
The main risk of open platforms is abandoned dependencies. A library maintained by a single enthusiast stops being updated, and known vulnerabilities stay in it. We track the state of the components in use and warn in advance when something needs replacing.
On licences yes, especially as the number of users grows: commercial platforms often charge exactly by that. On development and maintenance there is almost no difference. What you need to count is the total cost over three to five years.
Any developer who knows the platform, and that is the whole point. We hand over the sources and the documentation, the platform is publicly available, specialists exist on the market. A proprietary solution from a single contractor gives no such freedom.
Open code is reviewed by a large number of people, but its vulnerabilities are public and attackers learn about them just as fast. The key is regular updating of dependencies. A project without updates is more dangerous than a closed one.
Tell us about the task and your concerns over licences. We will select a platform and say honestly where an open solution loses.
Request received
We can already see it. We will reply within one business day, and for urgent matters we will bring in the on-duty engineer right away.
City not found. Please check the spelling.