Skip to content
Back to the index

calendardb

PyPIInfrastructure

No liveness check has reached it yet; it is registered on GitHub and PyPI and has been in the index since 8 Oct 2026. How this is checked

calendardb is an MIT-licensed Python package that uses Google Calendar as a storage layer for logs and agent traces. It provides a calendar-based database view for developers experimenting with application observability.

Inferred · not functionally tested

Open SourceMITCLISelf-hostedAPI
Visit PyPI

Overview

5 features

Purpose: Storing and viewing application logs and agent traces in a calendar-based database.

Inferred · not functionally tested

Audience: developers building logging and agent observability systems

Inferred · not functionally tested

Functions: monitoring

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

calendardb sits in PulseGate's Databases (SQL, NoSQL, vector, graph) category. Inferred · not functionally tested: It focuses on storing and viewing application logs and agent traces in a calendar-based database. Inferred · not functionally tested: It is built as an open-source project for developers building logging and agent observability systems. Basis unknown · not verified: calendardb is open source under the MIT license. Basis unknown · not verified: It ships for the command line and API, and it can be self-hosted.

Behind calendardb is that-guy-wade, and it first shipped in 2026. Inferred · not functionally tested: Among its 5 catalogued features are log storage, agent trace storage, and calendar database view.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Log storage
  • Agent trace storage
  • Calendar database view
  • Day view
  • Google Calendar storage

Topics: Inferred · not functionally tested

Tags
calendar-databaseagent-tracesdeveloper-loggingobservability

JSON profile · Text profile · Access guide

Built with & integrations

Runs on
CLISelf-hostedAPI-only

Trust & compliance

License
MIT
Public signals
HTTPSOpen SourceGitHub

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed8 Oct · 19:05 UTC
    calendardb seen via PyPI Bulk Enumerator
    Source: PyPI Bulk Enumerator · Open

Frequently asked questions about calendardb

What is calendardb?
Inferred · not functionally tested: Calendardb focuses on storing and viewing application logs and agent traces in a calendar-based database. It is catalogued under Databases (SQL, NoSQL, vector, graph) on PulseGate.
Who is calendardb for?
Inferred · not functionally tested: calendardb is an open-source project built for developers building logging and agent observability systems.
Is calendardb free?
Basis unknown · not verified: Yes — calendardb is open source under the MIT license and free to use.
What platforms does calendardb run on?
Basis unknown · not verified: calendardb runs on the command line and API. It can also be self-hosted.
Is calendardb still active?
Unverified. calendardb has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What are alternatives to calendardb?
Similar projects tracked by PulseGate include OpenLDAP Docker, DBConvert, and DB Kit.OpenLDAP DockerDBConvertDB Kit
Who develops calendardb?
calendardb is developed by that-guy-wade.
How long has calendardb been around?
calendardb first shipped in 2026.

Also in Databases (SQL, NoSQL, vector, graph)

Same category — not a similarity match