Starter
Single domain / a few protected URLsSmall events and reservation pages
MacroKeeper
Start with a limited protection scope and choose only the capabilities you need.

Small events and reservation pages
Services with repeated spikes
Teams without dedicated server staff
Package comparison
Start with a narrow set of critical URLs, then expand to Shield, Queue, or managed operation when repeated events and traffic peaks require it.
| Capability | Starter | Pro | Managed |
|---|---|---|---|
| Core protection | |||
| Protected URL selection | Included | Included | Included |
| Repeated URL/API request control | Included | Included | Included |
| POST request pattern protection | Included | Included | Included |
| Suspicious IP candidate review | Basic | Expanded | Expanded |
| Shield / Queue | |||
| Shield policy operation | - | Included | Included |
| Queue waiting room | - | Included | Included |
| Entry token issuing | - | Included | Included |
| Entry rate control | - | Included | Included |
| Operation / support | |||
| Operation log review | Basic | Included | Included |
| Policy tuning guide | - | Included | Included |
| Setup assistance | - | Optional | Included |
| Pre-event check | - | Optional | Included |
| Operational support | - | Optional | Included |
| Monitoring solution integration | - | - | Included |
| API integration support | - | - | Included |
Final scope is adjusted by protected URL count, traffic peaks, server structure, and event operation model.
Package basis
Protected URLs, event frequency, queue requirements, and setup support determine whether Starter, Pro, or Managed is the right starting point. Smaller services can begin with one or two critical URLs and expand after validation.