Karlsruhe · 5 November 2026 · 7 min read
Software development in Karlsruhe: local developer, agency or offshore?
Having software built in Karlsruhe: when does a local developer fit, when an agency, when offshore? With questions for the first meeting and notes on code ownership.
Karlsruhe is an IT city. There are large software companies, many agencies, start-ups from around KIT and quite a few freelance developers. That's good for you as a client, but it doesn't make choosing easier. In this article I explain how the three common routes differ and how to find the right partner for your project. I'm one of those freelance developers in Karlsruhe myself, so I'll also say openly when I'm not the right choice.
The three routes compared
- 01
Local freelance developer
You talk directly to the person who writes the code. Short paths, little lost in coordination, in-person meetings are possible. The limit is one person's capacity: very large projects with many parallel workstreams or round-the-clock availability don't fit here.
- 02
Agency or software company
A team with project management, design, development and often operations. Good for large projects and when contractual cover during holidays or illness matters. In return there are more coordination rounds and overheads, and your contact is often not the person writing code.
- 03
Offshore or nearshore
Development by teams abroad, often with lower hourly rates. It can work if you write very clear requirements yourself and can technically check what's delivered. Time zones, language, legal framework and data protection need extra attention.
None of these routes is fundamentally better. What matters is what your project needs and how much steering you can take on yourself.
What to base the choice on
- Size and duration: a customer portal, an integration or an internal web application is very doable for one person. A platform with many teams over years, less so.
- Your own technical expertise: if nobody in your business can assess code or architecture, you need a partner who explains decisions in plain terms.
- Closeness to the business: if processes need to be understood on site, say in a workshop, warehouse or kitchen, a visit to your premises helps more than any document.
- Data protection: with personal data, contracts, server location and access rights matter. Providers outside the EU bring additional requirements.
- Long-term support: software needs updates. Clarify early who takes care of that after launch.
Questions for the first meeting
Whoever you talk to, these questions quickly show whether the collaboration fits:
- Who actually writes the code, and who do I talk to during the project?
- Can you show me a comparable project that's live?
- What does the first small step look like, and what can I test afterwards?
- How often do I see progress, and how do I give feedback?
- How are changes during the project billed?
- Which technology do you use, and why that one for my project?
- Where is it hosted, and who has access to the servers and data?
- What happens after launch: maintenance, updates, bug fixes?
- What happens if we end the collaboration?
Look for concrete answers. Someone who answers the first-step question by immediately proposing a big specification for several months works differently from someone who starts with a small, usable result. Both can be right; you just should know what you're signing up for.
Code ownership: the most underestimated point
Many clients assume the software belongs to them as soon as it's paid for. Legally, that isn't automatically the case. Under German copyright law, the copyright stays with the developer. What you receive are rights of use, and their scope depends on the contract. So have the following put in writing:
- That you receive comprehensive, unlimited rights of use, including the right to modify the software and have third parties develop it further.
- That you receive the complete source code, ideally continuously in a repository you have access to yourself.
- That domain, hosting account, app store accounts and access to third-party services are in your name or transferable.
- Which components are subject to open-source licences and what that means for you.
- That there's documentation someone else can use to get up to speed.
With me, this is standard: the code lives in a repository you can access, accounts are in your name, and you can carry on with someone else at any time. I think that's fair, and it forces me to write clean code.
Warning signs
- A fixed price for a large project after a short call, without discussing your processes.
- No access to code or progress until acceptance.
- Hosting only with the provider itself, with no way to move.
- Vague answers to the question of who works on the project.
- Not a word about maintenance, updates and data protection.
When I'm the right choice and when I'm not
I work alone, from Karlsruhe, for small and mid-sized businesses in the region and beyond. I'm a good fit if you want a direct contact, if the project starts manageable and is allowed to grow, and if you care about understanding what's being built. Examples are ordering systems, customer portals, internal web applications, apps and integrations between existing systems.
I'm not the right fit if you need a team for several large parallel projects or if contractually guaranteed round-the-clock availability is required. Then an agency or software company is the better choice, and I'll tell you so in our conversation.
More notes