chronoverse
GitHub repository
About

What Chronoverse is.

It schedules heartbeat checks and container workloads on infrastructure you control. The scheduler, the dashboard, the documentation and this site are built and released from one repository.

Maintainer
Hitesh Rana

  • Docker containers run on runtime nodes that register with the platform. Kubernetes is the supported production orchestrator.

  • PostgreSQL holds transactional state, idempotency records, outbox rows and leases. ClickHouse retains logs, and Meilisearch indexes them.

  • Traces, metrics and logs export over OpenTelemetry to the bundled Grafana OTEL LGTM stack.

  • MIT. You run it on your own machines, and the data stays with you.

What it runs

Two workflow kinds. A HEARTBEAT workflow is a lightweight check that produces no logs. A CONTAINER workflow runs a Docker workload and can keep its stdout and stderr. Either can run on an interval or on demand, through the same replay-safe lifecycle.

How is it documented?

The guides, the API reference and the OpenAPI contract are authored as MDX in the same repository. Navigation, link validation, search and this site all come out of one build.

Report a defect as an issue on the repository, or email the maintainer.