English
Cronicle Hosting
Schedule and run jobs with a web UI, real-time logs, chaining, and multi-server support.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Tech
- Docker image
- soulteary/cronicle:latest
- Default port
- 3012
How Cronicle works
Cronicle organises executable jobs as scheduled events. An event can run at repeating times, on demand, or as part of a chain, while categories, plugins, parameters, timeouts, and resource limits shape how each task behaves. The web interface shows upcoming activity, completed runs, statistics, and logs for supported jobs.
A Cronicle installation can coordinate work across registered worker servers, but those workers must be installed, trusted, and connected separately. The catalogue package provides the hosted Cronicle service only. Tasks execute within the permissions and environment available to that service or to workers an administrator adds; the page does not imply control of the underlying hosting node.
Key Cronicle features
Live log viewing and execution history make scheduled work easier to inspect than isolated timer entries. Chaining can start one event after another completes, while retries, timeouts, concurrency controls, and notification settings help operators express operational expectations. Job code, plugins, credentials, and the effects of each task remain the user’s responsibility.
The catalogue persists Cronicle’s data directory and exposes the fixed upstream first-run credentials admin / admin. That password must be changed immediately after sign-in. Application email is disabled, so email-based completion or failure notifications cannot be treated as available; use in-application status and supported non-email integrations where appropriate.
Who uses Cronicle
Operations teams schedule maintenance scripts, reporting tasks, data imports, clean-up routines, and service checks. Developers trigger repeatable jobs without building a separate dashboard, while small teams use the execution history to understand when a scheduled process ran and whether it completed.
Cronicle is not a hosted worker fleet, secrets vault, monitoring service, or approval system. High-risk tasks require careful permissions, independent backups, change control, and testing outside critical production data before a schedule is enabled.
Self-hosting Cronicle: requirements and cost
Capacity depends on active schedules, concurrent executions, plugin processes, log volume, event history, dashboard users, and any connected workers. The catalogue records PostgreSQL and MariaDB as Not required and persists the Cronicle data directory, so schedules, settings, history, and logs should be treated as one recovery set.
On AvaHost, Cronicle uses Plan 1 at €2. The hosted Cronicle package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Only the Cronicle web service is included. Additional worker servers, job code, external credentials, notification providers, and target-system access must be supplied and administered by the customer. Change the fixed upstream administrator password immediately, and test each task with limited permissions before scheduling broader execution.
F.A.Q
Cronicle starts at €2 on Plan 1. A small schedule set with light concurrency and moderate logs fits the entry plan. Event frequency, overlapping executions, plugin workload, retained history, log volume, dashboard activity, and separately connected workers are the main reasons to review processing and storage later.
The package includes one Cronicle web service. Cronicle can coordinate separately registered workers, but AvaHost does not provide those extra servers, their credentials, or their job environments as part of this app plan. Add only trusted workers, limit their permissions, and test network reachability and task behaviour before assigning scheduled events.
The catalogue notes that Cronicle seeds the fixed first-run username and password `admin` / `admin`. Sign in and replace the password immediately. Store the new credential securely, restrict administrator access, and review existing users and API keys. Automated HTTPS protects the login connection but does not compensate for leaving the upstream default credential active.
AvaHost applies application updates automatically and includes scheduled backups while keeping the persistent Cronicle data directory attached. After a significant release, inspect schedules, plugins, categories, worker registrations, logs, and several low-risk test jobs. Email notifications are unavailable, so confirm completion through the web interface or another supported non-email path.