Blog/Private AI for QA and software testing
Private AI

Private AI for QA and software testing

By Samuel Seidel · September 9, 2026 · 8 min read

Running a code model yourself lets QA write test cases, review diffs and triage bugs without sending source code, API surface and test data to an AI vendor. For most codebases a cloud tool is a minor risk. For code under an NDA, anything pre-acquisition, or anything a security team would flag in a vendor's training pipeline, self-hosting removes the question instead of managing it.

What QA teams use LLMs for

Three tasks come up repeatedly. In test case generation, the model reads a ticket or acceptance criteria and drafts edge cases a human might not think of first: empty inputs, boundary values, concurrent access. In code review, it reads a diff and flags an unhandled error path, a missing null check, or a change inconsistent with the rest of the file. In bug triage, it reads a report plus a stack trace and suggests a likely root cause or duplicate ticket, which speeds up the first ten minutes before an engineer opens the code.

None of these need a frontier model. They're pattern-matching and summarization tasks over text you already have, which a mid-size open model handles well on a single GPU.

Why the codebase question matters

A cloud coding assistant's terms usually say your prompts and code snippets aren't used for training on paid tiers, and most vendors mean it. But "usually" and "most" are not the same as "never," and the actual guarantee depends on which product tier a given engineer is signed into that week, whether they're using a personal account instead of the company's enterprise agreement, and whether a browser extension is quietly routing text through a different endpoint than the one procurement approved. Self-hosting sidesteps most of that: the code goes to your own model on a dedicated machine, so there's no AI vendor policy to audit and no tier mismatch.

On a rented Spark that machine is GPUwerk's hardware, operated under its published DPA. For NDA-covered code, check that the NDA allows a hosting provider before the code goes on it.

This matters more for some codebases than others. A team building an internal admin tool has less at stake than one working on a security product, a trading system, or code under an active NDA with a customer. Match the effort to what's being protected rather than treating every repo the same way.

What quality looks like

The tradeoff: a self-hosted 30-70B class model is noticeably behind GPT-5 or Claude on code review depth. It catches the obvious issues (an unclosed resource, a missing await, an off-by-one in a loop bound) but misses subtler bugs a frontier model would flag, like a race condition that only shows up under specific ordering, or a security issue that requires reasoning across multiple files at once. If your team is used to a frontier model's review quality, a self-hosted model will feel like a downgrade on the hardest cases.

Where it holds up well is volume work: generating a first draft of test cases from a spec, summarizing a long bug report into a triage-ready one-liner, or doing a first pass over a diff to catch the mechanical issues before a human reviewer looks at the substantive ones. Treat it as a first-pass filter, not a replacement for a senior engineer's review on anything that matters.

Setup effort

Running an open coding model like Qwen2.5-Coder or a similar instruct model isn't a one-click install. Someone on the team needs to stand up an inference server, wire it into whatever IDE plugin or CI hook the team wants to use, and tune the prompt templates so the model's output format matches what your test framework or ticketing system expects. Budget a few days of setup for a small team, more if you want it integrated into CI so every PR gets an automatic first-pass review comment. It's not free, and a team expecting Copilot-level polish out of the box will be disappointed by the raw experience before the integration work is done.

Once it's running, maintenance is light: updating the model occasionally as better open weights ship, and revisiting the prompt templates when the team's conventions change.

A concrete workflow

A pattern that works well: wire the model into a pre-PR hook that reads the diff and posts a first-pass review comment before a human looks at it. It catches the mechanical issues (unhandled errors, obvious style deviations, missing tests for new branches), so the human reviewer's time goes to logic and design. Separately, point the model at a ticket queue once a day to draft test cases for anything newly marked ready-for-QA, which a QA engineer then edits rather than writes from scratch. Neither task requires the model to be right every time; it needs to be right often enough to save more time than it costs to review its output.

A 30-70B coding model fits on one Spark

A 30-70B class coding model fits in a single Spark's 128 GB of unified memory with room for a long context window, which matters for code review: a meaningful diff plus surrounding file context can run to several thousand tokens. It costs $0.79/hour in Europe, North America or East Asia, billed per minute, and reserving a Spark by the month cuts that by up to 35% if the team runs it continuously.

Related pages

First top-up: pay $20, get $30 in credit

Review code and generate tests without sending your repo to an AI vendor.

A dedicated DGX Spark in EU-Central, $0.79/hour, for code review, test generation, and bug triage on a dedicated machine assigned only to you.

Your data stays on a machine assigned only to you. GPUwerk processes it under its published DPA.

Create account Private LLM hosting