Plans and packages compared

View as Markdown

Every HostTracker account is on a package (what the app calls a plan). A plan is not just a price tag - it governs a set of independent limits and entitlements at once. This page describes what a plan controls; for current prices and exact numbers, compare plans in the app or on the pricing page, since those change over time and this page does not repeat numbers that drift.

What a plan governs

Area	What it controls
Monitor count	The maximum number of monitors the account may have enabled at once. Some plans allow paying per extra monitor beyond the cap instead of hard-blocking; others hard-cap. A per-monitor-type override can further cap or unlock a specific type (for example Site crawl or Waterfall/page-speed checks).
Check interval	The shortest gap between checks a monitor on this plan may use (the account-wide floor). Some monitor types carry their own fixed cadence regardless of plan - certificate expiry, domain expiry and DNSBL checks run every 6 hours and Web Risk every 12 hours, on every plan.
Attached sub-checks	Whether SSL/TLS expiry, domain expiry, DNSBL and Web Risk can be attached to a Website/HTTPS monitor as a bundled extra check, and whether Site indexability tracking is available.
Assertion rules	How many AssertRuleLang validation rules an HTTP/API monitor can carry, and whether stateful (previous-result-aware) rules are available.
Cron scheduling	Whether a monitor can run on a cron expression instead of a fixed interval.
DNS resolver choice	Whether a monitor can use public third-party DNS resolvers or a custom/manual resolver list, instead of HostTracker’s default resolution.
TLS handshake policy	Whether a monitor can require a valid certificate chain, reject weak ciphers, require strong TLS versions, and check certificate revocation online.
Contacts	The maximum number of alert contacts, and a per-contact-type cap (for example a lower cap, or none at all, on voice-call contacts).
Reports	Which periodic report frequencies are available - daily, weekly, monthly, quarterly, yearly - or none at all on a plan that doesn’t include reporting.
Subaccounts	Whether the account can invite teammates as subaccounts at all.
API access	Whether the account may mint API tokens and call the REST API/MCP server.
Support level	Whether the plan includes priority support.
SMS/voice credit	The starting free SMS balance and the balance level that triggers a low-balance warning - see SMS balance.
Site crawl allowance	For plans that include Site crawl: how many pages the account may crawl per month, which also caps how many pages a single crawl run can budget for.

Changing plans never deletes your data - a downgrade that puts you over a new, lower cap doesn’t remove monitors; it pauses the excess or blocks creating more until you’re back under the limit. See Upgrade or downgrade.

The plan families

Free - a small number of monitors, longer check intervals, the core feature set. No card required, no expiry.
Personal - a small step up from Free: more monitors, still at a relaxed interval.
Solo - a single-monitor entry paid plan with the fastest interval, priced per extra monitor beyond the first - the right choice when one site matters more than anything else.
Webmaster / Business - the everyday paid tiers for a handful to dozens of sites: faster intervals, keyword/content checks, assertions, cron scheduling and more contacts. Business is HostTracker’s most commonly chosen paid tier.
Enterprise (offered in a few sizes) - the largest monitor counts, the highest assertion caps, subaccounts and the full feature set, sized to how many monitors you actually need.
The free trial - a time-limited plan with a much higher monitor cap and no card required. See The free trial.

Set it up in the app

Open Billing -> Packages to see every tier side by side, with the monitor cap, minimum interval and feature set for each, and your account’s current plan highlighted.

Do it with the API or MCP

GET /account returns your account’s current entitlements under limits (intervals allowed, bulk-operation caps, page-size caps) and usage (monitors/contacts/reports/maintenance windows used vs. allowed - null means unlimited). GET /monitor/type lists every monitor type with accountLimits: {minInterval, available} resolved against your current plan when you’re signed in. An MCP client uses get_account and list_monitor_types for the same information.

Limits and gotchas

A create that exceeds your plan’s monitor cap is refused (403 package_limit on the API; a validation error in the app) unless the operation explicitly opts to land the extra monitor disabled instead.
A monitor type your plan doesn’t include answers the same package_limit refusal with a feature naming the type (for example monitorTypeUnavailable.Crawl).
usage.<area>.allowed is null on the API precisely when that area is uncapped - never treat it as zero.