# How automations work

> Automations run devlo on your repositories when a GitHub event happens or on a daily or weekly schedule, following instructions you write.

An automation runs devlo on your repositories when something happens on GitHub, or every day or week, following instructions you write. Owners and admins manage them from **Automations** in the sidebar.

## Built-in automations

devlo comes with two: the **Code Reviewer**, which [reviews new pull requests](/code-review/), and the **PR Assistant**, which [answers `@devloai` on pull requests](/coding/pull-requests/). Both are on by default. You can edit them but not delete them. To turn one off, see [Turn an automation on or off](/automations/create/#turn-an-automation-on-or-off).

devlo also adds a **Weekly Security Scanner**, turned off, when you connect GitHub. You can turn it on, edit it, or delete it.

![The Automations list, with the built-in automations and the inactive Weekly Security Scanner.](/_astro/automations-list.DF3CS47D_ZlVhIp.webp)

## Runs and credits

Each run covers one repository. An event starts one run per matching automation; a schedule starts one run per repository in scope. Results appear on GitHub, or by email with **Send Email**.

Each run uses [credits](/account/plans/). **Send Email** needs a paid plan, and running commands such as tests needs Startup or higher; see [Triggers and capabilities](/automations/triggers/#capabilities).

## Next steps

[Create and manage automations](/automations/create/)

[Example automations](/automations/examples/)