OnlineOrNot VS cppq

• Ease of Use
  OnlineOrNot boasts a user-friendly interface that makes it simple for users to set up and monitor websites for uptime.
• Customization Options
  The service offers a range of configuration options, allowing users to tailor monitoring alerts and reports to their needs.
• Real-time Monitoring
  OnlineOrNot provides real-time monitoring capabilities, helping users to quickly identify and respond to downtime issues.
• Multiple Check Types
  The platform supports a variety of check types including HTTP, HTTPS, and keyword checks, ensuring comprehensive monitoring.
• Notification Integrations
  OnlineOrNot integrates with various notification systems like email, Slack, and other channels, ensuring that users are promptly informed of any issues.
• Affordable Pricing
  The service offers competitive and transparent pricing plans, making it accessible for both small businesses and larger enterprises.

Possible disadvantages

• Limited Advanced Features
  While adequate for most needs, OnlineOrNot may lack some advanced features that specialized monitoring services provide.
• Support Availability
  Customer support options may be limited, particularly for lower-tier plans, which could be a drawback for users requiring immediate assistance.
• Scalability Issues
  The platform might not be as scalable as some competitors, which could pose challenges for very large enterprises needing to monitor a vast number of sites.
• Learning Curve
  Despite its user-friendly interface, some users may still face a learning curve when first getting started with the platform.
• Dependency on Internet
  As an online service, OnlineOrNot itself depends on having a reliable internet connection, which could be a drawback if users have unstable internet access.

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

Monitor a Website with OnlineOrNot

More videos

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

• Ask HN: What are you working on? (September 2026)

  Still OnlineOrNot (https://onlineornot.com/), 5.5 years on. Most recently I shipped an MCP server (w/ OAuth sign-in) recently to expose the API a bit better to agents, a TypeScript SDK and rewrote the CLI to use it. Just before LLMs... - Source: Hacker News / about 1 month ago

• Ask HN: What are you working on? (April 2026) (Non AI)

  Still OnlineOrNot (https://onlineornot.com/) - I've been working on adding more and more configurability to the browser checks feature. More recently, I've made it so you can drop your existing playwright test suites into the code... - Source: Hacker News / 7 months ago

• Ask HN: What Are You Working On? (March 2026)

  I've been celebrating five years of working on OnlineOrNot (https://onlineornot.com/) by adding more features for teams that build software: - 2FA, PassKey, and password-based login for folks that hate magic links - Moved my entire API... - Source: Hacker News / 8 months ago

View more

Tracking cppq since Nov 2022.