Fluxguard Pricing for Website Monitoring

Fluxguard pricing for website monitoring currently starts with a free plan and ranges from $110 to $550 per month for the listed paid self-service tiers. Fluxguard says its site-count estimates assume about 10 pages per site crawled once daily; actual usage is credit-based, so estimate page crawls and optional features before choosing a plan. Prices below are the amounts visible on Fluxguard’s official pricing page when reviewed in 2026; confirm the current price and checkout total before subscribing.

Fluxguard plans and listed monthly prices

Plan	Listed price per month	Estimated sites per month*	Users	Versions kept per page	Listed features
Free (Gyroscope)	$0	3	1	3	Chrome crawler; visual, HTML, and text change detection; instant or daily alerts; English translation
Standard (Periscope)	$110	25	3	25	Custom page filters, network blocks, form-submission tracking
Plus (Telescope)	$220	50	5	100	Custom AI prompts, AI summaries, proxy network
Premium (Horoscope)	$550	100	10	100	Consolidated AI email summaries, AI filtering, crawling as often as every five minutes, webhooks

*Fluxguard’s estimate assumes approximately 10 pages per site, with each page crawled once per day. The service uses credits, and actual usage may vary. These are planning estimates, not guaranteed capacity. Source: Fluxguard pricing page.

The paid self-service plans are listed with a seven-day trial, after which billing is automatic monthly or annually according to the selected option. Fluxguard says subscribers may cancel at any time. The pricing page labels annual billing “2 months free,” but the annual toggle’s exact totals were not available in the reviewed page view. Do not infer the annual checkout amount by multiplying or discounting the monthly prices; confirm it on the pricing page or at checkout.

How Fluxguard credits affect the cost

Fluxguard’s FAQ says one page crawl uses one credit. Credits are allotted monthly, reset on the subscription start date, and unused credits do not carry over. Optional features also use credits, so your actual workload is not always just the number of pages multiplied by crawl frequency. The FAQ lists extra credit use for AI prioritization and summaries, English translation, enhanced proxies, AI overviews, and AI-guided link harvesting. Check the current account or pricing information for the applicable rates, since they can change. See Fluxguard’s FAQ.

Estimate the base crawl credits

Start with the number of pages you intend to monitor, then multiply by crawls per day and days in the billing month:

monthly crawl credits = pages × crawls per day × days per month

For example, a 10-page site crawled once daily is roughly 10 × 1 × 30 = 300 page-crawl credits in a 30-day month. Fluxguard’s FAQ gives 300 credits per month for that example. Crawling those 10 pages hourly is 10 × 24 × 30 = 7,200 credits; that is also the vendor’s example. These figures describe the base crawl arithmetic, not a guarantee about plan capacity or a complete estimate when optional features are enabled.

Monitoring schedule	Base monthly estimate for 10 pages (30 days)	Use case to consider
Once daily	300 credits	Pages where daily change detection is enough
Hourly	7,200 credits	Pages where faster detection justifies much higher crawl volume

Estimate a mixed schedule

You can model high-priority pages at a faster cadence and low-priority pages less often. Calculate each group separately, then add the estimates and any optional-feature usage:

monthly credits = (high-priority pages × high-priority crawls/day × days)
                + (other pages × other crawls/day × days)
                + optional-feature credits

For instance, if 4 pages are checked hourly and 16 pages daily in a 30-day month, the base estimate is (4 × 24 × 30) + (16 × 1 × 30) = 3,360 credits. This is an arithmetic planning example, not a Fluxguard plan allowance. Mixed schedules can focus monitoring effort and reduce unnecessary alerts, but check the product’s available scheduling controls and credit rates for your account.

Which Fluxguard plan fits your monitoring workload?

Use the listed site counts as a rough orientation only. They rely on the 10-pages-per-site, once-daily assumption, so they can overstate capacity if sites have more pages, you crawl frequently, or optional features consume credits.

• Free (Gyroscope): a starting point for a small, one-user monitoring setup that can work within the listed estimate of three sites. It includes visual, HTML, and text change detection, plus instant or daily alerts.
• Standard (Periscope): consider it when the listed custom page filters, network blocks, or form-submission tracking matter, or when you need the listed three-user cap and 25 retained versions per page.
• Plus (Telescope): consider it when custom AI prompts, AI summaries, or a proxy network are relevant. Its listing allows five users and keeps up to 100 versions per page.
• Premium (Horoscope): consider it when you need listed features such as consolidated AI email summaries, AI filtering, webhooks, or crawling as often as every five minutes. It has the highest listed user cap (10) and the same 100-version history as Plus.

These are plan descriptions from Fluxguard’s pricing page, not independent performance validation. Confirm that the plan’s credit allocation covers your page count, cadence, and chosen optional features before relying on the estimated number of sites.

What Fluxguard monitors

Fluxguard describes its crawler as headless Google Chrome, used to render pages that depend on JavaScript. Its FAQ describes text, rendered DOM/HTML, visual, and network-activity monitoring, with filters to focus on relevant page areas. It also describes proxy locations for geo-restricted or otherwise difficult content. These are vendor descriptions; this guide does not make independent claims about detection accuracy or crawl performance. Feature availability can differ by plan, so consult the current pricing page and FAQ.

Trial, billing, cancellation, and annual pricing

• Trial: the pricing page says paid self-service plans begin with a seven-day trial, then billing is automatic monthly or annually based on the selected option.
• Annual option: the page displays “2 months free.” The exact annual totals were not verified in the reviewed page view. Confirm the amount and billing schedule on the live page or checkout.
• Cancellation: Fluxguard’s FAQ says monthly self-service subscribers can cancel at any time; service ends at the close of the billing period. It says unused credits are not refunded.
• Annual or invoice payment: the FAQ says annual plans may be purchased through the pricing page or by contacting Fluxguard, and invoice payment can be arranged. Confirm terms for the specific plan.
• Currency and changes: Fluxguard’s terms state payments are in USD and that service features, prices, availability, and credits may change. Recheck before purchase.

Sources: official pricing page, FAQ, and terms.

Reliability, monitoring cadence, and cost planning

Monitoring cost is only one part of deciding whether a cadence is appropriate. Faster crawls can identify changes sooner, but they also increase page-crawl credits and may create more notifications. Decide how quickly you need to know about a change, use a shorter interval only for pages where that matters, and route or filter alerts so that a high volume does not hide important changes.

Before subscribing, write down the pages to monitor, the required crawl interval for each group, and any optional features. Calculate the base credits, then check Fluxguard’s current add-on credit rates and plan allowance. Leave room for changes to the monitored page list or crawl schedule. Since unused credits do not carry over, avoid choosing an allowance solely for a short-lived peak unless the flexibility is worth the cost. No independent uptime or performance figures are available in the reviewed sources, so use the trial to assess fit for your own pages and workflows.

Fluxguard pricing troubleshooting

What you see	Likely reason	What to do
Your site count does not match the plan estimate	The estimate assumes about 10 pages per site, once daily; your crawl volume or optional features may be higher.	Estimate by page and cadence, include optional-feature credits, and confirm plan allowance in the current account details.
Credits run out before the month ends	More pages or more frequent crawls were used than planned, or credit-consuming options increased usage.	Review actual page crawls and enabled options; reduce cadence for lower-priority pages or choose an allowance that fits the measured workload.
Unused credits disappeared	Fluxguard says monthly credits reset on the subscription start date and do not roll over.	Plan around the reset date and avoid buying capacity far above expected recurring use.
The annual price is unclear	The pricing page’s annual toggle did not provide a verifiable total in the reviewed page view.	Check the current pricing page or checkout and confirm the recurring annual total before starting the trial.
You were charged after a trial	The pricing page says paid plans bill automatically after the seven-day trial according to the selected monthly or annual option.	Review the selected billing interval and trial end date before subscribing; contact Fluxguard about account-specific billing questions.
You canceled but service or a charge remains until a date	The FAQ says service continues through the end of the billing period after cancellation; unused credits are not refunded.	Check the billing-period end date and the cancellation confirmation, and contact Fluxguard if account records do not match.

Alternative for one-off website screenshots: ScreenshotNeo

Fluxguard is for recurring website change monitoring. If your immediate task is to capture a page as an image or PDF, ScreenshotNeo is a separate website screenshot API and MCP server from Yorker Media. It is not a change-monitoring replacement. Its API accepts one GET request with a URL and returns a PNG, JPEG, WebP, or PDF; it can also handle full-page and element captures, custom CSS and JavaScript, and many other capture options. See the ScreenshotNeo API documentation.

Or skip the browser setup:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. Start with 1,000 free screenshots a month, no card required.

Fluxguard pricing FAQ

How much does Fluxguard cost?

The official page listed a free tier and paid monthly prices of $110, $220, and $550 when reviewed in 2026. Prices and plan details can change; verify the live checkout amount.

How many credits does a page crawl use?

Fluxguard’s FAQ says one credit per page crawl. Optional features can use additional credits.

Is Fluxguard billed monthly or annually?

The pricing page offers monthly and annual billing. It labels annual billing “2 months free,” but confirm the exact annual total before subscribing.

Can I estimate cost from the number of websites?

Use the published site estimate only as an initial guide. It assumes about 10 pages per site crawled once a day; page count, cadence, and optional features determine actual credit needs.

Are the monitoring and pricing figures independently tested?

No independent tests or price validation are included here. The plan details and usage examples are attributed to Fluxguard’s own pages.