Scheduled pentests
Re-run a finished pentest automatically — once, daily, weekly or monthly — in your own timezone, with agents auto-filled for every phase.
What scheduling does
Security isn’t a one-off. Once a pentest has completed, you can schedule it to run again on a recurring basis, so the same scope is re-assessed automatically. The platform stores the schedule, the streaming backend picks each run up when it’s due, executes every phase and records the outcome — no manual launch required.
Scheduling is available from Pro upwards; Casual users can’t schedule. Limits scale with your tier (see Teams & tiers).
Schedule a pentest
-
Open a completed pentest at aleex-rank.ai and choose Schedule.
-
Pick a schedule type — once, daily, weekly or monthly — and a time of day (in your local timezone).
-
For weekly, choose a day of the week (Monday–Sunday). For monthly, choose a day of the month (1–31). For daily, no day is needed. For once, a day is optional — leave it blank to run today.
-
Save. The pentest is now scheduled, and you’ll see its next run shown in your local time.
The four schedule types
- Once — runs a single time, then deactivates itself. With no day set it runs today; if the chosen time has already passed today, pick a day so it runs in the future.
- Daily — runs every day at the chosen time.
- Weekly — runs every week on the chosen weekday.
- Monthly — runs every month on the chosen day. If the day exceeds the month’s length (e.g. the 31st in February), it falls back to the last day of that month.
Timezones
You schedule in your timezone, but the platform stores the next run in UTC and converts it back for display. Your timezone is resolved from your explicit preference if you’ve set one, otherwise from your country’s default, falling back to UTC. So “every Friday at 14:30” means 14:30 where you are — daylight-saving shifts and all — and you never have to do the maths.
How a scheduled run executes
When a run comes due, the streaming backend takes over:
- It picks up the pentest within a window around the scheduled time (a few minutes before, and a couple of hours after as a safety margin).
- It checks that every phase has agents. If a phase is missing agents — for instance because the original pentest stopped early — it auto-fills the defaults so the run is complete, keeping the 3-to-4-agents-per-phase rule.
- It runs the phases, updating an execution status you can watch:
idle→running→completed(orfailedon error). - When the run finishes, it computes the next run according to the schedule type — or deactivates the schedule if it was a one-off.
Manage and cancel
From your scheduled list (sorted by next run) you can:
- Reschedule — change the type, time or day at any time.
- Cancel — remove the schedule. The pentest reverts to its completed state and stops running automatically.
The list includes both your own scheduled pentests and those of teams you belong to.