{% extends "base.html" %} {% load staticfiles compress %} {% block title %}Pricing - It's Free! - healthchecks.io{% endblock %} {% block content %}
{% if messages %}

We're sorry! There was a problem setting up the subscription. Response from payment gateway:

{% for message in messages %}

{{ message }}

{% endfor %}
{% endif %} {% if sub.plan_id %}

{% if first_charge %} Success! You just paid ${{ sub.price }}. {% else %} You are currently paying ${{ sub.price }}/month. {% endif %} See Billing History.

Thank you for supporting healthchecks.io!

{% endif %}

free

  • Personal or Commercial use
  • Unlimited Checks
  • Unlimited Alerts
  • 100 log entries / check
  •  

$5/mo

  • Personal or Commercial use
  • Unlimited Checks
  • Unlimited Alerts
  • 1000 log entries / check
  • Team Access

$20/mo

  • Personal or Commercial use
  • Unlimited Checks
  • Unlimited Alerts
  • 10'000 log entries / check
  • Team Access

What is the "log entries / check" number?

healthchecks.io keeps a log entry for each ping it receives. The log entry contains the date, the source IP address, the protocol (http or https) and the user agent string. The log can be useful for auditing past activity of your cron jobs.

There is a per-check limit of how many log entries are kept. When this limit is reached, the oldest log entries are culled. You can increase this limit by upgrading to paid plans.

When is 100 log entries per check sufficient?

It depends on how frequently your cron job runs and for what time period you want to keep a log of received pings. For example, if your cron job runs once a week, then the 100 log entries will cover 2 years. On the other hand, if the cron job runs every 5 minutes, then the 100 log entries will only cover 8 hours.

If I cancel my paid plan, do I get a refund?

You can easily cancel your subscription at any time, but no refunds are provided for prorated periods.

{% endblock %} {% block scripts %} {% compress js %} {% endcompress %} {% endblock %}