BonHand VS cppq

• Client records
  One page per client: sessions, payments, notes and a running balance
• Scheduling
  One-off, recurring and group sessions; in person, online or by phone; attendance and payment per attendee
• Double-booking check
  Flags a clash and will not save it
• Payment reminders
  Lists each unpaid session and the total; you send it
• Payment link and QR
  Your own payment link and QR on each client's page (Starter and Growth). BonHand never handles money
• AI update drafts
  Drafted from your session notes; you edit and send. Free 15 a month, Starter 100, Growth unlimited
• Client portal
  Optional private page per client, no app or account needed, revocable
• Calendar feed
  One-way subscription link for Google, Apple and Outlook
• Income
  Totals by month and year; statement PDF on Starter and Growth
• File sharing
  With one client or one session on Starter; with whole groups on Growth
• Public profile page
  Free on every plan; rates and full details on Starter and Growth
• Languages
  English and Traditional Chinese (繁體中文)
• Currencies
  Your fees in 11 currencies, including GBP, HKD, USD and EUR

• Lightweight C++ implementation
  cppq is written in modern C++ and designed to be a minimal, efficient task queue library, making it a good fit for performance-sensitive applications where the overhead of scripting language runtimes is undesirable.
• Redis-backed reliability
  Built on top of Redis as the message broker, cppq benefits from Redis's persistence, atomic operations, and wide adoption, giving the queue system durability and the ability to survive process restarts.
• Inspired by proven design (asynq)
  The library's architecture mirrors the popular Go asynq task queue, so it inherits a well-thought-out API design for task enqueueing, retries, and worker processing patterns that have already been validated in production systems.
• Native integration for C++ projects
  For teams already working in a C++ codebase, cppq allows adding background job processing without needing to introduce a separate service written in another language (like Go or Python), simplifying the technology stack.
• Open source and inspectable
  Being open source on GitHub, developers can review the source code, modify it for custom needs, and contribute improvements, which offers transparency not available with closed-source queueing solutions.

Possible disadvantages

• Limited maturity and battle-testing
  Compared to established task queue libraries like Sidekiq, Celery, or asynq itself, cppq is a newer and smaller project with less real-world production usage, which may translate into undiscovered bugs or edge cases.
• Smaller community and ecosystem
  Because it has far fewer users and contributors than mainstream task queue systems, finding community support, third-party tutorials, or pre-built integrations is more difficult.
• Documentation gaps
  As a smaller project, cppq may have less comprehensive documentation compared to major task queue frameworks, requiring developers to read source code directly to understand advanced features or edge-case behaviors.
• C++ build and dependency complexity
  Using cppq requires managing C++ build toolchains and dependencies (such as a Redis client library), which can be more cumbersome than installing a package via pip or npm in other ecosystems.
• Fewer built-in features and tooling
  cppq likely lacks the extensive ecosystem tooling of more mature queues, such as web-based monitoring dashboards, extensive metrics/observability integrations, or advanced scheduling features found in more established solutions.

No analysis of BonHand yet.