Service · Software and licences

Developer tools

Consider a Valencia software studio with eleven staff and two freelancers who come and go with each project. Its code is spread across the founding partner's personal GitHub account, a GitLab an intern once set up and a Bitbucket inherited from a client. JetBrains and Copilot seats are charged to private cards and reclaimed through expenses, and the live database password was posted in a Slack thread back in the day and never rotated. We guide the tool choice and hand back an environment in which source, builds and releases are company property. Configuration is done remotely; subscriptions are bought by you, direct from each vendor.

Company-owned
accounts and seats, never personal
Freelancers
access that expires by itself
No commission
we resell no licences
Working set-up
rather than a list of recommendations

What falls within the scope of this service

The work revolves around three questions that large customers and public bodies routinely put to a software supplier: who owns the code, who can change it, and what is inside it.

Pin down the details with one of our engineers

Move to an organisation

Repositories transferred from personal accounts into a company-owned GitHub, GitLab or Bitbucket organisation, keeping history, issues and pull requests intact.

Single sign-on

Access to the code platform through the company's Entra ID or Google Workspace accounts, so disabling someone in one place removes their access everywhere.

Environments and releases

GitHub Actions or GitLab CI pipelines with separate test and production environments, and mandatory approval before anything reaches production.

Secrets rotated

A list of passwords and keys that have travelled through chats, emails or files; every one is changed and the replacements are stored in a secrets manager.

Freelancers with contracts and end dates

Per-project access with an expiry date, plus a review with your lawyer of the rights assignment clause, since a freelancer's code does not pass to the company by default.

Software bill of materials

A list of the open source libraries and licences in each product, something more and more customers ask for and useful if NIS2 supply-chain duties reach you.

Copy outside the platform

Automatic mirroring of repositories to a company server, for example at Hetzner, OVHcloud or Arsys.

How the engagement unfolds, one stage at a time

Order matters: control of the accounts comes back first, and everything else is improved afterwards.

01

Account inventory

Who has access to what, on which platforms and under which email; which subscriptions exist and who pays for them.

02

Organisation and SSO

Repositories moved and connected to Entra ID or Google Workspace without disrupting day-to-day work.

03

Pipelines and secrets

Exposed credentials rotated, a secrets manager introduced and releases gated by approval.

04

Leaver check and handover

We confirm no outsider still has access, document the environment and walk the team through it on video.

Moving a password into a vault is not enough if it once appeared in Slack. Anyone with access to that channel, former staff and freelancers included, may have copied it. An exposed credential gets changed, not hidden. That is why rotation comes before any other improvement to the environment.

Common questions

GitHub is the most common and has the broadest ecosystem, Copilot included. GitLab is handy if you want repositories, CI and issue tracking in one tool, or need to install it on your own server. For most small teams either will do; what matters is that it belongs to the company.

Frequently: code and data kept in the EU, ENS compliance where the system requires it, documented access control and, increasingly, a software bill of materials. We help prepare that paperwork; ENS certification itself is granted by an accredited body.

Through an account tied to a corporate identity or as an outside collaborator, restricted to the repositories of their project and set to expire. No access to production secrets, and mandatory review of their code.

No. Repositories move project by project, outside the busiest hours, and old links keep redirecting for a while.

Our work is €75 per hour + VAT, or a fixed price after the inventory. We resell no licences and take no commission: your company pays subscriptions straight to the vendor.

Tidy up your developers' environment

Give us a headcount for the dev team and tell us which services host your code at the moment. We come back with a proposed toolset and a plan for the subscriptions.

Hours
Monday to Friday, 9:00-18:00 Spanish time (CET), answers within a working day
Meetings
Video calls via Google Meet or Teams

This site only stores the cookies it needs to work and to remember your chosen city. No advertising or tracking cookies are set. See our privacy policy for the details.