Service · Software and licensing

Tools for developers

Suppose a web agency in Graz has nine employees and brings in three freelancers depending on the project. Its source code is spread around: some in a private GitHub profile belonging to a co-founder, in a GitLab instance an intern set up years ago on an ageing virtual machine, and the rest in a Bitbucket space taken over from a former customer. IDE licences and AI coding assistants are paid on private credit cards and claimed back as expenses, and the production database password sits in a chat thread from two years ago. Then an industrial client in Upper Austria sends a questionnaire before awarding a contract. Where is the code kept, who can access it, and which open source components does it contain? We help you pick suitable tools and build an environment in which code, builds and releases belong to the business. Everything is done remotely, and you take out the subscriptions directly with each vendor.

Company accounts
instead of personal logins
Freelancer access
that expires automatically
No commission
we do not resell licences
Configured
not merely recommended

Everything this covers

Buyers from industry and financial services keep raising the same trio of questions: whose property is the code, who is able to modify it, and what third-party parts does it include? Everything below is aimed at letting you reply with proof rather than assurances.

Settle the details with an engineer

One organisation for everything

Transferring every project from private profiles into a company-held GitHub or GitLab organisation, with commit history, tickets and pull requests preserved.

Sign-in through the corporate identity

Single sign-on with Entra ID or Google Workspace. When someone leaves, one click removes their access to code, pipelines and cloud consoles alike.

Licences on the company invoice

JetBrains, GitHub Copilot, Docker Desktop and similar subscriptions moved onto a single business account, with a clear view of who uses what. No more duplicate plans or awkward conversations about personal cards.

Pipelines with guard rails

Build and deploy workflows in GitHub Actions or GitLab CI that keep staging apart from live, require a second pair of eyes on every merge and need explicit approval for each release.

Getting secrets out of the code

Hunting through code, chat logs and historic tickets for keys and passwords, rotating each one and keeping the replacements in a dedicated vault.

A bill of materials for your software

An automatically generated SBOM listing every open source component and its licence, so supply-chain enquiries from customers no longer mean a late night.

An independent mirror

Every repository is continuously replicated to a machine under your own control, at Hetzner or Exoscale for example, so a locked or lost account never means lost code.

Our working method

First the business regains control of its accounts and code; only then do improvements follow. We do not change that order.

01

Stocktake

Who can reach what, on which platform, under which email address, and whose card pays for which subscription?

02

Organisation and SSO

Repositories migrated and linked to the corporate identity, project by project, without bringing development to a halt.

03

Clean-up and hardening

Replacing exposed credentials, introducing a secrets manager and adding approval gates to pipelines.

04

Handover

We confirm that former staff and outsiders are locked out, write up how everything fits together and present it to the developers over video.

Code written by freelancers does not automatically belong to you. For employees, usage rights to software created as part of their job largely rest with the employer. For independent contractors, it depends on what the contract says. If the contract is vague, that can become expensive when the business is sold or a dispute arises. We check whether technical access matches the contractual position; for the contracts themselves we recommend speaking to your lawyer.

Frequently asked questions

Either will do the job. GitHub has the largest ecosystem and Copilot built in. GitLab bundles source control, pipelines and tickets and can be self-hosted in an Austrian data centre, which some clients appreciate. What matters more than the platform is that the company owns it.

Traceable access control, approvals before release, an up-to-date SBOM and a documented process for handling known vulnerabilities. That covers most questionnaires. Formal certification such as ISO 27001 comes from an accredited auditor, and we can support the groundwork.

Either give them an identity in your own directory or invite them as a guest, scoped to the relevant repositories only and with a built-in end date. Live credentials stay out of reach, and nothing they write is merged without a colleague reviewing it.

No, and that is deliberate. We hold no partner agreements with vendors and earn no commission, which leaves us free to recommend whatever suits your team. You buy subscriptions directly from the vendor or from a reseller of your choice.

Our work is charged at €110 per hour plus VAT, and you receive a quote once the stocktake is complete. Licence fees are paid by your company straight to the provider.

Put your development environment in order

Let us know how many people write code and where it lives today. We will propose a toolset and sort out accounts and subscriptions.

Availability
Monday to Friday, 8:00-17:00 Austrian time (CET/CEST), reply within one working day
Meetings
By video on Microsoft Teams or Google Meet

We only use cookies that are technically required: to run the website and to remember the location you picked. There are no advertising or tracking cookies. Details are in the privacy notice.