# Software audit and code review > Your provider has been reporting “almost done” for weeks, an investor wants to know what the software is worth, or you are asked to approve an expensive rebuild you cannot judge. A code review gives you an independent look at code and architecture before you put a lot of money into one direction. With a written report and no obligation to build with us afterwards. Page: https://fragonstudios.com/en/services/software-audit/ Updated: 2026-11-13 ## In short - A code review with us costs €1,200 to €4,500 and takes 1 to 3 days, with a written report. - Tech due diligence for investors takes 3 to 5 days and is billed by effort at €190 an hour. - The answer to your question is at the start of the report, clear without programming knowledge. Then come prioritised findings with reasons and next steps. - The audit commits you to nothing. We also recommend solutions we do not build ourselves. - A code review is not legal advice and no guarantee that the software is free of bugs. ## When is a software audit worth it? **Whenever an expensive decision is coming up and nobody in-house can look at the code independently.** - **Before taking over a codebase**: What are you getting into? For existing apps we clarify that in an audit of two to three days. - **When the project is not moving forward**: Deadlines slip, fixed bugs come back. We say what the cause is and what it takes. - **When the developer leaves**: Can another team carry on without them, and what is missing for that? - **Before a major rebuild**: Move it unchanged, replace it step by step, or rebuild it. We recommend one path, with reasons. - **GDPR check**: A technical review against GDPR Art. 25 and 32, with improvements you can put in place quickly. No legal advice. - **Tech due diligence**: For investors before an acquisition, with a risk score and an estimated remediation cost. **For a system that has grown over time and is to move to the cloud, we assess all three paths before you commit.** You are taking over software from another provider and want to know what you are getting into. Or the person who built everything is leaving your company or the provider. The review shows whether another team can carry on and what is missing for that. A system that has grown over time is to move to the cloud, and the team disagrees. We assess the three paths, meaning moving everything unchanged, replacing it step by step or rebuilding, and recommend one with reasons. Before a data protection audit we review code and architecture technically against GDPR Art. 25 and 32. You get improvements you can put in place quickly and a hardening plan. ## What does a code review cost? **A code review with us costs €1,200 to €4,500 and takes 1 to 3 days, depending on the size of the codebase. It includes a written report with prioritised findings.** - **€1,200** is the minimum for a code review, up to €4,500 depending on the size of the codebase. - **1 to 3** days is how long a code review takes for a mid-sized codebase. - **€190** an hour is what consulting costs, and it is the rate we bill tech due diligence at. *Guide prices 2026, net. Consulting costs €190 an hour.* | Format | Price | Duration | Result | | --- | --- | --- | --- | | Code review | €1,200-4,500 | 1-3 days | Written report, prioritised findings, concrete recommendations for action | | Tech due diligence | by effort, €190/h | 3-5 days | Report with a risk score and an estimated remediation cost | The code review is a package price. It is above the project day rate of €1,100 because the report is part of the service. The initial consultation costs nothing. If the decision still comes before the build, such as the choice of tech stack or the question of feasibility, an [architecture workshop from €1,500 or a feasibility analysis from €3,000](https://fragonstudios.com/en/services/consulting-architecture/) is the better fit. ## What does tech due diligence cost? **Three to five days, billed by effort at the consulting rate of €190 an hour. The result is a report with a risk score and an estimated remediation cost.** **We go through the repository and talk to the CTO in an architecture workshop.** Tech due diligence is the technical review of a software company before an acquisition or an investment. It is for investors who need an independent assessment of code, architecture and scaling risks. At the end there is a written report that rates the risks and estimates what a remediation would cost. ## What questions does a code review answer? **The questions you have before your decision, phrased so that you understand the answer without programming knowledge.** - can another team keep working with this code, and what is missing for that - where are the risks for security and data protection - which parts are outdated and need to be renewed soon - who holds the access to code, servers and services - is it worth building on, replacing step by step or rebuilding **We agree in the initial consultation which questions come first.** A review before a takeover sets different priorities than one before a data protection audit. The technical details are included for your team or the next provider. ## What is in the audit report? **Prioritised findings with reasons and concrete next steps, as a list your team or another provider can work with.** - the answer to your question in a few sentences, at the start - findings sorted by urgency - recommendations for action, with reasons - what we looked at and what we did not - for tech due diligence, also a risk score and the remediation cost On request we go through the report with you and your team. ## What does a code review not do? **It is not legal advice and no guarantee that the software is free of bugs. It shows where the risks are and how serious they are.** In one to three days we do not read every line of a large codebase. We review the parts your decision depends on and state in the report what we looked at. In the GDPR check we review code and architecture technically. Whether your processing is lawful is for your data protection officer or a lawyer specialising in data protection law to clarify. > **We assess the code, not the people who wrote it.** **Under time pressure, every team writes code that causes work later.** The report is meant to show what needs to be done now. ## How does a software audit work? **Three steps from the free initial consultation to the written report, plus implementation as an option.** 1. **Initial consultation** (free): Code review or tech due diligence? 2. **Analysis** (1 to 3 days, 3 to 5 for due diligence): Code, architecture, conversations, with your team on request. 3. **Written recommendation** (Report): Recommendations and next steps, gone through together on request. 4. **Optional: implementation** (separate quote): We support the implementation or develop it ourselves. **The assessment is independent of technology and vendor.** 1. Initial consultation, free and with no obligation. We get to know the situation and clarify whether a code review or tech due diligence fits. 2. Analysis. Depending on the assignment, a code review, an architecture analysis or conversations with the people involved, and interviews with your team on request. 3. Written recommendation. You get a report with concrete recommendations and next steps. On request we go through it with your team. 4. Optional: implementation. If you want, we support the implementation or take over the development ourselves. That is a separate quote. ## What do we need from you? **Read access to the code, a person who can answer questions, and the decision at stake.** - **Access to the code**: Read access is enough. If you cannot get the code because it sits with your provider, that is already the first finding. - **The documents that exist**: Documentation, the quote the software was built to, a description of the servers. - **Someone for questions**: Ideally someone who knows the code. On request we also talk to your team. - **Your question**: Take over, rebuild, invest or carry on as before? ## Is the audit independent of a later order? **Yes, explicitly. You pay for advice, not for a hidden sales pitch, and we also recommend solutions we do not build ourselves.** Danijel Balog, founder and lead engineer, does the review himself. **If your current provider has done good work, that goes into the report just the same.** A review that looks for flaws because the reviewer hopes for the follow-up order does not help you. We have no interest in a particular cloud or a particular framework. If you want to build with us after the audit, we are happy to. If not, the report is still complete and usable for any other team. The recommendations come from our own operations, because we develop and run software in production ourselves. ## Do you also work on site in Linz? **Yes. On request we hold the initial consultation and workshops in person in and around Linz; ongoing coordination is mostly remote.** **Fragon Studios e.U.**, Moosfelderstraße 45/11, 4030 Linz, Upper Austria Phone: +43 699 11066720 · Email: office@fragonstudios.com Meetings on site: Linz, Leonding, Traun, Ansfelden, Enns, Steyregg, Wels, Steyr, Freistadt, Gmunden and the surrounding area, otherwise remote. Google Maps: https://www.google.com/maps?cid=7601366018796259551 ## Which technologies does Fragon Studios review? **Web frontends, backends, mobile and infrastructure. We do not review Salesforce customisation or SAP parameterisation.** - Web frontend: React, Vue, Angular, Svelte - Backend: .NET, Node.js, Python, Go - Mobile: React Native, Flutter, native for iOS and Android - Cloud and infrastructure: Kubernetes, Docker, Hetzner, AWS, Azure, GCP ## Frequently asked questions ### How long does a code review take? **One to three days for a mid-sized codebase.** Tech due diligence typically takes three to five days. ### Do you need access to our code? **Yes, read access is enough.** Without the code, all we can do is guess. If the code is with your provider and you cannot get it, first clarify who owns it under the contract. ### Does our current provider have to know about it? **That is your decision.** For the review we need the code. Questions to the developer often make the result more precise, but they are not a condition. ### Do you also review software built by another provider? **Yes, that is exactly what an independent second opinion is for.** We apply the same standards to code written by others as to our own. ### What if the code is fine? **Then that goes in the report, with reasons.** That too is a result that makes the review worthwhile, for example before a takeover or an investment. ### Do we get a figure for what fixing it costs? **For tech due diligence, yes: the report estimates the remediation cost.** With a code review you get prioritised findings with recommendations for action. If you want a price from that, the implementation is a separate quote, from us or from someone else. ### What is the difference between a code review and a feasibility analysis? **The code review assesses existing code, the feasibility analysis a planned project.** The feasibility analysis comes with an effort estimate and a stack recommendation, from €3,000 in one to two weeks. ### Is the GDPR check legal advice? **No.** We review code and architecture technically against Art. 25 and 32 GDPR. Whether your processing is lawful is for your data protection officer or a lawyer specialising in data protection law to clarify. ### What does implementation cost after the audit? **Implementation is a separate quote, usually at a fixed price after an analysis phase.** We bill project work at the day rate of €1,100 and consulting at €190 an hour. ## Have your code reviewed independently? Briefly describe the situation to us. The initial consultation is free, and afterwards you know which format fits. [Request a code review](https://fragonstudios.com/en/contact/) ## Further reading - [Architecture workshop and feasibility analysis](https://fragonstudios.com/en/services/consulting-architecture/) - [MVP in 12 weeks](https://fragonstudios.com/en/services/mvp-entwicklung/) - [Hiring a software developer: what to look out for?](https://fragonstudios.com/en/ratgeber/softwareentwickler-beauftragen/) - [GDPR-compliant hosting in Austria](https://fragonstudios.com/en/ratgeber/dsgvo-hosting-oesterreich/) ## Sources - [General Data Protection Regulation (EU) 2016/679, Art. 25 and 32, on EUR-Lex](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016R0679)