Subscription & Support Terms

These Subscription & Support Terms govern paid BidGlory subscriptions and support and are in addition to the BidGlory EULA and SLA. Provider is ProjectThunder.com, Inc. The EULA's ownership, warranty-disclaimer, and limitation-of-liability sections apply here in full.

1. Plans

Plans are priced per instance, not per user. No plan carries a per-seat or per-named-user fee, and adding users does not change the price of a plan. Provider may change pricing prospectively on 30 days' notice under §2.

• Open Source — free, self-hosted, for companies under $1M/yr in sales; community-forum support; no SLA.
• Hosting — Standard — $299/month. Managed single-tenant instance on shared infrastructure, updates + nightly backups, business-day email support, 99.5% uptime SLA. Up to 600 bids/year.
• Hosting — Business — $899/month. Dedicated resources, 99.9% uptime SLA, staging environment, point-in-time restore, SSO/SAML, priority support, quarterly review. Up to 3,000 bids/year.
• Hosting — Enterprise — from $2,500/month, annual term. Multiple instances (one per operating company or branch), high availability and disaster recovery with agreed RTO/RPO, custom SLA, security review support, named engineer. Unlimited bid volume.
• Per-Incident Support — $299 per incident. One indivisible issue worked to resolution; not a subscription; not divisible into sub-issues.
• Custom Dev Path — $1,250/month for 10 AI-enhanced development hours, plus bundled DevOps and hosting, plus 2 scheduled calls/month.

Higher Dev Path tiers are priced as multiples of the base and are available to subscribe up to 50 hours/month; every tier bundles DevOps + hosting:

• 20 hours — $2,500/month · 2 calls
• 30 hours — $3,750/month · 3 calls
• 40 hours — $5,000/month · 4 calls
• 50 hours — $6,250/month · 4 calls
• 100 / 200 / 300 hours — contact us for a custom high-volume arrangement.

1a. How hosting tiers are measured (bid volume, not users)

No plan is limited by user count. Customer may create unlimited user accounts on any plan — staff, contractors acting on Customer's behalf, and Customer's own clients in the customer portal — at no additional charge (EULA §2). Hosting tiers are distinguished by bid volume and by the infrastructure and service level Provider commits to.

• What counts. A "bid" is a distinct bid record created in Customer's managed instance during the measurement window. Saved versions, revisions, and duplicates-as-versions of an existing bid are not counted again. Self-hosted installations are not measured at all.
• Measurement window. Volume is assessed on a rolling 12-month basis, so a single busy month does not move Customer's tier.
• No throttling, no overage billing. Provider does not block, throttle, degrade, or refuse a bid for exceeding a band, and does not issue overage charges. Exceeding a band is never a breach of these terms.
• How a tier changes. If Customer's rolling volume passes the band for its tier, Provider notifies Customer and the tier changes at the next renewal following 30 days' notice, consistent with §2 and §4. Customer may instead reduce volume, move to self-hosting, or cancel under §4 before that date.
• Moving down. The same measurement works in Customer's favour: if rolling volume falls into a lower band, Customer may request the lower tier, effective at the next renewal.
• Provider's records. Provider's instance metrics are the authoritative count. Provider will share the figures it relies on with Customer on request, and will not use them for any purpose other than tier assessment.

2. Billing (PayPal subscriptions)

• Recurring plans are billed in advance each period through PayPal Subscriptions. By subscribing, Customer authorizes Provider (via PayPal) to charge the recurring fee automatically each period until cancelled.
• Auto-renewal. Subscriptions renew automatically until cancelled under §4. See §2a.
• Minimum term. Recurring subscriptions carry a minimum term of 3 months (3 billing periods). Cancellation is effective no earlier than the end of the minimum term.
• Prices are in USD and exclusive of taxes, which are Customer's responsibility. PayPal's own terms and fees apply.
• Price changes. Provider may change pricing or inclusions on 30 days' notice; changes take effect at the next renewal after the notice period.
• Failed payments. If a recurring charge fails, Provider may suspend the service (including hosting) after a short grace period and, if unresolved, terminate the subscription. Provider is not liable for downtime during a payment-caused suspension.

2a. Auto-renewal disclosure & consent (California ARL and beyond)

Provider's checkout and these terms are designed to exceed the California Automatic Renewal Law (Cal. Bus. & Prof. Code §17600 et seq.) and comparable statutes:

• Clear and conspicuous pre-purchase disclosure of the recurring amount, frequency, minimum term, that it auto-renews until cancelled, and how to cancel — shown near the consent control, before payment.
• Affirmative consent — the Customer must actively check a consent box to the recurring terms; the box is never pre-checked, and no subscription starts without it.
• Acknowledgment — after subscribing, Customer receives an acknowledgment restating the terms and the cancellation method, retained in the plan-management area.
• Easy online cancellation — Customer can cancel online at any time from the plan-management area (and via PayPal), without contacting support.
• Change / cancellation notice — at least 30 days' notice; the change takes effect at the end of that period and no earlier than the 3-month minimum term.

3. Dev hours & calls

• Dev hours are a monthly allotment. Unused hours bank and remain available for up to 24 months from the month accrued (hours older than 24 months expire). Hours are usable only while the subscription is active and are forfeited on cancellation or termination (not refundable or transferable, no cash value).
• Hours cover AI-enhanced development, DevOps, and the plan's included support calls. Work beyond the available balance requires a plan upgrade or is quoted separately.
• Scheduled calls are up to the number for the tier, ~30–45 minutes each, booked in advance during business hours; unused calls do not roll over (calls reset monthly).
• Provider prioritizes the Customer's backlog collaboratively but retains sole discretion over implementation approach, sequencing, and technical feasibility.

3a. Custom development — ownership, private label & source

This section governs work product created for Customer under a Custom Dev Path or other paid custom-development engagement, and controls over EULA §4 for that work product.

• Customer owns the custom work. On full payment for the period in which it was created, Provider assigns to Customer all right, title, and interest in the Custom Work Product — the features, modules, integrations, reports, document templates, and themes built specifically for Customer to Customer's requirements. Ownership is not contingent on the subscription continuing; it survives cancellation.
• Source code is delivered, not held. Provider delivers the Custom Work Product as readable source in a repository Customer controls, together with its build and deployment configuration. Provider does not withhold source as leverage, and Customer's copy is not disabled or revoked on cancellation.
• The core platform stays Provider's. Provider retains all right, title, and interest in the BidGlory platform itself and in its pre-existing materials, tools, libraries, and frameworks ("Background IP"), including any generally-applicable improvements to the platform. Where Custom Work Product incorporates or depends on Background IP, Provider grants Customer a perpetual, worldwide, royalty-free, non-exclusive licence to use, modify, and run that Background IP as embedded in the Custom Work Product, for Customer's own business purposes.
• Third-party components are carved out. Ownership and the licence above do not extend to third-party components, which remain governed by their own licences — including Syncfusion Blazor components, which are used under Provider's commercial licence and are not redistributable as part of Customer derivative works (EULA §5). Customer needs its own licence to redistribute or independently develop against those components.
• Private label / white label. Customer may apply its own name, logo, colours, typography, domain, and document templates to its instance, and present the result under its own brand to Customer's employees and to Customer's own clients (including the customer portal, generated proposals, and system e-mail). This does not by itself grant a right to resell, sublicense, distribute, or operate the platform as a service for third parties, which continues to require Provider's prior written consent under EULA §3 — Provider will consider OEM and reseller arrangements separately and in writing.
• Know-how. Provider may reuse the general skills, techniques, and know-how gained during an engagement, provided it does not use or disclose Customer's confidential information, data, business processes, or the Custom Work Product itself.
• No exclusivity by default. Unless expressly agreed in writing, an engagement does not make Customer's feature exclusive to Customer at the platform level; Provider may build comparable capability into the core platform independently. Where a feature is intended to be exclusive, it is stated in writing at scoping and priced accordingly.

4. Cancellation & refunds

• Customer may request cancellation at any time online (plan-management area or PayPal). Cancellation requires 30 days' notice and is effective at the end of that period, but no earlier than the end of the 3-month minimum term. Service continues until the effective date.
• The same 30 days' notice applies to any plan change (upgrade, downgrade, or tier change), effective at the next renewal after the notice period.
• All fees are non-refundable, and Provider does not pro-rate partial periods, except where a refund is required by non-waivable law.
• On termination, Customer may export their data (portable .bgbid files and standard exports) for 30 days, after which Provider may delete the hosted instance and its data.

5. Support scope

Support covers the operation and use of BidGlory. It excludes custom development outside the Dev Path allotment, third-party products, Customer infrastructure, data entry, and training beyond what a plan includes. Per-Incident = one discrete issue worked to resolution; a distinct problem is a new incident. Provider may decline abusive or out-of-scope requests.

6. Technology Preview

BidGlory is a Technology Preview: it is evolving, and features may change, be delayed, or be withdrawn. Except for the express SLA credits, the software and services are provided "as is" with no guarantee of fitness for a particular purpose, and Customer's data is always exportable.

7. Acceptable use

Customer will not use BidGlory to break the law, infringe rights, transmit malware, overload or probe the service, or resell/host the service for third parties without Provider's written consent (see EULA §3).

8. General

Provider may amend these terms on 30 days' notice; continued use is acceptance. These terms, the EULA, and the SLA are the entire agreement on their subject and supersede prior discussions. Governed by the laws of the State of California; venue in the state and federal courts located in California. Provider's aggregate liability is capped as stated in the EULA (not to exceed fees paid in the trailing 12 months).