Welcome to Starllion Cloud This page provides essential links to helpful resources, instructions, and downloads needed to get started. Starllion Cloud Architecture Starllion Cloud VMS is comprised of the Admin portal, Video portal, Alarm station, and Video wall. Admin Portal: Manage customer accounts and cameras. Video Portal: View live camera streams, review events and archives, and search for recognized objects and faces. Video Wall: Display multiple live feeds simultaneously for enhanced visualization. Alarm Station: Monitor critical events through an alarm system, receive notifications, review recorded events, and search for significant activities. Getting Started To add the first camera, a customer must be created. There are various methods for adding a new camera, with the best option depending on the camera model and the network setup at the installation site. Smart Analytics Setup Once a camera is integrated into the system, server-side smart analytics can be activated. Several modules are available, including Object Detection, Face Recognition, Smart Alarms, and Push Notifications. Branding Option for Admin and Video Portals Starllion Cloud offers branding options for both the Admin and Video portals. This allows for showcasing custom branding and logos across the products. Free Rebranding: The login page and letters can be customized, and custom URLs can be requested for the main integrator account and sub-accounts. Starllion Cloud copyright will remain visible. More Useful Resources Users in the Starllion Cloud environment are assigned roles that determine the available features and functions. Understanding the roles is crucial to building a successful organizational structure and ensuring proper access levels. If customers are given access to the Admin portal, they will have limited access compared to the primary user. It is possible to control the permissions for each customer in the Admin portal. If there are questions or issues regarding system features or unexpected camera behavior, this portal likely contains tutorials, guides, or manuals that can help. For example, a camera troubleshooting tutorial for common issues is available here. A manual on configuring a camera connected to both the VMS and another device, such as an NVR, can be found here. For assistance with camera selection, review this guide. Explore the Help Center for articles and files necessary to successfully grow the business with Starllion Cloud. Support tickets can always be submitted with questions about the system, and customer support agents will work to assist in fully utilizing all system capabilities. The Starllion Cloud success team is here to help.

Starllion Cloud provides two monthly cloud service subscription options for cameras in the Starllion Cloud admin portal: Option 1 (Fixed plans) and Option 2 (Pay As You Go). Cameras integrated using the P&P connection method are eligible for either plan, while cameras added via the ONVIF or Generic methods are only eligible for the Pay As You Go plan. Option 1 offers fixed monthly costs with preset cloud retention and streaming settings, making it easy to resell with a fixed margin. Option 2 is based on usage, where the subscription cost varies depending on the cloud data storage and streaming consumption. These two options are designed for the following reasons: To offer flexibility to customers by allowing the use of a variety of camera types and billing based on actual usage. To provide customers who prefer predictable pricing with fixed plans for P&P cameras and gateway-enabled devices. For cameras using the Fixed plan, the platform enforces preset streaming settings to guarantee a fixed monthly cost. Cameras added through ONVIF or Generic methods must use the Pay As You Go plan, which provides more flexibility without limiting customers to specific settings. This plan allows payment based only on actual usage. When a camera is assigned to the Pay As You Go plan, users can customize the Quality and Recordings settings in the admin portal. The subscription cost depends on the monthly cloud storage and traffic usage, charged at the same TB rate per camera. Cloud storage usage varies based on the average variable bitrate up to the preset limit in the Recording tab. Cameras with bandwidth-efficient codecs adjust their bitrate in real time for more efficient storage use. Traffic costs depend on the number of users accessing the camera feed through the Starllion Cloud video portal, alarm station, or mobile apps. High traffic, such as frequent surveillance playback by multiple users, can lead to increased costs. While inactive users are logged out after thirty minutes, it's important to communicate that cloud playback is not designed for constant monitoring like a traditional video wall. For such applications, an on-premise NVR is recommended. The "My Invoices" tab in the Integrator account provides monthly cost breakdowns, while daily cloud usage can be monitored through the Dashboard or individual camera settings. This helps estimate end-of-month costs. Additional Fixed plans with customized cloud retention and streaming settings are available upon request through a support ticket. For further inquiries or to explore additional pricing FAQs, please contact an Starllion Cloud account executive.

Getting Started with the Starllion Cloud VMS Solution Welcome to the Starllion Cloud. This guide explains how the platform functions, provides instructions on getting started, details the available features, and outlines how and where to access different services. The page includes links to helpful resources, articles with step-by-step instructions, and downloadable files required to begin. Starllion Cloud Architecture The Starllion Cloud VMS consists of three primary portals: Admin Portal: http://www.admin.starllion.com Video Portal: http://www.video.starllion.com Alarm Station: http://www.alarm.starllion.com Each portal can be co-branded, allowing customization of login pages and interface colors to match company branding. Custom branding can be applied individually for each customer and a separate branding option is available for the main integrator account. Admin Portal The Admin Portal serves as the backend for Starllion Cloud, where integrators can manage customer accounts and oversee all aspects of the client lifecycle. Customers can create users for their accounts and set access levels for each individual. There are no limitations on the number of users that can be created, and up to 10,000 simultaneous viewers are supported per camera by default. Many of the Admin Portal menus resemble spreadsheets, allowing for sorting and searching like standard spreadsheets. Every table has modifiable and sortable columns. Dashboard The Dashboard is the default page when accessing the Admin Portal, visible at both the Integrator and Customer levels. Integrators see statistics for all customers, while individual customers only see their own account data. By adjusting the date range, different time frames can be viewed. For graphical representation, the Charts button provides camera-specific data showing storage, traffic, and clip durations over the past 3 months. Data can be filtered by camera and selected dates. User Levels and Types Integrator Level Users: An integrator is a partner who connects new customers to the services. They can manage all other user types, including creating and modifying user roles and controlling access to the Admin and Video portals, as well as billing modules. Managers can be created to assist with customer management tasks but cannot delete or modify integrator users. Note: Integrator-level users cannot log into the Video Portal, ensuring customer privacy. If integrators need to view footage, they must create a tech support user at the customer level. Customer Level Users: Customers can create users with specific roles, granting either full or limited access to the Admin and Video portals. The user list can be sorted by any column and columns can be customized. The system includes three user types: Owner: Each customer account has one owner, who always has full access to all cameras unless restricted by the integrator. Admin: Admins access the Admin portal, manage cameras, and configure settings based on their permissions. Guard: Guards do not have access to the Admin portal and can only view cameras and perform actions like creating clips or using PTZ controls based on role permissions. A Guard cannot delete clips created by other guards. Clips can only be deleted by the same Guard or an Admin user with appropriate permissions. Menu Roles Customer-level roles are categorized into Admin and Guard types, with the role defining what cameras and features can be accessed. - Admin Role: Allows access to both Admin and Video portals for managing cameras and users. - Guard Role: Limited to the Video portal, where users can view streams, create clips, and share cameras based on permissions. Customers (Visible to Integrator Level) The Customers menu displays all current customers and integrators. Clicking on a customer name shows their properties. The table is not updated in real-time; refreshing the page is required to see changes made by others. The Deleted Customers tab allows viewing of deleted clients and integrators. Custom column settings can be adjusted using the Columns button, and tables can be sorted or filtered as needed. Manager (Visible to Integrator Level) The Managers menu lists users with managerial access, including operational, billing, and sales managers. Changing a manager's role, password, or reviewing activity logs is done by selecting the manager's name and using the appropriate tabs. When creating a new manager, select their role and generate a secure password, or provide a temporary password for the manager to change on the first login. Cameras The Cameras menu at the integrator level shows cameras assigned to direct customers but not those of sub-integrators. Accessing cameras of sub-integrator customers requires logging in with the sub-integrator’s credentials. On the integrator level, the P&P Cameras tab displays cameras for all customers, while the Customer Cameras tab displays cameras from individual customers. The Deleted Cameras tab shows cameras that have been removed. To add a new camera, select the Add button and choose whether to assign the camera to a customer. Pre-registering cameras in the system for future assignment reduces setup steps when installing a new camera. Adding a New Camera - To add a new camera: Go to the Cameras tab and click Add. Select how to connect the new camera. Add P2P Camera A P2P (peer-to-peer) connection is the simplest and most secure method. It requires no public IP setup and automatically ensures secure data flow to the cloud over HTTPS. This method is preferred as it prevents connection disruptions due to IP address changes. Add ONVIF Camera Adding an ONVIF camera requires manual configuration, including port forwarding on the client’s router. This method allows direct camera configuration from the Admin portal and retains ONVIF-compatible features. However, access may be interrupted if the client’s IP address changes, though services like DynDNS can help mitigate this. Adding a Generic Camera This method is designed for cameras that cannot be added using P2P or ONVIF methods. Only the RTSP port needs to be forwarded, although if the camera has an HTTP/service port, it can be added as well. If event information is sent through this port, events will be displayed in the video portal. If no event data is sent, no events will be registered for cameras added via this Generic method. To set up, a specific path to the camera’s video stream must be provided after the port number. Control of these cameras is not supported, and the only available payment model for such cameras is the Pay As You Go option. The camera must support H.264 encoding for the video stream to be added via RTSP or RTMP connection. The stream's quality can be configured through the camera’s own web interface. Note: If the client's internet service provider changes the IP address, camera access may be interrupted, and manual adjustments to the access path might be required. To avoid disruptions caused by changes in the public IP address, services like DynDNS can be used. Alerts Integrator-Level Alerts At the Integrator level, alerts can be created for system events and sent to the integrator's email inbox or to registered managers. This setup allows for centralizing alerts for all customers into a single inbox, rather than sending multiple emails for each individual customer. To create a new alert, click on the “Create System Event” button and select the customer for whom the alert should be set. Then, configure the alert parameters. Alerts can be aggregated into a single notification to reduce the frequency of alerts related to recurring issues. Customer-Level Alerts At the Customer level, alerts can be created for both sensor and system events. These alerts can be delivered to users registered under the selected customer, either via email or push notifications, provided server analytics is used as a trigger. To create or edit an alert, navigate to the Alerts tab in the customer menu. Select “Create Sensor Event” for sensor-related events, such as motion or intrusion, and choose the desired Alert Type from the drop-down menu. For more details on creating alerts, refer to the dedicated instructions page. Logs Integrator-Level Logs Logs at the Integrator level allow tracking of all manager and integrator activity. Logs can be viewed in one of three modes: By Count – Displays the most recent entries from a selected time period. By Time – Shows entries for the last specified number of hours. By Period – Displays logs for a defined time frame. To view the details of any log entry, simply click on it. Customer-Level Logs Logs at the Customer level provide an overview of all activity for that customer's users. The same viewing options as the Integrator level are available. Entries can be reviewed by Count, Time, or Period, and details can be accessed by clicking on a specific entry. Billing Module The Billing module streamlines financial and administrative tasks for the cloud service platform. Accessible by Integrators, Billing, and Sales Manager roles, this module assists in managing all aspects of customer billing, including generating monthly invoices, integrating third-party payment systems, and connecting accounting solutions. The platform also allows for the customization of invoices with additional billable items and provides detailed consumption breakdowns. This module offers tools to manage recurring revenue, including marking up costs for cloud storage and add-on plans. It supports unique billing plans for each customer, with customizable tax rates and pricing structures. API Keys API methods enable integration with third-party software. With over 75 available methods, you can create, modify, or delete platform components and automate routine tasks. To access these methods, each integrator and customer has a unique API key, which can be found under the API Keys menu or by using the API key retrieval method. To disable specific API methods for a customer, use the Enable/Disable slider next to the desired method. Video Portal The Video Portal offers a centralized platform for viewing live camera streams, reviewing events and archives, and searching for recognized objects or faces. User Interface Overview: Top Menu Bar - Provides access to main features and settings, including the Help menu and Profile options. Camera Controls - Appears when hovering over the camera feed and includes available action buttons based on camera features. Bottom Toolbar - Contains tools for managing camera timelines and global camera controls. Thumbnails - Displays still images from the camera footage at specific time intervals. Timeline - Indicates available archive footage, with darker areas marking event-based recordings. Black gaps represent times when the camera was offline. Alarm Station The Alarm Station monitors camera activity to reduce the need for constant live stream monitoring. When an event is detected, the camera feed is triggered and displayed with an accompanying sound notification. This system allows for quick response to detected events. Mobile Application The Starllion Cloud mobile app is available for both Android and iOS devices. It allows users to access the Video Portal, view recent events, manage cameras, and access archived footage. Note: Integrator accounts cannot log into the mobile app, as integrators do not have access to camera streams. Once logged in, users can access the Events tab, select a camera, and filter events by camera, object type, or color. Additionally, saved layouts and camera views can be accessed via the 'Layout' option in the app.

Ensure that a valid credit card with available funds is added to the Starllion Cloud account. Signing into the Integrator account is required for this process. After registering for the Starllion Cloud Integrator account, the first 30 days of cloud usage are free, providing an opportunity to explore different plans, settings, and add-ons without incurring additional charges, aside from the one-time setup fee. Subsequent months will include a minimum maintenance fee, which is not a separate monthly charge but a minimum spend allocated towards account hosting, technical support, and training. Once the minimum monthly cloud consumption spend is exceeded, charges will apply only for the cloud usage accumulated. At the end of each month, an invoice from Starllion Cloud will automatically be generated in the My Invoices section of the Integrator account. This should not be confused with the Billing module in the top menu, which is for client billing. The billing module generates an invoice once the month ends, accessible through admin portal access. Charges will be processed using the credit card on file based on the newly generated invoice and any outstanding balance. If there is an issue with the credit card, such as insufficient funds or an expired card, a notification will be sent. Keeping the credit card information up to date and ensuring sufficient balance is essential to avoid service interruptions and additional charges. Starllion Cloud service is billed monthly, with an option to save 10% by prepaying for a year. This can be helpful for clients opting for annual billing, easing monthly cash flow management. To close an Starllion Cloud Integrator account and avoid future charges, request account closure by contacting support@starllion.com. To temporarily disable cameras, go to the Camera settings in the Integrator Account, General Tab. Note that any analytics and retained data from disabled cameras will still contribute to the monthly invoice. Charges will cease only when the camera is deleted or after the associated data expires.

Introduction The upload speed is crucial for camera systems, yet many internet service providers fail to highlight this aspect, often offering upload speeds that are only a fraction of the advertised download speeds. This can lead to confusion when setting up and configuring cameras, as a low upload speed limits the number of cameras that can stream simultaneously. Many internet plans offer asymmetric speeds, where the upload speed is much lower than the download speed. For instance, a plan marketed as offering 150 Mbps may only provide 5 Mbps for uploads. While this is typically sufficient for tasks like browsing or streaming, it may cause problems for cloud-connected cameras. Therefore, it's essential to understand the number of cameras that can be supported by the existing upload speed or determine the required upload bandwidth based on the number of cameras planned. Rough Estimation Method To estimate the upload speed required for different camera resolutions, the following approximations can be used: 720p cameras: 0.5 Mbps upload per camera 1080p cameras: 1 Mbps upload per camera 4 MP cameras: 2.5 Mbps upload per camera 4K cameras: 3.5 Mbps upload per camera These values are rough estimates, as the actual bitrate may vary depending on the camera model and scene complexity. However, they offer a useful starting point for estimating either the maximum number of cameras that can be supported or the required upload bandwidth for a given setup. Calculating the Number of Cameras with Known Upload Speed To determine how many cameras can be connected with a known upload speed, simply divide the upload speed by the required bandwidth per camera. For example: For 10 Mbps upload speed: 720p cameras: 10 Mbps / 0.5 Mbps = 20 cameras 4 MP cameras: 10 Mbps / 2.5 Mbps = 4 cameras Calculating Upload Speed for a Known Number of Cameras If the number of cameras is already determined and the required upload bandwidth needs to be calculated, multiply the number of cameras by the bandwidth requirement per camera. For example: For 5 cameras at 720p resolution: 5 x 0.5 Mbps = 2.5 Mbps For 5 cameras at 4K resolution: 5 x 3.5 Mbps = 17.5 Mbps Advanced Method To calculate the exact upload speed needed for multiple cameras streaming at once, follow these steps: Determine the average bitrate for each camera. For cameras on fixed plans, the bitrate is often listed in the billing plan tab. For cameras on pay-as-you-go plans, check the quality settings for bitrate. Multiply the bitrate by 2 to account for "spikes" in bandwidth usage when I-frames (keyframes) are transmitted. During regular streaming, a camera sends I-frames at intervals, and between those, it sends smaller p-frames. When an I-frame is sent, the bandwidth usage temporarily spikes. Doubling the bitrate ensures that enough bandwidth is available to handle these spikes. Multiply the result from Step 2 by the number of cameras with the same bitrate. If there are groups of cameras with different bitrates, calculate the bandwidth requirements for each group separately, then sum them to determine the total upload bandwidth needed. Account for metadata: Cameras also send metadata, including event data, camera status, health checks, and connection packets. While this data is typically small, it can become significant when dealing with many cameras. Add a buffer: Since the internet connection will often be shared with other devices or users, add 3-4 Mbps as a buffer to account for other traffic. Thus, the total bandwidth requirement will be the sum of the calculations from Steps 3, 4, and 5. Example Calculation Consider a system with 10 cameras: 6 cameras set to 700 Kbps and 4 cameras set to 400 Kbps. The total upload speed required would be: ((700 x 2) x 6 + (400 x 2) x 4) + 4 = 15600 Kbits or about 15.5 Mbit of upload speed is needed. (Blue color represents step 3 / Green color represents step 4 / Purple color represents step 5) If the connection is dedicated to the cameras, it may work with around 8-9 Mbps, but a higher bandwidth is recommended to reduce the risk of connection issues and video stream loss. Note: Satellite internet connections, especially those not using Starlink, suffer from high latency, often up to 2 seconds. This can cause buffering issues, as cameras must wait for a response from the server, leading to frame drops and disrupted video streams. Consequently, such conditions are not ideal for camera systems that require stable and low-latency connections.

Introduction Capture the progress of a project over time with the timelapse feature, designed to document every stage, regardless of the project’s duration. Whether the project spans weeks or years, this feature allows for ongoing review, downloading, and sharing of the complete timelapse video at any point during or after the project. The ability to monitor progress and share the result with others is always available. Note: Currently, timelapse features can only be enabled by our team. Future updates will include the option to configure timelapses directly through the admin portal. Timelapse Options For 4K timelapse recording, the camera must support 4K resolution, and the main streaming channel of the camera must be configured for this resolution. Starllion Cloud offers three solutions for timelapse recording: Single Camera Configuration at 4K The camera streams continuously at 4K, which increases cloud storage and on-site data consumption due to continuous high-quality video streaming. Both continuous recording and timelapse recording will maintain high quality. Dual Camera Configuration One camera copy is configured for sub stream use at a lower resolution, while the second copy streams at 4K. This approach reduces on-site data consumption but ensures that the highest possible image quality is available for the timelapse without interrupting other platform features. Reconfigured Single Camera at 4K The camera is reconfigured to stream in 4K for the timelapse, but continuous recording and live streaming are disabled. This reduces on-site data usage but limits other platform features, as there will be no active live stream. To achieve the best results, the following guidelines should be followed: Select a high-quality camera that can withstand the entire project duration. Replacing a camera mid-project may cause a noticeable quality jump in the final timelapse and result in lost footage during the transition. Choose an optimal camera position to ensure consistent visibility of the project over time. Moving the camera during the project may result in a change of scene in the final video. Avoid placing the camera where bright light sources (such as the sun or artificial lights) will shine directly into it, as this can cause temporary blindness and produce a white image. Verify that the internet service provider can handle the required bandwidth for streaming and uploading timelapse footage. Set the timelapse parameters in the admin portal, including camera address, recording schedule, resolution, and duration. When configuring the timelapse, the following parameters must be specified: Camera ID Time of day to record Days of the week to record Resolution Duration of video per day 1. The recording schedule for the timelapse can be set to the following options: 24/7 24 hours a day, Monday through Friday Sunrise to sunset, 7 days a week Sunrise to sunset, Monday through Friday 2. Resolution Two streams can be used from the same camera. The primary stream is set to a lower resolution for regular monitoring, while the second, higher-resolution stream is used solely for the timelapse. This reduces network load, as the high-resolution stream is only active when capturing images for the timelapse. 3. Duration of Video per Day The daily video duration refers to how many seconds of footage will be compressed into a single day. Available options for daily video length are 2, 4, 6, 8, or 10 seconds. To calculate the optimal duration for a project, use the following formula: Where: D is the daily duration in seconds L is the desired length of the final movie in minutes P is the number of days the project will last Example Timelapse Setup For a project lasting 300 days, with the goal of producing a 10-minute final timelapse, the parameters would look like this: Camera ID: 00000 Time of day to record: Sunrise to sunset Days of the week to record: Every day Resolution: 4K Duration of video per day: 2 seconds In this setup, the final video will have 48 frames (2 seconds * 24 frames/second) per day. If the recording schedule is 24/7, one frame will be captured every 30 minutes. Note: To conserve bandwidth after setting up the long-term timelapse, consider disabling the camera through the admin portal. This will not affect the ongoing timelapse recording or subsequent viewing. To access the timelapse, navigate to the Cameras menu in the video portal, filter by "Offline," open the offline stream, and click the timelapse button.

Introduction Transforming cameras into intelligent devices capable of recognizing license plates on passing vehicles is made possible with the License Plate Recognition (LPR) feature. This technology processes video streams to identify license plates, storing the data in a database. The information includes the time and date of recognition, license plate number, confidence level, camera ID, and links to corresponding video archive files. This allows for efficient review and access to specific footage via a user-friendly portal. Proper camera placement, configuration, and event detection are essential to ensure reliable LPR performance. Different camera modules can be used to generate events, with the optimal detection method (such as motion detection, line crossing, or intrusion) depending on the scene conditions and camera positioning. NOTE1: Object detection for vehicle detection must be enabled for LPR functionality to work. NOTE2: The license plate must be visible for at least one second for recognition to occur. Plates on fast-moving vehicles may not be captured. Requirements and Recommendations Step 1: Camera Selection Most modern cameras can be used for LPR, but the best results are achieved with models that allow for manual or semi-automatic control over image settings, including shutter speed, frame rate, and bit rate. Additionally, selecting the appropriate lens and resolution is crucial. The license plate must have a minimum width of 100 pixels for recognition. For instance, a 720p camera can work with a narrow lens, while a 4K fisheye camera positioned 15 meters away may not provide enough clarity. Step 2: Camera Placement Considerations To achieve optimal license plate recognition, cameras should be positioned at locations where vehicles pass directly in front, such as at entrance checkpoints or driveways. The camera should be placed at road level or slightly above the typical height of a car, ensuring that vehicles pass toward or away from the lens for a brief but direct engagement. In areas where a front license plate is not required, the camera should be positioned to capture the vehicle's rear. This positioning maximizes the chances of obtaining clear, readable license plate images. Step 3: Lighting Considerations Proper illumination of the license plate is essential for effective recognition. Avoid direct sunlight on the plate or scenes with high contrast, such as indoors near large windows or in areas with changing light conditions, such as garages with automatic lighting. Uniform, consistent lighting is needed for reliable LPR. Avoid bright spotlights, which can create harsh shadows. Diffused, soft light sources are preferred. If the camera is positioned against a light source (e.g., sunlight behind the entrance), adjust the camera exposure to ensure the plate is illuminated and readable, even if it results in background overexposure. Be cautious with camera features like WDR, Backlight Compensation, or Highlight Compensation, as these can lead to blurry frames. Sharp, though sometimes underexposed, images are better than evenly lit but blurry plates. Step 4: Camera Setup To ensure reliable license plate recognition, the camera resolution and lens must allow the plate to be at least 100 pixels wide when passing under the camera. A width of 150+ pixels is ideal for better accuracy. For low-resolution cameras, vehicles must pass closer to the camera, or a zoom lens should be used. The recommended frame rate for slow-moving vehicles is between 8 and 15 frames per second (fps), but for high-speed roads, the frame rate should be adjusted to capture the license plate on at least five frames. The camera must have adjustable exposure settings to avoid blurred images of passing vehicles. The minimum shutter speed should be no slower than 1/100 second, with 1/150 second or faster being preferable. Prioritize shutter speed over aperture to avoid blurry images; in some cameras, this is managed through sharpness or smoothness settings. Cameras lacking exposure control will result in blurry images, which may appear acceptable during motion but will decrease the accuracy of license plate recognition. Ensuring sharpness without excessive visual noise can prevent false motion detections and improve LPR performance. Better illumination at the camera’s location can help mitigate issues with sharpness and visual noise. Note: Using the H.264 codec with high compression or long keyframe intervals may cause a "tailing effect" in moving objects. To address this, adjust the camera's bitrate and reduce the keyframe interval.