Skip to main content
TradeVulcan logoTradeVulcan
Web Spark Guides
Web Spark

Web Spark hosting: plans, HTTPS, usage and availability

Understand managed AWS website hosting, separate recurring charges, plan limits, monitoring, and what happens before republication.

What hosting does

Hosting makes the approved website available to visitors. Web Spark uses managed AWS delivery, private site storage, HTTPS and versioned releases. The website build purchase and hosting subscription are separate. Selecting a hosting preference during setup is not the same as activating a paid subscription.

The hosting panel and Billing view are the authority for your website’s current plan and status. Availability depends on the project, permissions, active access and completed provisioning—not merely a plan name displayed on a marketing page.

Choose the right plan

The public product page lists Essential, Performance and Enterprise hosting. Compare storage, monthly transfer, accessible history, analytics window, check interval and included AI-service credit. Confirm the current quote before purchase. The highest tier is not necessary just because your build package has a large generation allowance.

Consider the weight of images, retained versions, expected transfer and the history your team needs. A page count is not a storage measurement. A monitoring interval is not an uptime guarantee. Included AI-service credit is not unlimited generation.

Read usage correctly

The customer operations view can show storage, transfer, requests and HTTPS observations. Requests are not unique visitors. A probe response time is not a browser performance score. Missing measurements remain unknown; they should not be read as zero usage or perfect availability.

Private original images, variants and retained releases can contribute to storage. A history-access window does not promise that all older content is deleted. Review the actual displayed measurement before deciding whether you need to change plans.

HTTPS and domains

The default delivery address supplies managed HTTPS. A custom domain additionally requires current ownership, the correct certificate and actual DNS routing. The system checks the public result before treating the approved release as live. See the separate domain guide for the cutover steps.

Plan changes and limits

Use Billing to review upgrades, any proration, scheduled downgrades and cancellation. Check the effective date and consequences before approving. Read notices about usage, grace periods or restrictions; do not assume traffic over an allowance will simply incur an automatic overage charge.

Where the interface reports an over-limit restriction, resolve the measured cause and follow the required publication path. Do not delete useful content or buy another website as a workaround without understanding the underlying measurement.

After a pause or hosting lapse

Restoring access or resuming the project is not a new publishing approval. The hosting panel may offer Prepare draft for republication. Review the current website and approve a fresh release through the normal checks. Retained content and separately owned domains are not the same as active public hosting.

Before canceling, review the current retention and transfer terms with support, especially for a business-critical website. Do not rely on an assumed permanent archive or an automatic migration elsewhere.