Service · Custom software development

Open source development

Open source removes two risks in one go: licence costs that climb with every new employee, and dependence on a vendor that may decide to discontinue the product or raise the price. The trade-off is that it demands skill, both from whoever builds the system and from whoever runs it afterwards.

Send an enquiry See the scope

No licence fees

you pay for the work

No single owner

cannot be switched off

The code

is entirely yours

Community

fixes and extensions

What the service covers

Open does not mean free. Part of what you save on licences goes into disciplined maintenance and regular upgrades.

Talk it through with us

Technology selection

We assess maturity, project activity, licence type and how easy it is to hire developers for it in Denmark.

Development

We build on PostgreSQL, Linux, Laravel, Django or Keycloak, for example, and use ready-made components where they genuinely fit.

Pipeline and hosting

Containers, environments, automated builds and deployment, so new versions are released in a controlled way.

Vulnerabilities

Continuous monitoring of dependencies plus a software bill of materials (SBOM). In open projects, flaws become public knowledge immediately.

Licence review

We check that the licence of every component suits your use, so GPL obligations do not come as a surprise during a sale or a tender.

Documentation

Architecture, key decisions and an operations guide, so another team can step in without starting over.

How we deliver it

Development time is roughly the same as on proprietary platforms. The saving comes from not paying for each additional user.

Assessment

We analyse the task and shortlist candidates. Sometimes no open alternative of the required quality exists, and we will say so.

Proof of concept

We test the technology on a small, well-defined slice of the task before you commit.

Development

We build on maintained, well-proven components.

Handover

Code, architecture description and guides for installation and upgrades.

A library maintained by one person in their spare time will one day stop receiving updates. Any vulnerabilities in it stay open, and replacing it inside a running system can be painful. That is why we look beyond features when choosing components and check who is behind them and how often fixes are released.

Common questions

On licences, definitely, particularly as user numbers grow, because that is exactly what proprietary platforms charge for. On development and operations the gap is small. Compare the total spend over three to five years.

Any developer who knows the technology, and that is the whole point. The code and documentation are yours, the technology is public, and the skills are available on the market. A closed system from one supplier offers no such freedom.

Many eyes review open code, but discovered flaws also become known to everyone at once. What matters is update discipline, which fits neatly with the NIS2 requirements on supply chain risk management.

Related services

View the whole area

Service End-to-end development Discovery, design, code, testing and ongoing care from one team Service Mobile app development iOS and Android apps published under your own accounts Service Dedicated development teams Developers and testers in your team without hiring Service System integration Data moves between systems with no retyping

Let us look at an open platform

Describe the task and what frustrates you about your current licences. We will propose a technology and also point out where the open option is weaker.

Email
office@apply.dk

Coverage
All of Denmark, delivered remotely

I agree that Apply may handle my details as set out in the privacy policy