Metamorphic VS cppq

• Post-quantum cryptography
  Hybrid ML-KEM-768 + X25519 key encapsulation, the same approach as Signal.
• End-to-end encryption on all plans
  All data encrypted client-side before reaching the server. Every plan, not a paid upgrade.
• Zero-knowledge email
  No plaintext email stored. Only an HMAC blind index for lookups.
• Habit tracking
  Daily/weekly check-ins, streaks, and drag-and-drop reordering.
• Goal setting
  Milestones, progress bars, and habit linking.
• Self-reflections
  Mood tracking and daily prompts.
• Schedule & calendar
  Recurring events, day planner, and printable views.
• Progress insights
  Activity heatmaps and completion stats.
• Family & group accountability
  Shared habits, shared goals, group dashboard, and member spotlights.
• Client-side data export
  JSON/CSV export decrypted entirely in your browser. Server never sees plaintext.
• Three encryption layers at rest
  Client-side E2E → AES-256-GCM in Postgres → LUKS disk encryption.

• 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 Metamorphic yet.

Creator Walkthrough: Exploring Metamorphic’s Features & Benefits

No cppq videos yet. You could help us improve this page by suggesting one.

• I Built a Zero-Knowledge Encrypted Habit Tracker with Elixir & Phoenix LiveView

  I'm the solo dev at Moss Piglet, a bootstrapped public benefit company. I've been building Metamorphic — a habit and self-improvement tracker where all personal data is encrypted client-side before it ever reaches the server. The server... - Source: dev.to / 6 months ago

Tracking cppq since Nov 2022.