# About cronservices

Most scheduled code is plumbing. Call an API, pick a few fields out of the response, send them somewhere else. Yet each piece of it usually becomes a function, which then needs a repo, a deploy target, a cron trigger, secrets, logs, and someone to notice when it stops running.

cronservices turns that plumbing into configuration. A job is a cron expression and a short pipeline of HTTP requests and JSON transforms. There's nothing to build or deploy. Every run is recorded, and you can read, change, or pause a job in seconds.

## Why now

More and more code is written by AI agents. Agents are good at describing what should happen and when. They're worse at owning the infrastructure that makes it happen: picking a host, wiring up a scheduler, rotating secrets, and keeping it all alive after the conversation ends.

So we built cronservices to be easy for an agent to use correctly. The API is small and documented in [OpenAPI](/openapi.json). The docs are published as plain Markdown and [llms.txt](/llms.txt). The [agent guide](/agents) says plainly when cronservices is the right tool and when it isn't. An agent can schedule work in one API call, and a person can see and change exactly what it did.

## What we believe

**Configuration beats code for glue.** If a task can be described as "fetch this, reshape it, send it there", it shouldn't need a deploy.

**Small and predictable.** One scheduler, standard 5-field cron in any time zone, a template language you can learn in five minutes, and limits that are written down. No surprises at 3 a.m.

**Readable by people and machines.** Every page on this site has a Markdown twin. If an agent can't read our docs, they aren't good enough.

**Honest about limits.** Requests time out after 10 seconds. Templates don't branch or loop with side effects. When you need more than that, write the code and let cronservices call it.

## Get started

[Create a free account](/login#signup), read the [docs](/docs), or point your coding agent at [https://cron.services/llms.txt](/llms.txt).

## Contact

Questions and account help: [support@cron.services](mailto:support@cron.services).