Skip to content
Sun Software logo with the tagline Engineering Beyond Code
Software Architecture & Code Audits

A code audit that shows what you have before you invest in the next build.

Our code audit services turn an unfamiliar or troubled codebase into an evidence-backed technical picture and a practical plan for what to do next.

service-briefFixed scope
  • CategorySoftware & SaaS
  • EngagementFixed scope
  • First stepScoping call
  • Reply withinOne business day
01

50+

Countries our clients come from

Mostly the US, UK, Germany, Canada and Australia.

02

1,685

Reviews on Fiverr

Public, and open for anyone to read.

03

16

People on the team

Working together since 2020.

04

4.9

Out of 5 on Fiverr

Average across all reviews.

You are about to spend on this code. Do you know what is in it?

Most software carries problems its owners have never seen. Published audits and studies show how common they are, and what they cost.

  • of 947 commercial codebases audited contained at least one vulnerability

    87%

    What we do

    We review sign-in, permissions, stored secrets and outdated packages, and each finding says where we saw it.

  • of those codebases contained components four or more years out of date

    92%

    What we do

    We list the outside packages your code depends on and mark the ones that are out of date.

  • is the least that poor software quality was estimated to cost in the US

    $2.41tn

    What we do

    We inspect how your code is tested and released, then name the causes behind the faults you keep paying to fix.

  • of the audited codebases contained critical-risk vulnerabilities

    44%

    What we do

    We rank every finding by severity, serious ones first, and keep confirmed issues apart from suspicions.

What you need to know before you spend.

Five situations that bring teams to us, and what the audit does in each one.

  1. Problem 01 · Inherited code

    We took over this code, and nobody can tell us what state it is in.

    What we do

    We read the code and map how it is built. You get a plain picture of what is solid, what is fragile and what nobody has touched in years.

    • Architecture mapped
    • Data flows traced
    • Outside packages listed
    • Missing documentation noted
  2. Problem 02 · Security questions

    An investor or a large customer asked how the app is secured, and we could not answer.

    What we do

    We review sign-in, permissions, stored secrets and outdated packages. Each finding says where we saw it and how serious it is.

    • Sign-in and permissions reviewed
    • Keys and passwords in the code found
    • Outdated packages listed
    • Confirmed issues kept apart from suspicions
  3. Problem 03 · Broken releases

    Every release breaks something else, and nobody knows why.

    What we do

    We inspect how the code is tested and released. Then we name the causes, so you stop paying to fix the same symptoms.

    • Test coverage checked
    • Release steps inspected
    • Fragile areas marked
    • Causes separated from symptoms
  4. Problem 04 · Repair or rebuild

    One developer says rebuild it, another says patch it, and we cannot judge who is right.

    What we do

    We set out three options: repair, modernize or rebuild. Each one comes with its effort and its risk, based on what the code shows.

    • Three options compared
    • Effort and risk for each
    • What can be kept
    • Reasons you can check
  5. Problem 05 · What to fix first

    We have a long list of problems and no idea where to start.

    What we do

    We rank every finding by severity and turn the list into an ordered backlog. Then we walk your decision makers through it on a call.

    • Findings ranked by severity
    • An ordered backlog
    • A plain-language summary
    • A readout call

Known problems. Nobody checked.

Two public cases show what an unchecked system can cost. Neither is our client.

  • Data breach · July 2017

    A fix was ordered. Nobody checked it was done.

    What happened

    The US regulator said Equifax was warned in March 2017 about a critical flaw in one of its databases. A patch was ordered, but nobody followed up to confirm it. The flaw was found in July, after attackers had been inside for months. About 147 million people were affected.

    What we do about it

    We list every outdated package and check the code itself, so a fix that was ordered but never made shows up in the report.

    Source: US Federal Trade Commission
  • Banking · April 2018

    A new platform that failed on day one

    What happened

    TSB moved its customers to a new IT platform. The data moved across, but the platform failed at once and services were not back to normal until December. UK regulators fined the bank £48.65 million and said it had not managed the programme or its outside supplier properly.

    What we do about it

    We review the system and how it is released before you commit to a large change, and we tell you plainly what is not ready.

    Source: UK Financial Conduct Authority

Our own work

Live products we built. Open them and judge the work for yourself. Work for private clients is shared on a call, with the client's agreement.

See all case studies

A code audit report you can act on.

What you hold when the audit ends.

  • 01

    A plain-language summary

    What is solid, what is fragile, and what it means for you.

  • 02

    Findings ranked by severity

    The serious ones first, each with its evidence.

  • 03

    Proof for every finding

    Where we saw it and why it matters.

  • 04

    A map of the system

    How the parts fit and where your data goes.

  • 05

    Your three options

    Repair, modernize or rebuild, with effort and risk.

  • 06

    A readout call

    We walk your decision makers through it.

Why choose Sun Software as your software audit company?

An audit is only useful if you can trust it and act on it.

  • What usually happensOpinions are presented as facts, and you cannot tell which ones were checked.

    Evidence for every finding

    Each finding shows where we saw it. Confirmed problems are kept apart from suspicions.

  • What usually happensYou receive a scanner export with hundreds of lines and no judgement.

    An engineer reads the code

    Scanners run first. Then a person reviews the code and how it is built.

  • What usually happensThe advice is to rebuild everything, from the team that would be paid to rebuild it.

    Options, with reasons

    Repair, modernize and rebuild are set side by side, each with its effort and risk.

  • What usually happensA code review is sold as proof that the system is secure.

    Honest about the limits

    It is an engineering review. It is not a certification or a penetration test, and we say so.

In their words, not ours.

No public review names this service yet. These are recent reviews about how we work, word for word from Fiverr.

  • Great....very professional, delivered on time and exactly as I needed. Exceptional. I always find Sunsoft very easy to work with, always helpful and I'll continue using their services for the foreseeable future. No need to go anywhere else.
    Client in United KingdomOctober 2026 · Fiverr review
  • Excellent experience from start to finish. Communication was great, responses were always prompt, and the work was completed quickly. They captured the exact look and feel I wanted on the first try and delivered excellent value for the money. I would gladly work with them again and highly recommend their services.
    Client in GermanySeptember 2026 · Fiverr review
  • Choosing SunSoft was exactly the right decision. Their professionalism, extensive experience, and attention to detail have really impressed me so far. It was a complex project that exceeded my expectations! I look forward to continuing to work with SunSoft!
    Client in CzechiaAugust 2026 · Fiverr review

Questions before you book

What do code audit services include?

A written report and a call to walk you through it. You get a plain-language summary, findings ranked by severity with proof for each one, a map of the system, and your three options: repair, modernize or rebuild.

Is a software code audit a security certification?

No. It is a scoped engineering review. It is not a compliance certification or a penetration test.

Does this include penetration testing?

Only if it is scoped separately and carried out by qualified testers.

How fast can you start?

As soon as the NDA is signed and access is in place. Your proposal gives the start date.

What a code audit costs?

A code audit has a fixed price, set by the size of what is reviewed. Three things decide it. Size: One small repository, or a larger application in several parts. Depth: A snapshot of the main risks, or a full review of every area. Access: The code alone, or the code plus the running system and its settings.

What happens after I contact you?

We reply within one business day. Then the work runs in 4 steps: Agree the scope, Review, Report, Readout. Each step ends with something you can review.

  1. 1Request a Technical Audit
  2. 2We reply within one business day
  3. 3Scoping call
  4. 4Step one: Agree the scope

Know the state of your code before you spend on it.

Scope and level of access are agreed before the review starts.

  • The first conversation is free
  • NDA before you share anything
  • A reply within one business day