AI-generated video
CodeGuard Cloud
Checking tools through one interface: Lighthouse, security headers, known vulnerabilities in your packages. Your source code stays on your machine.
In development. We test every feature daily for at least a week before it goes live.
Your code stays with you
The cloud never sees your source code. It checks what is public anyway, and otherwise works only with what you choose to send.
- Addresses, not files
- Performance, security headers and certificate are measured on your live website, exactly as any visitor sees it. All the cloud needs is the address.
- A package list, not your project
- For the vulnerability check, a script on your machine reads the lockfiles and sends only package names and versions. No file, not a single line of code.
- No path for source code
- Features that transfer source code are not part of the concept. What the cloud never receives cannot get lost there either.
Tools through one interface
Your AI assistant calls the tools directly (through the MCP protocol). For scripts and pipelines there is a web interface (REST), first for Lighthouse and the package check. What comes back is data a program can work with. One practical example per tool:
Lighthouse for lists of addresses
in progress
After an update, your home page is noticeably slower on mobile. The measurement shows by how many points each Lighthouse score dropped compared with the last measurement.
DNS, encryption and security headers
in progress
After a server move, the header that forces browsers onto HTTPS is missing, and the certificate expires in twelve days. The check reports both before a visitor sees a warning.
Known vulnerabilities in your packages
in progress
A security flaw becomes known for a package version in your composer.lock. The check names the package, the version and the identifier of the flaw; the file itself stays with you.
Lifecycle of frameworks such as Laravel
in progress
Your package list shows Laravel 9. The check reports that this version no longer receives security updates.
Crawler and SEO
in progress
After a relaunch, internal links and sitemap entries point to pages that no longer exist, and several pages lack a meta description. The crawler lists the affected pages it has checked.
HTML and structured data
in progress
Your product data lacks required fields for ratings, without which Google cannot show stars. The check names the missing or faulty field.
Accessibility in a real browser
planned
Your contact form has fields without labels that a screen reader cannot read out. The check names every spot.
Detection of the software you use
planned
Your website ships an old jQuery version with known flaws. The check detects it from the public page.
Continuous monitoring
in progress
The cloud checks your website again at regular intervals. If performance drops noticeably after an update or a new flaw becomes known in your packages, you get a message.
Interface for your AI assistant and pipeline
in progress
Your pipeline starts a Lighthouse measurement after every deploy, fetches the result and stops if the performance score is not above 80.
Overview in the browser
in progress
Your project lead sees without a terminal which findings are open, which are new since the last run and which count as fixed.
Right away or as a job: you decide how you wait
One address takes about a minute, because the cloud measures every page three times. Twenty addresses on two devices take considerably longer. So every request has two paths, and both lead to the same result.
- Synchronous: the result in the same response
- Your tool waits for the result: up to five minutes through the web interface, up to one minute for your AI assistant. If the result is not there by then, you get a job number instead of an error: the measurement keeps running, nothing is lost. Intended for the moment you are in your editor or just before a commit.
- Asynchronous: a job number at once
- The cloud accepts the job and answers immediately with a number. Your pipeline keeps working and checks the status later: waiting, running, done or failed. Intended for long lists of addresses, nightly runs and CI.
- Partial results as soon as they are done
- When you check, you see every finished measurement while the others are still running. Every value comes with a comparison to the last run. The same request within ten minutes is answered from the cache, without measuring again.
An example: our own website
Measured at www.provimedia.de on October 7, 2026, mobile view, with Lighthouse on our own machine, not yet through the cloud. The example shows why a score alone is not enough: only the cause tells you what to do.
- Mobile performance
- 55 and 56 out of 100
1,197 KB uncompressed, as delivered
328 KB compressed
- Cause
- The web server compressed only the HTML. JavaScript and CSS went over the wire uncompressed.
- Fix
- One web server setting. These three files are then transferred about 73% smaller. The fix is in progress; we will add the measurement taken after it here.
What you save
- Machine time
- One Lighthouse measurement kept our development machine busy for about 20 to 25 seconds. Twenty addresses on mobile and desktop, each measured three times, are 120 measurements: 40 to 50 minutes in which the machine does nothing else. With the cloud they run on our machines, and yours stays available for your work.
- Numbers you can trust
- Lighthouse fluctuates: the same page scored 53 and 63 for us on the same day. The cloud measures every page three times and takes the middle of the three values for performance. A single outlier does not decide the result.
- Findings, not just a score
- Every measurement comes with up to ten findings from performance, accessibility, best practices and SEO, ordered by their weight in Lighthouse. You see which values pull the score down.
- Nothing to run yourself
- No test environment to set up, no browser to maintain on the build server, no vulnerability database to keep current. You call a tool and get a result.
How far we are
The status comes straight from our development and updates itself. We count the core build, weighted by effort.
4% built
3 of 66 weight points, core build P0 Status as of 7 October 2026, 15:59