Disabling a customer account is a reversible process. When an integrator disables an account, all users under that account are restricted from accessing any of the Starllion Portals and mobile app. The restriction applies not only to the video portal but also to the admin portal, alarm station, and mobile app. All cameras are paused, but archives and any clips created up to that point are preserved. Any links shared from the clips will remain active for the duration specified when the link was created. Charges may still apply if there are archives, clips, time-lapses, or shared links from the clip library for any cameras under the disabled account. To avoid further charges, the customer account should be deleted. However, deletion is irreversible, and once the customer is deleted, all associated data will be lost and cannot be restored. This includes users, all cameras under the account, roles, settings, cloud data such as archives, clips, time-lapses, shared links, events, and alerts. Additionally, all automation webhooks will be permanently deleted and must be recreated if the customer is re-added.

Disabling a camera is a reversible process designed to protect the privacy of the customer. It allows for temporarily halting the collection of new archives, such as when a customer is on-site and does not want their activities recorded. Even when a camera is disabled, the integrator will still incur charges for services associated with the camera, including traffic generated from saved clips, archives, shared links, analytics, time-lapses, and any other add-ons linked to the camera. When a camera is disabled, either by the customer or by the integrator on behalf of the customer, the live feed will no longer be accessible in the Video Portal, and new archives will cease to accumulate. However, the customer will still have access to saved time-lapses, clips in the library, events, and any archives stored on the cloud. Additionally, object search analytics for objects detected before the camera was disabled will remain accessible. Archives will be retained according to the duration specified in the "Recordings" tab. If long-term time-lapse is enabled for the camera, it will continue to be collected based on the schedule. To avoid further charges, the camera should be deleted. However, this action is irreversible, and once the camera is deleted, all associated data (archives, clips, time-lapses in the library, shared links, and events) will be permanently deleted and cannot be recovered.

When transitioning between billing plans for a camera, it’s important to note that the archives associated with the device may be affected. Changes to the billing plan will modify the archives based on the storage duration specified in the new plan. If the new plan offers a longer storage duration, all archives up to the point of the plan change will be retained. However, if the new plan has a shorter storage duration, archives beyond the new plan’s storage limit will be deleted, leaving only the data within the new retention period. For example: Moving from a Lite plan (7 days of storage) to a 30 Days with Analytics plan will preserve the first 7 days of archives. The archives will then continue until reaching the new 30-day period. Object detection will start from the moment the plan change occurs. Switching from a 30 Days with Analytics plan to a Lite plan will delete archives older than 7 days, retaining only the most recent 7 days of data and object detection information. These rules apply to both Fixed and Pay-as-you-go plans, with the platform automatically adjusting the archive duration when switching between plans. Note: Switching to a plan with Analytics does not affect the archive duration.

The Total Traffic displayed in the Statistics section of the Dashboard Menu indicates the amount of data used by customers or their users while viewing cameras through the video portal or mobile app. To determine the data used by the camera for internet consumption, refer to the Average Storage to estimate daily usage. This can then be used to calculate the approximate traffic consumed by the camera. Average Storage This metric shows the amount of data stored on servers. It is calculated by averaging the total archive used at the end of each day. If a camera is newly added, the Average Storage will increase daily until the archive reaches the selected storage duration. After that, it will remain relatively constant, assuming the camera is always online and streaming at the same quality. For example, if a camera is set for 15 days of storage and consumes 10 GB per day, by day 2, the Average Storage will be 10 GB. Statistics are updated daily at midnight, so on day 2, the consumption from day 1 will be shown. On day 3, Average Storage will be 20 GB, and it will continue to grow until day 16, when it reaches 150 GB. From that point, Average Storage will remain at 150 GB, assuming the camera is continuously operating and streaming at the same configuration. Even if the selected period is 30 days, the Average Storage will still be 150 GB in this example. Traffic Traffic reflects the amount of data downloaded from the servers when users view the camera in the video portal or mobile app. For instance, if a user reviews the camera daily for the same duration, resulting in 100 MB of traffic per day, on day 2, 100 MB of Traffic will be shown for day 1. On day 3, the total Traffic will be 200 MB, representing the usage from the previous two days. If the user continues viewing the camera for the same duration, by day 16, 1500 MB of Traffic will be displayed, and by day 31, 3000 MB of Traffic will appear. Unlike Average Storage, where daily usage is averaged, traffic accumulates daily over the selected period.

Custom prices can be set for all sub-integrators and customers to manage profits effectively.

Resolutions up to 4K are currently supported. For higher resolutions, contact the local integrator to request the desired quality settings.

When attempting to copy a subscription plan, an error message may appear stating, "Cannot copy a plan that is not a base plan." This occurs when trying to duplicate a plan associated with a sub-integrator. To successfully copy such a plan, the corresponding base plan must first be copied. It is important to note that all plans created by a sub-integrator are based on base plans linked to the main integrator account. If there is a need to copy a specific subscription plan for a sub-integrator, an operational manager can be assigned to provide the necessary capabilities. Typically, a sub-integrator operates independently, managing its own customer base, while the parent integrator manages costs for the direct sub-integrator only. As a parent integrator, the role is limited to overseeing the sub-integrator's billing plans and assisting when needed. In the role of parent integrator, an operations manager can be established to track all actions performed, ensuring that the account owner has a complete record of who performed each action and when.

Under the Pay as You Go plans, storage and traffic charges are calculated according to the following rules: Traffic Calculation: Traffic is the cumulative total of all activities generated by users interacting with the camera, including accessing the camera via the admin portal, mobile app, or video portal, viewing live or archived feeds, and traffic from widgets and shared URLs. The highest traffic is generated when users view video feeds, which contributes significantly to the total monthly traffic consumption for the camera. Storage Calculation (Daily Average Method): The platform uses the daily average method to calculate storage. Daily, the system tracks the storage used by the camera. At the end of the month, the daily storage values are summed and divided by the number of days in the month. For example, if a camera connects on the 5th day of the month, generates 5 GB of data per day, and has a 3-day archive, the daily average calculation works as follows: The first four days contribute 0 GB. Starting on day 5, the camera accumulates 5 GB per day (5 GB on day 5, 10 GB on day 6, and 15 GB on day 7). For the remaining days, the storage remains at 15 GB daily, as older data is replaced by new. The final calculation for a 30-day month would be: (0 GB * 4 days + 5 GB + 10 GB + 15 GB * 24 days) / 30 = 12.5 GB. Therefore, the charge would be for 12.5 GB of storage, even though the camera used 15 GB at the end of the month. In subsequent months, assuming the same streaming bitrate and continuous online status, the storage charge will be for the full 15 GB. These calculations ensure transparency and fairness in billing for storage and traffic usage under the Pay as You Go plans.

As an integrator, customer accounts are created and cameras are connected to the Starllion Cloud via ONVIF, direct RTSP, or HTTP URL through the admin portal. All video footage is stored in the cloud and accessible to end-users via web or mobile apps. Charges are based on either a pay-per-use model for storage and outbound traffic (with no charges for ingested traffic by Starllion Cloud) or a monthly fee per camera.

Starllion Cloud provides a comprehensive suite of services for integrators, including an admin portal, customer portal, end-user mobile, web, and executable apps. It supports both cloud and local/hybrid recording, flexible alarm schedules, and offers an API for integration with existing alarm or access management systems. Additionally, there is an option for branding. Pay-as-you-go plans are available for those who prefer not to commit to fixed camera fees.

Not for the public cloud setup. For private cloud setup and licensing, please reach out to the sales team.

Flexible plans and payment options are available.

The Pay-as-you-go plans provide full control over camera quality settings, which in turn affect the cost per camera.

A wide range of quality settings is supported, and a custom plan can be created to suit the desired application.

Offers are available. Contact the local integrator for a complete list of options.

Customers have the ability to control the markup for each billing plan in their account.