Security work from people who build software for a living
Propel Tech is a UK software consultancy. We build bespoke systems, and we also check whether the ones you already run are safe. That means an AI-augmented security assessment of your application, a review of the AWS or Azure environment it lives in, and penetration testing when you need to see what an outsider could get to.
We are a member of the Anthropic Cyber Verification Program, which gives us access to Claude models built for this kind of defensive work, and we point them at the whole codebase rather than a sample of it. Then a security consultant goes through every finding, throws out the noise and ranks what is left by what it would actually cost you.
And because we are developers first, we can fix it.
Let’s talk tech
We’re eager to support your bespoke software and AI project goals. Get a free consultation.
Get in touchHere to propel your
business forward
We work with manufacturers, logistics firms, property companies, utilities and public bodies, often on software a previous supplier built. Security sits alongside our wider software development services.
How an engagement works
Scope first, always. Assessments run against a copy of your system in an environment we control. Penetration tests run under written rules of engagement. Nothing happens to production without you signing it off.
01
Scope and threat model
We map the system with you: the data, the users, the integrations, the cloud footprint. Then we agree where the real risk is and which of the three services you actually need.
02
Assess and test
AI-augmented scanning for the software and the cloud account. Manual and tooled testing for the pen test. Either way, the whole system gets covered.
03
Consultant review
A security consultant goes through every finding. False positives go. Real issues get confirmed, and we look at how they could be chained together into something worse.
04
Report
A summary your board can read, a findings list ranked by risk, and a technical appendix for your developers with exactly where each issue lives and what fixing it involves.
05
Fix and retest
Our developers make the fixes, or work alongside yours. Then we scan or test again to make sure they held.
Which one do you need?
People ask us this a lot, so here is how the three services and our free AI audit compare.
| Software security assessment | Cloud environment assessment | Penetration testing | Free AI audit | |
|---|---|---|---|---|
| Looks at | Application code, dependencies, APIs, AI features | AWS or Azure configuration and identity | A live or staging system from the outside | A codebase at a high level |
| Access | Full source code and infrastructure as code | Read-only access to the cloud account | Network access and test credentials, with rules of engagement | Read-only view of a codebase |
| Finds | Code-level weaknesses and insecure patterns | Misconfiguration, exposure, weak identity controls | What an attacker can actually reach and exploit | Code quality, security hygiene, AI readiness headlines |
| Output | Three-part report and remediation plan | Ranked misconfiguration list with fixes | Severity-rated findings, evidence, retest letter | Short summary with next steps |
| Typical time | Two to four weeks | One to two weeks | One to two weeks plus retest | A few days |
| Fixes | Propel can remediate | Propel can remediate | Propel can remediate | Not included |
The usual order is software and cloud assessments first, fix what comes up, then a pen test to prove it. If an insurer or a contract is asking for a pen test by a date, start there and we will fit the rest around it.
What you get
Whichever service you pick, the same things hold.
The whole system, read
A manual review of a large codebase samples. It has to. AI reads all of it, every file, every config, and applies the same checks throughout.
Someone who decides what matters
A consultant confirms each finding and ranks it by what it could cost you, so your remediation budget goes on the things that would hurt.
Fixes from the same people
We can do the remediation ourselves. You do not have to take a findings report to a second firm and start the explanation again.
Something to show people
Reports and retest letters written so you can send them to the enterprise customer, the insurer or the auditor who asked.