Protection onlyattackers notice.

TurtleGuard stops bots, DDoS and malicious requests before they reach your site.

Connect via DNSNo infrastructure move
01Incoming flowbots · flood · exploit
02TurtleGuard Edgethreats lose their route
03Origin respondsclean request delivered
TurtleGuard networkNetwork status ↗
044 protection nodesin 2 countries

Our network takes the hit.

Nodes in Germany and Poland stop an attack before it reaches your server.

DEGermany2 protection nodes
DE-1edge node
DE-2edge node
PLPoland2 protection nodes
PL-1edge node
PL-2edge node
one networkAll nodes operational
Traffic is spread across active nodesAS219506
Connecting
5–15minutes

Your site stays where it is.Only the path to it changes.

Enter your server address and point the domain to TurtleGuard. We issue the certificate — no changes to your code or hosting.

  1. 01Add a domainAnd your current server address
  2. 02Point DNSVia NS, an A record or CNAME
  3. 03Protection is onThe certificate is issued automatically
What's included

From a huge flood to a single bad request.

TurtleGuard absorbs attack traffic, inspects requests to your site and handles HTTPS. Features depend on the plan.

01DDoS

Attacks don't clog your server

Large floods stop in the TurtleGuard network and never touch your server's uplink.

L3–L4 protectionburst limitingunder-attack mode

External floods stay outside; only traffic that passed inspection reaches the origin.

02WAF

Dangerous requests don't get through

Bots, scanners and exploit attempts are stopped before your site.

L7 protectionOWASP CRScustom rules

Rules can be tuned per site without touching its code or infrastructure.

03HTTPS

HTTPS just works

Certificates are issued and renewed automatically. On CDN plans static files are served from the TurtleGuard network.

TLS 1.3auto-renewalCDN · Premium+

Certificates are maintained automatically, and CDN can be enabled where fast static delivery matters.

Protection plans

The price depends on the project, not the size of the attack.

Every plan states its clean-traffic bandwidth, number of servers and WAF rules up front.

Billing period

Basic

A small site

Base price$10/ month
Clean traffic100 Mbit/s
Servers1 server
Rules3 WAF rules
  • 1 site
  • Unlimited subdomains
  • L3–L7 protection
  • 99% availability

Due for 1 month$10

Choose plan →

Standart

For most sites and shops

Base price$30/ month
Clean traffic250 Mbit/s
Servers3 servers
Rules10 WAF rules
  • 1 site
  • Unlimited subdomains
  • Custom WAF rules
  • 99.5% availability

Due for 1 month$30

Choose plan →

Premium

A project with CDN

Base price$80/ month
Clean traffic500 Mbit/s
Servers10 servers
Rules25 WAF rules + CDN
  • 1 site
  • Unlimited subdomains
  • CDN for static files
  • 99.9% availability

Due for 1 month$80

Choose plan →

Enterprise

Several large projects

Base price$200/ month
Clean trafficUnlimited
Servers50 servers
Rules100 WAF rules + CDN
  • 5 sites
  • Unlimited subdomains
  • CDN for static files
  • 99.95% availability

Due for 1 month$200

Choose plan →

Custom

Custom configuration

Custom projectfrom $400on request
Clean trafficPer project
ServersUnlimited
RulesPer project
  • Any number of sites
  • Dedicated capacity
  • Personal manager
  • Terms and SLA for your project

Priced after assessmentfrom $400

Discuss a project →

Prices in USD excluding VAT. The final amount is shown in the panel before ordering.

Before you connect

Common questions.

Briefly about migration, DNS, HTTPS and billing.

Open the docs ↗

No. Your server, hosting and DNS provider can stay the same. Use NS or an A record for the apex domain and CNAME for a subdomain.

Usually 5–15 minutes. The exact time depends on how quickly your provider's DNS updates.

Once the domain opens through TurtleGuard, the certificate is issued and renewed automatically.

No. You pay for your plan. Its limits apply to clean traffic and service features, not to attack volume.

A site must respond

Your site's pulse shouldn't depend on an attack.

Route traffic through TurtleGuard. Malicious traffic stays with us, and visitors keep opening your site.

Filtering activeSite responds
5–15 minutes is a typical setup timeDNS the route changes, not your projectNo migration code and hosting stay in place