Account inventory
GitHub, GitLab, Bitbucket, cloud consoles, the domain registrar, App Store Connect, Google Play Console, SMS and mapping API accounts: which email each one is tied to and which card pays for it.
Picture an exporter in Gaziantep with a three-person in-house software team building a B2B portal for dealers and a mobile app for the field sales force. Part of the code lives in the personal GitHub account of a team lead who left two years ago; the rest sits in a GitLab instance on an ageing virtual server. The mobile app is published on the App Store and Google Play under a developer account one employee opened in their own name. IDE licences and coding assistant subscriptions are paid in dollars on personal credit cards, with invoices addressed to individuals. The database password is in a text file in a shared folder. Then a large European buyer sends a security questionnaire before placing an order: where is the code, who can reach it, and what third-party open source is bundled inside? Apply helps you choose suitable tools and builds an environment in which the business owns the source, the build process and every release. We work entirely at a distance; the subscriptions themselves are purchased in your company's name, either from the maker or through a dealer of your choosing.
Large customers and foreign buyers increasingly ask the same three things: who owns the code, who is able to change it and what is inside it. The scope is designed so you can answer all three with evidence.
GitHub, GitLab, Bitbucket, cloud consoles, the domain registrar, App Store Connect, Google Play Console, SMS and mapping API accounts: which email each one is tied to and which card pays for it.
Repositories move, with history, issues and merge requests, into a GitHub or GitLab organisation registered to the business. Mobile apps are transferred to developer accounts opened in the company's name.
Login via Entra ID or Google Workspace single sign-on, so switching off a departing employee removes code, pipeline and cloud access together.
Subscriptions such as JetBrains, GitHub Copilot, Docker Desktop and Figma consolidated under one account billed to the company, with a list of who uses what. How services bought from abroad are treated for tax is something you settle with your accountant.
GitHub Actions or GitLab CI with separate test and production environments, mandatory code review before merging to the main branch and sign-off before anything goes live.
Passwords and keys lying in repositories, chat histories and shared folders are tracked down, every one of them rotated, and the replacements stored in a secrets manager.
An automatically generated SBOM listing open source components and their licences, plus regular mirroring of all repositories to a company-owned server at a provider such as Hetzner or OVHcloud.
Ownership comes back to the business before anything is improved, and that sequence is not negotiable.
A video call with the team plus a look through card and invoice statements produces a list of every account, subscription and access right.
Repositories, store accounts and cloud resources are moved into company accounts one project at a time, while development carries on.
Exposed keys are replaced, a secrets manager goes live and approval steps are added to the pipeline.
A check that no unauthorised access remains, a short guide to the environment and a walkthrough with the team by video call.
If your app is published under an employee's store account, in practice it is theirs. Apple and Google both allow an app to be moved to another developer account, but the move needs the current account holder's cooperation and certain preconditions. Once that person has left on bad terms, it can drag on for months, and sometimes the only way out is to publish again as a new app and lose every rating and review. That is why store accounts sit at the very top of our inventory.
Either will serve you well. GitHub stands out for its vast ecosystem and native Copilot support; GitLab puts repositories, CI and issue tracking in one product and can also be self-hosted. What really counts is not the platform but the fact that your company owns it.
Yes, on business plans rather than personal ones. Business plans commit to not training models on your code and let you manage who has a seat. We also suggest a written rule on which repositories the assistant may be used in.
Through an account in your corporate identity or as an outside collaborator, limited to the project's repositories and set to expire. They never see production secrets and their code goes through mandatory review. The transfer of rights to what they write is a contract matter to settle with your lawyer.
No. Apply is not a reseller for these vendors and earns no commission, so our recommendations follow what suits your team. Seats are purchased in the company's name from the maker or any dealer it prefers.
Our time is billed at €55 an hour plus VAT, and you get an estimated quote once the account inventory is done. Licence costs go straight from your company to the supplier.
Tell us how many people write code, where it is kept today and whether you have a mobile app. We propose a tool set and pull your accounts and subscriptions together.
We have your enquiry
A reply will reach you by the next working day at the latest. If your message says work has come to a halt, it goes to the top of the pile.
No such city in our list. Try another spelling, or just pick the closest big city: we work entirely over remote connections, so nothing about the service changes from one province to the next.
The only cookies here are the essential ones: they keep the site running and remember the city you picked. Nothing is used for advertising or tracking. See our privacy notice for more.