Windows 10/11
x64 only, no account to run
SmartCode Relay 2.9.22 is a Windows agent that reads the logs you export, drafts rate limits and a runbook for servers you run, and shows file changes as diffs you can review.
logs/3 filesyour log tool > summary.csvexit 0/checkout summary.csv4 matchescopy/server-settings.txtreadcopy/server-settings.txt+6 -1your test commandexit 0x64 only, no account to run
released 28 Oct 2026
portable .exe is about 25 MB
interface languages
after the fact, outside traffic
or the built-in model
DDoS protection for a site you run is mostly built outside your own server: capacity at your hosting provider, a CDN or a scrubbing service, plus rate limits, caching and a written runbook on your side. SmartCode Relay 2.9.22 helps you plan, configure and document that side. It reads logs afterwards. It never sits in your traffic path.
You export last night's access log from your server and put it in the project folder. SmartCode Relay lists the folder with list_dir, then Shell runs your own log-summary script, which counts requests per address and per path and saves summary.csv. Next, grep searches that summary for the path you suspect, such as /checkout. A legitimate spike follows a launch or a mention and comes from many networks with varied pages, while a layer 7 flood often hits one or two paths with identical requests. Logs give hints, not proof. In Ask first mode the agent pauses before the command that writes the file, so you read it first.
list_dir logs/ → 3 files
Shell your log tool > summary.csv → exit 0
grep /checkout summary.csv → 4 matchesA rate limit caps how many requests one client may send to one path. Start from a copy of your server settings, never the live file. read_file opens the copy, edit_file adds the draft rule and shows a diff, and Shell runs your own configuration test command and reports the real exit code. The change touches 1 file. In Ask first mode the diff appears before you accept, so you can reject the change. Reject what looks wrong. Apply it to the live server yourself, once the test passes and you have a rollback line.
read_file copy/server-settings.txt → read
edit_file copy/server-settings.txt → +6 -1
Shell your test command → exit 0A runbook is a plain-text page that says who to call and what to switch on at your provider. Ask the agent for a text file, and write_file saves ddos-runbook.txt with a trigger line, 6 numbered steps, a rollback line and a review line. http_get can read one documentation page of your hosting provider, so the setting names come from the source. It contains no attack commands. Switch to Plan only first to read the outline, because that mode runs nothing, then let Ask first pause before the file is saved.
Timeouts and connection limits belong in the review too. Copy your web server settings into the folder; read_file opens the copy while grep searches it for lines about the 2 settings that matter here, timeouts and connection limits. Read only that output. On bare metal servers, meaning machines you rent or own outright on one network link, DDoS mitigation mostly happens at your provider, because a full network link cannot be fixed by anything running on the machine. The agent lists what to ask your provider for. In Ask first mode nothing changes until you accept the diff, and you test every edit on the copy first.
Chat answers stay text. SmartCode Relay 2.9.22 runs the tools itself and shows each action as a card with its real result, so you can check what happened.
| Typical chat assistant | SmartCode Relay | |
|---|---|---|
| Files | You copy text from the reply into your files | Reads, searches and edits files in the project folder, with a diff |
| Commands | Describes a command and leaves you to run it | Shell runs your command and reports the real exit code |
| Approval | No pause points, because the reply is only text | Auto-run, Ask first or Plan only; you choose how much runs |
| Logs | Sees your logs only when you paste them | Reads exported logs after the fact; it is not in the traffic path |
This is for the owner of a small shop, blog or API who runs the server and can export a log. You need facts first. A search for "protect server from ddos" usually ends at a provider setting, a rate limit and a runbook, and those are the three things the app helps you write down.
Hobby hosts count too. If a DDoS attack hits the game server you run for friends, the same provider call, the same rate limit and the same runbook apply, and the agent still only reads logs afterwards.
Any server you run fits. If it can export a log, the method is the same: summarise the log by address and by path, read the numbers yourself, and keep the 6 steps of the example runbook in a file you can find in a hurry.
DDoS protection is a set of layers, not one switch: capacity at your hosting provider or a CDN, a private origin address, rate limits, caching, sensible timeouts and a written runbook. Layers overlap on purpose. No single layer is complete, and each one needs testing.
Yes, smartcodegroup.com is the official SmartCode Relay website. This is the original build. Download the installer here, compare its SHA-256 checksum with the published manifest, and run it only when the two match. If something looks wrong, press Send feedback inside the app.
No. SmartCode Relay is not in your traffic path, so nothing it does touches live traffic. It reads logs you export after the fact, drafts rules and a runbook, and you apply them at your provider or on your server.
The short answer is layers: ask your hosting provider or a CDN to filter traffic before it reaches you, keep the origin address private, rate-limit per client and per path, cache static pages and write a runbook. Then test each rule.
Yes, but only on your own staging copy, or on the live site with your hosting provider's written permission, because providers can treat a load test as an attack. Get that permission first. The agent can help you write the plan and read the results afterwards.
The answer depends on the model you pick. With a cloud model, prompts, including any log text the agent reads, go to that provider; with a local model nothing leaves your PC. Access logs hold visitor IP addresses. Check your logs first.
A cloud AI provider through a standard API endpoint, a model running locally on your PC, or the built-in model. The Test button checks an endpoint and shows the response time and the context window. Press Test first.
No account is needed. Download version 2.9.22, a setup program of about 34 MB, compare its checksum with the published manifest, and point it at one exported log from your own server.
Download SmartCode Relay for Windows ↗Every page is available in 20 languages.
What SmartCode Relay does for server owners ↗ Connect a cloud, local or built-in model ↗ Review a log and draft a rate limit ↗ Download and verify the Windows installer ↗ Answers about scope, privacy and models ↗ How this site and the app handle data ↗