Chronoverse is a self-hosted distributed scheduler and orchestrator for running heartbeat checks and containerized workloads on your own infrastructure.
It combines a public HTTP API and dashboard with gRPC domain services, Kafka-driven workers, durable PostgreSQL state, live and retained logs, notifications, analytics, and OpenTelemetry observability.
Duplicate events, worker restarts, partial publication, stale workflow builds, and abandoned container executions are expected operating conditions. Chronoverse uses idempotency keys, transactional outbox delivery, workflow generations, deterministic event identifiers, and durable job leases to recover safely.
What you can run
HEARTBEATworkflows for lightweight health checks without execution logs.CONTAINERworkflows for arbitrary Docker-backed commands with optional retained stdout and stderr.- Automatic interval-based jobs and immediate manual runs.
What the platform provides
System shape
Where to go next
Start with the quickstart, then create your first workflow. For implementation detail, read the architecture and replay-safety model.