Service · Software and licences

Developer tools

For example, a software house with fifteen people: code spread across three places, JetBrains paid for on personal cards and claimed back as expenses, and the production server password sitting in a two-year-old Slack message. Together we choose the tooling and build a set-up in which the codebase and the release process are company assets, independent of whoever is on the payroll this year. All of it is configured remotely.

Company-owned
seats and accounts, not personal
Source code
in an organisation you control
Advice
we do not resell licences
Hands-on
set-up, not just a shopping list

Included in this service

Which editor the team prefers matters far less than where the code lives and what route it takes to become software running for your customers.

Talk the scope through with an engineer

IDEs and editors

JetBrains bundles, Visual Studio subscriptions, GitHub Copilot. We help settle the edition and seat count and tie every licence to a work account, never to a Gmail address.

Repositories

A company-level space on GitHub, GitLab or Azure DevOps, split into sensible teams, with protected branches and 2FA enforced for every member.

Builds and releases

A pipeline that compiles the application, runs the tests and publishes a version to staging by itself. No more dragging files over FTP late on a Friday.

Secrets and access

Passwords, API keys and certificates held in a secrets manager rather than in config files committed to the repo.

Contractors

External freelancers see just the projects assigned to them, and only while their contract is live. When it ends, access is withdrawn automatically.

Library licences

We check which open source licences apply to the libraries inside your product. GPL code in an application you sell is something to know about before a client signs. The legal assessment stays with your lawyer.

How we work together

Timing depends on the number of projects and repositories, and the schedule is agreed at the start.

01

Current state

Where the code sits, who can reach it, whose name the subscriptions are in, and how a new version ships today.

02

Selection

Products and quantities sized to the team, its stack and your customers' demands, for instance on where code may be stored.

03

Configuration

Organisation, permissions, pipelines, secrets and repository backups, done remotely while development carries on.

04

Handover

Written notes on the environment and an hour on Teams or Google Meet for the team to ask questions.

Code on a developer's personal account is not really company property. When that person leaves, the entire history of changes can go with them, and copyright questions then need sorting out with a lawyer. So step one is transferring repositories to a company-owned organisation.

Questions and answers

Usually not. A hosted service takes server administration, updates and backups off your hands. Self-hosting is worth it when a client contract bans code outside your infrastructure, or when everything must remain in the EU with one named provider.

Yes, provided you pick a plan whose current terms rule out training models on your code (we check them before purchase), and agree a few plain rules: no client data, no secrets pasted in. We apply those settings at organisation level so they do not hinge on each developer's good intentions.

Usually as a per-user subscription, bought from the vendor or one of its partners. What matters is that the invoice names the company and the seat is linked to a work account. A subscription on a private address walks out with the employee and the money is gone.

For much of the daily work, yes: Git, Docker, VS Code and countless free libraries already carry most teams. Budgets tend to go on commercial IDEs, AI helpers and hosted build capacity. Alongside that we read through the terms attached to third-party packages bundled in anything you sell.

Get your development set-up in order

Tell us how many developers you have and where the code is kept today. We will suggest a toolset and clear out redundant subscriptions.

Hours
Mon-Fri 8:00-18:00 CET, reply within one working day
Meetings
Online via Teams or Google Meet

We set strictly necessary cookies only: they keep the site running and remember the city you chose. Nothing here is used for advertising or tracking. More in our privacy policy.