My Subscription & Billing View
Learn how the My Subscription view in GC Surge exposes your active subscription, camera-based usage, billing details, and how to monitor overage risk. My Subscription is the customer-facing visibility layer for your commercial relationship with GC Surge. It shows your active subscription context, camera-level usage data, and feature configuration state. It is your primary tool for understanding your current cost exposure and monitoring for unexpected usage patterns. Covers: What My Subscription Does, Devices Usage Table, Monthly Review Workflow.
What My Subscription Does
My Subscription is the customer-facing visibility layer for your commercial relationship with GC Surge. It shows your active subscription context, camera-level usage data, and feature configuration state. It is your primary tool for understanding your current cost exposure and monitoring for unexpected usage patterns. The view also includes a Payment Method panel for managing your saved card, a Recent Invoices panel with your latest billing history, and a Payments Overview panel where you can compare plans, see your active subscription rate, and subscribe. To open My Subscription, click My Subscription in the left sidebar.
Review My Subscription monthly. Surprises at invoice time are almost always the result of not monitoring this view during the month.
Billing Context
GC Surge bills at a flat rate of €3 per camera, per month (for 250 to 1,999 cameras) — with a fair-usage alarm allowance of 3,000 alarms per camera per month. Overage is charged at €0.03 per alarm above that threshold. For full pricing and trial limits, see Plans & Pricing.
Two rules that affect how you read the table below: a camera is billable only if it generates 5 or more alarm events in the calendar month; overage is calculated per camera individually, not pooled across cameras.
Devices Usage Table
Every registered device appears as a row, and the panel header shows summary counters for total devices, billable devices, and alarms this month. Each row shows:
- Site name
- Device name
- Device brand
- Billable status
- Alarm usage for the current period (against the per-camera allowance)
- Overage alarms
- Overage cost (EUR)
- Device cost (EUR)
- Total (EUR)
This table is the primary tool for identifying high-usage devices and verifying that all registered devices are expected and authorized.
What Each Column Means
- Billable status — A camera is billable only when it is active (onboarded and not decommissioned) AND has generated at least 5 alarm events in the current calendar month. Cameras below 5 events appear in the table but are not charged.
- Alarm usage — A progress bar tracking alarms received this month against the 3,000-alarm fair-usage allowance for that camera. The bar turns red as the camera approaches the limit. Exceeding 3,000 does not trigger automatic overage charges — you must have explicitly accepted overage terms before charges apply.
- Overage alarms — Alarms sent beyond the 3,000 monthly allowance for that camera. Counted pre-filtering: every alarm ingested increments this counter, regardless of whether NOVA99x later classifies it as real or false.
- Overage cost — The overage charge for that camera this month: (alarms sent − 3,000) × €0.03, calculated independently per camera. Example: a camera that sent 3,800 alarms = €24.00 overage.
- Device cost — The subscription cost for that camera: €3 per camera per month, prorated if the camera was added or removed mid-month.
- Total — Device cost + Overage cost for that camera. This is what appears on your invoice for that device.
Filters and Controls
The Devices Usage Table includes two filters for navigating large deployments.
- Brand Filter — narrows the table to cameras from a specific manufacturer (Hikvision, Dahua, Axis, and others). Use this for brand-level usage analysis in mixed deployments. For precise results, verify individual camera brand assignments in Configuration.
- Site Filter — narrows the table to cameras at a specific site. Use this when reviewing usage for a single location rather than the full camera roster.
NOVA99x Configuration State
My Subscription includes a dedicated NOVA99x panel showing whether AI-assisted alarm verification is active for your account, with a control to Configure or Unconfigure it without leaving the billing view. When NOVA99x is active, it filters alarms before they reach operators, which lowers the alarm volume that counts toward overage. If your overage is significant, keeping NOVA99x active is the main lever for reducing next month’s bill.
Monthly Review Workflow
Conduct this review in the last week of each month to prepare for the incoming invoice.
- Check total active camera count. Compare against your expected operational roster. Unexpected cameras may indicate unauthorized onboarding or test devices left registered.
- Identify cameras approaching or exceeding 3,000 alarms. Use the alarm count column. Apply the Site Filter to focus on specific locations with high-volume cameras.
- Calculate overage exposure. For any camera above 3,000 alarms: (alarm count − 3,000) × €0.03 = overage for that camera. Sum across all cameras to estimate total overage.
- Review NOVA99x state. If NOVA99x is not active and overage is significant, evaluate enabling AI filtering to reduce next month's bill.
- Prepare a stakeholder summary. Draft a brief note for finance covering: current camera count, subscription rate, estimated invoice range, and any anomalies found.
Best Practices
- Name cameras meaningfully. Camera names appear directly in the subscription table. A camera named Camera 47 makes anomaly detection slow. Use names that include location, zone, or function so high-usage cameras are immediately identifiable.
- Set a calendar reminder for the 25th of each month. Reviewing My Subscription before the billing period closes gives you time to act on unexpected usage — not just observe it after the invoice arrives.
- Designate one subscription owner. Shared responsibility with no named lead means nothing gets reviewed. One person should own monthly review, invoice reconciliation, and escalating anomalies.
- Act immediately on unexpected usage spikes. A camera generating a sudden spike in alarms may be in a high-activity environment, stuck in a motion detection loop, or experiencing a hardware issue such as a fogged lens or IR bleed at night. Investigate at the source — do not wait until invoice day.