ReferenceGaFor developerFor agencyFor operatorFor evaluator

Plans, capabilities and billing decisions

Compare current eligibility, add-on capacity, limit behaviour, payments and renewal outcomes before committing a workload.

Last updated 2026-08-28

What you'll achieve

  • Compare plans from the live catalogue
  • Understand hard-limit behaviour
  • Prepare for renewal and payment failure

Use the live catalogue

The public Pricing page is generated from the same approved commercial catalogue used by checkout. It shows every currently purchasable plan and add-on, its USD price and billing interval, compatible plans, quantity range and included capacity. The signed-in Billing page is authoritative for a particular workspace because it includes contracted entitlements, add-on quantities and measured usage.

The current public families are Free, Dev Pro, Team, Agency Pro and Agency Scale. White-label delivery and portfolio observability are included only where the live plan comparison marks them Included. Enterprise capabilities are contracted rather than assumed. A feature shown as unavailable cannot be enabled by changing source code or repository structure.

Limits, compute and add-ons

BlinkHost does not automatically charge an overage. Monthly bandwidth, backend compute, outbound requests, preview work, database operations and telemetry stop accepting additional metered work when the applicable hard limit is exhausted. Existing source is not deleted because a monthly meter is full. Monthly meters reset on the date shown in Billing; resource-count and concurrency limits do not reset and require freeing capacity, buying a compatible add-on or changing plan.

Backend compute is measured as WebAssembly execution fuel rather than wall-clock seconds. Fuel is a deterministic runtime work meter, but application cost varies with code paths, data size and request volume. Use a preview or representative production canary, then compare its measured fuel and request counts in Usage before forecasting a larger workload. BlinkHost does not publish a universal requests-per-compute-unit conversion because it would be misleading.

Available add-ons, including project, seat, managed-database, storage and observability capacity, are listed with exact prices on Pricing. There is no unpublished pay-as-you-go path after a hard limit. If no compatible add-on is shown, reduce use, wait for a monthly reset or choose a plan with the required capacity.

Payments, renewal and cancellation

Direct public prices are in US dollars. The checkout provider shows the card methods it can accept, applicable tax and final total before confirmation; BlinkHost does not publish a guarantee that every card or country is supported. Microsoft Marketplace purchases use the currency, invoicing, payment and tax options available to that Microsoft account.

An eligible recurring payment that remains unconfirmed enters a seven-day grace period. BlinkHost sends a billing notice and Billing shows the deadline. Paid entitlements are suspended after the deadline; project data is not immediately deleted. Cancellation stops future renewal and takes effect at the end of the paid period. Review the Refund and Cancellation Policy before purchase and contact billing@blinkhost.me for an account-specific discrepancy.

When plan changes take effect

A paid plan or add-on becomes usable only after BlinkHost independently verifies the payment. The Billing page continues to show the previous entitlement while verification is pending. A verified purchase of a different plan starts that new plan and billing period immediately at the checkout price; BlinkHost does not calculate or promise an automatic prorated credit for unused time on the previous plan. Buying the same prepaid plan again extends its already-paid term instead of discarding the remaining time. A requested downgrade takes effect at the end of the current paid period.

For recurring subscriptions and recurring add-ons, submit cancellation and wait for the confirmation before the exact period-end timestamp shown in Billing. That displayed timestamp is the account-specific cutoff; a request received after the payment provider has begun the renewal cannot be treated as a pre-renewal cancellation. Cancellation preserves access until the displayed period end and does not itself request a refund.

Payment and purchasing availability

Direct self-service recurring checkout currently uses a supported debit or credit card. Bank transfer, mobile-wallet and invoice payment are not offered as standard public self-service methods. Microsoft Marketplace purchases use the payment, currency, invoice and tax methods available to the purchasing Microsoft account. Enterprise buyers that require an invoice or procurement review should contact Sales before placing an order.

BlinkHost does not block a published list of countries at the application layer. A purchase may still be unavailable because of the payment provider or card issuer, sanctions or export controls, or local law. A declined or unavailable checkout does not activate service and does not authorize BlinkHost to represent that a particular payment rail works in every country.

Help improve this page

Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.

Plans, capabilities and billing decisions | BlinkHost