{ }hardened
krons24-backend
FastAPI · Python 3.11 control-plane API, auth, scheduling & licensing.
registry.krons24.com/krons24-backend:latestregistry.krons24.com/krons24
krons24
Teknomee· Verified Publisher
Self-hosted, distributed cron job management for teams. Schedule, run and observe scheduled tasks across every server — from one hardened, container-native control plane.
// quick start — pull the stack
docker compose -f deployment/docker-compose.yml up -dImages3
Pulls12,480
Latestv3.0.0
Archamd64 · arm64
LicenseFree + Paid
About Krons24
Krons24 is a self-hosted platform that turns scattered, hard-to-track crontab entries into a single, observable control plane. Instead of SSH-ing into every server to edit cron files — with no logs, no alerts and no history — teams schedule, run and monitor every job from one web dashboard.
Each scheduled job runs on your own infrastructure over SSH, streams its logs back in real time, and raises an alert the moment it fails. It ships as a small set of container images you run with Docker Compose — your data never leaves your servers.
⌗
One control plane
Every job, every server, one dashboard. Cron expressions with a visual builder.
↺
Real-time logs
Live log streaming over WebSockets, full run history and audit trail.
⚑
Alerting
Email, Slack, Discord and webhooks fire the instant a job fails or runs slow.
⛁
Self-hosted
Runs on your hardware. No data leaves your network. Air-gap friendly.
Images in this registry
◵hardened
krons24-frontend
Next.js 15 · React 19 dashboard UI, standalone output, white-label ready.
registry.krons24.com/krons24-frontend:latest⌳hardened
krons24-nginx
Nginx 1.25 edge · TLS termination, rate-limiting, security headers, routing.
registry.krons24.com/krons24-nginx:latestThe stack also uses upstream mariadb:11 and redis:7-alpine, plus two Celery roles (worker & beat) that reuse the backend image.
How to use these images
1
Authenticate to the registry
docker login registry.krons24.com2
Pull an image
docker pull registry.krons24.com/krons24-backend:latest3
Run the full stack with Compose
# 1 · configure secrets
cp deployment/.env.example deployment/.env
nano deployment/.env
# 2 · launch all services
docker compose -f deployment/docker-compose.yml up -d
# 3 · open the dashboard
open http://localhostDefault sign-in on first boot: admin@krons24.com — the one-time password is printed in the backend logs (docker logs krons24-backend).
Why use Krons24 images
⛨Minimal attack surface
Multi-stage builds ship only the runtime — no compilers, no build tooling, no shells you don't need. Slim base images, pinned by digest.
⚇Runs as non-root
Every container drops to an unprivileged user (UID 1001). No process runs as root by default — straight out of the OWASP playbook.
♥Built-in health checks
Each image declares a HEALTHCHECK so orchestrators know the real state, not just “process alive”.
⇄Hardened edge
The nginx image enforces TLS, HSTS, CSP and per-route rate limits, and isolates internal services behind one gateway.
⌁Reproducible & signed
Immutable digests and versioned tags mean the image you test is byte-for-byte the image you run in production.
⛁Your data, your servers
Self-hosted by design. Secrets stay in your .env; job output never leaves your network.
License & plans
The images are free to pull and run. Capabilities are unlocked by a license key set in your .env — leave it empty to run the Free tier forever.
Free
$0/mo
- 5 workspaces
- 20 jobs / workspace
- 5 servers / workspace
- 100 executions / day
- Community support
KRONS24_LICENSE_KEY=(empty)
Starter
$29/mo
- 10 workspaces
- 100 jobs / workspace
- API access
- Slack & webhook alerts
- Email support · 24h
Popular
Pro
$99/mo
- 50 workspaces
- 500 jobs / workspace
- Webhook triggers
- Job templates
- Priority support · 4h
Enterprise
Custom
- Unlimited everything
- SSO · SAML / OIDC / LDAP
- Kubernetes executor
- Custom SLA
- Dedicated support
Licenses are JWT-based and verified offline by the backend, with a 7-day grace period on expiry.