Timezone-Aware Scheduling
Build schedules with cron expressions and timezone support, preview timing before you save, pause and resume safely, and choose how missed runs are handled after downtime.
About
Scheduling and run visibility. Built for teams who operate, not just deploy.
Outcron is a hosted scheduling platform for DevOps teams, SaaS operators, and platform engineers who need to schedule HTTP calls, health checks, containers, scripts, database queries, cloud commands, and more — with execution history, misfire recovery, and team-scoped access controls.
More than a hosted crontab: Outcron gives teams searchable execution history, timezone-aware scheduling with misfire recovery policies, private registry support, role-based team isolation, and API and CLI automation — in a service our team operates for you.
Searchable Run History
Every execution is logged with status, timing, and trigger context. Filter by job, schedule, or time range, and clean up completed history while live work stays protected.
Outside-In Health Checks
Check services from outside your network on a schedule and catch the failures your customers would see, with expected-status validation and clear run history.
Built-In Job Type Coverage
HTTP calls, health checks, containers, scripts, database queries, cloud functions, CLI commands, IaC drift detection, ETL pipelines, and git workflows — all with the same scheduling, retry, and visibility controls.
Team Isolation And Access Control
Give each team its own organization with role-based access, admin controls, and org-scoped API keys so automation stays isolated without shared operational access.
API-First With Web And CLI
Manage everything through the REST API, the outctl CLI, or the web UI. Scoped API keys fit pipelines, scripts, and internal tooling.
outctl CLI managing schedules and executions from the terminal
Operational Excellence
Schedules support cron expressions with timezone awareness, preview before they are saved, pause and resume cleanly, and bound backlog with max pending and pending timeout controls.
The outctl CLI gives teams full administrative control from the command line — managing jobs, schedules, executions, alerts, reports, support tickets, billing, users, roles, and API keys without opening a browser. It ships as a single static binary for Linux, macOS, Windows, FreeBSD, NetBSD, and OpenBSD on both AMD64 and ARM64, so it works wherever your team already operates.
Alerting That Matches Real Operations
Outcron now gives teams a fuller alerting model built for real on-call work, not just one-off failure emails. Teams can combine threshold-based alert rules, lifecycle-driven alert subscriptions, maintenance silences, acknowledgements, and multi-step escalation policies in the same workflow.
Alert rules
Watch for repeated failures, repeated timeouts, rising error rates, or jobs that are running longer than expected. Rules support cooldowns, sliding evaluation windows, and minimum sample counts so teams can catch real regressions without turning every transient blip into noise.
Alert subscriptions
Subscribe directly to execution, healthcheck, job, and schedule lifecycle events when you want immediate visibility instead of threshold evaluation. Subscriptions can be scoped by job or schedule, support per-minute rate limits, and work well for teams that want to route every failure, every misfire, or every critical change.
Silences and acknowledgement
Planned maintenance does not need to become alert fatigue. Silences can target a rule, a subscription, a job, a schedule, or a specific lifecycle event for a bounded window, and suppressed matches are still recorded for auditability. Once an alert fires, responders can acknowledge it with notes so the team can see what is already being handled.
Escalation policies
Escalation policies let teams define timed follow-up steps for unacknowledged alerts. Matching subscriptions notify immediately, then additional channels can fan out minutes later if nobody has picked the event up. Acknowledging the event stops further escalation, which keeps serious incidents visible without repeatedly paging people for issues that are already in progress.
All of this flows through the same durable delivery pipeline, with built-in support for email, webhooks, Slack, Microsoft Teams, Discord, PagerDuty, and Opsgenie. The result is one alerting surface that fits both routine operational hygiene and higher-stakes incident response.
Fits Existing Environments
Outcron is built to support teams running across cloud, virtualized, and container-based environments without forcing them into a single deployment model.
The hosted service coordinates schedules and execution capacity so teams can add coverage or capacity as their workload grows without wiring together separate schedulers, monitors, and job runners.
That keeps the day-to-day experience simpler: one place to schedule work, review runs, manage access, and troubleshoot issues.
Outcron is developed by Exclaim Systems LLC, based in Frisco, Texas in the United States.
Exclaim Systems has been working on the web since 1993, building long-lived web systems with an emphasis on durable operations, practical engineering, and clear ownership.
Exclaim Systems LLC
Visit exclaim.systems