Flux Platform Terms
Flux Platform Terms
Effective Date: June 10, 2026 · Version: 2.1
These Flux Platform Terms (“Terms”) govern use of the Flux platform (“Platform”), operated by Socium IT LLC, a Georgia limited liability company doing business as “Vigilis” (“Vigilis”). By creating an account, clicking to accept, or using the Platform, the accepting person or entity (“Customer”) agrees to these Terms and represents authority to bind its organization. If Customer has an executed Vigilis Services Master Services Agreement, that agreement governs Platform access provided under it.
1. The Platform
1.1 Service. Flux is a SaaS platform for automated management of Customer’s carrier services via supported carrier APIs — service orders and modifications, scheduled bandwidth changes, self-service changes, and, where enabled, utilization-triggered bandwidth scaling via SNMPv3 monitoring subject to Customer-configured thresholds, cooldowns, and guardrails (“Auto-Flux”). Currently supported: Lumen NaaS Internet on Demand and Ethernet on Demand; the current list is published in the Platform. Flux is not affiliated with or endorsed by Lumen Technologies or any other carrier.
1.2 License. Vigilis grants Customer a limited, non-exclusive, non-transferable, non-sublicensable license to use the Platform during the subscription, solely for Customer’s internal business operations. Vigilis retains all right, title, and interest in the Platform and related intellectual property.
1.3 Users. Customer may designate users as Viewer (read-only), Operator (changes within guardrails), or Administrator (full configuration and user management). Customer is responsible for its account information, credential confidentiality, user designations and revocations, and all activity under its accounts, and will promptly report suspected unauthorized access.
2. Acceptable Use
Customer will not: use the Platform unlawfully; attempt unauthorized access; interfere with Platform integrity or performance; reverse engineer the Platform; transmit malicious code; or resell or redistribute access, except through sponsored accounts under a written Vigilis partner agreement (Section 4.3).
3. Automation and Carrier Charges
3.1 Authorization. Customer authorizes Vigilis and the Platform to submit service orders and modifications to supported carriers on Customer’s behalf via API, whether (a) scheduled, (b) initiated by Customer’s users, (c) initiated by Vigilis operations at Customer’s request, or (d) triggered by Auto-Flux within Customer-approved thresholds and guardrails.
3.2 Carrier Charges. Each submitted change is a binding service change with the carrier and may alter Customer’s recurring charges. Customer is solely responsible for all third-party charges resulting from authorized actions, including changes triggered automatically at any hour and charges resulting from configuration errors.
3.3 Configuration. Customer is responsible for the accuracy of all configurations (schedules, thresholds, tier limits, cooldowns, guardrails, user designations) and must approve schedule and threshold configurations before activation (via Platform or email); changes executed per approved configurations are deemed authorized. Customer should verify business-critical changes in the carrier’s portal. Available guardrails include maximum tier, bandwidth ceiling/floor, daily change limits, approval thresholds, and cooldown periods; Vigilis is not responsible for charges resulting from guardrails Customer declines to enable or from changes within configured parameters.
3.4 Fair Use. Changes are subject to the carrier’s published API rate limits (Lumen NaaS: currently 24 changes per managed service per rolling 24 hours). Monitoring evaluations that produce no API submission do not count. Vigilis may throttle or queue submissions to stay within carrier limits and will notify Customer when usage approaches them.
3.5 Carrier Credentials. Customer-provided carrier credentials are confidential, stored encrypted (AES-256 or equivalent), and used only for authorized actions. Vigilis will notify Customer within 72 hours of known unauthorized access to them and deletes them within 30 days after termination. Customer is responsible for providing, rotating, and revoking credentials.
3.6 Monitoring. Auto-Flux requires Customer devices supporting SNMPv3 (authPriv) reachable from Vigilis’s monitoring infrastructure; Customer is responsible for SNMP and firewall configuration and for notifying Vigilis of network changes affecting monitoring. If monitoring data is unavailable, threshold-triggered changes do not execute. Vigilis is not responsible for monitoring gaps caused by Customer devices, third-party changes, or network conditions, or for performance impacts of standard polling.
3.7 Carrier Terms and APIs. Customer’s carrier services and APIs remain governed by Customer’s own carrier agreements; a Platform-submitted change does not expand the carrier’s obligations to Customer. Vigilis is not responsible for carrier API changes, outages, or errors, and resulting delays or failures are not a breach. If a carrier permanently discontinues an API and Vigilis cannot provide a substantially equivalent capability within 60 days, either party may remove the affected service (with fee adjustment) or Customer may cancel.
4. Fees and Billing
4.1 Fees. Fees are as stated at checkout per Vigilis’s published pricing (typically a monthly platform fee plus a monthly fee per managed service — a distinct carrier service actively configured in the Platform). Managed-service changes adjust fees the next billing cycle. Vigilis may change published pricing on 30 days’ notice, effective at Customer’s next billing cycle after the notice period.
4.2 Auto-Charge. Subscriptions are billed monthly in advance to the payment method on file with Vigilis’s payment processor. Customer authorizes recurring charges until cancellation and full payment, and will keep a valid payment method on file. If a charge fails and remains unpaid 10 days after notice, Vigilis may suspend access; suspension does not relieve accrued obligations.
4.3 Sponsored Accounts. Vigilis may provision access at no charge or a discount under a partner arrangement. These Terms apply in full to sponsored accounts. If sponsorship ends, Vigilis may transition the account to published pricing on 60 days’ notice; Customer may cancel at any time.
4.4 Chargebacks. Before any chargeback or payment reversal, Customer will contact Vigilis and attempt resolution in good faith for at least 15 days. A chargeback without doing so, or for amounts properly owed, is a material breach; Customer will reimburse resulting chargeback fees, processor fees, and reasonable attorneys’ fees.
4.5 Taxes; No Refunds. Fees exclude taxes, which are Customer’s responsibility (other than taxes on Vigilis’s income). Fees are non-refundable except as required by law.
5. Term and Termination
The subscription is month-to-month. Customer may cancel anytime, effective at the end of the current billing cycle. Vigilis may suspend or terminate for material breach (including non-payment and acceptable-use violations) or as required by law or carrier requirements, with notice and opportunity to cure where practicable. Upon termination: access is revoked and automation deactivated; Customer remains responsible for accrued amounts and carrier charges from pre-termination changes; carrier credentials and monitoring data are deleted within 30 days; and data export and retention follow Section 6. Sections 3.2, 3.7, and 6–11 survive.
6. Customer Data
6.1 Ownership. Customer owns all data provided to or generated through the Platform on its behalf (“Customer Data”) and grants Vigilis a license to process it solely to provide the Platform and comply with law.
6.2 Security. Vigilis maintains commercially reasonable security — encryption in transit (TLS 1.2+) and at rest (AES-256 or equivalent), role-based access controls, and incident response — and will notify Customer within 72 hours of a security incident involving Customer Data.
6.3 Audit Logs. Service change operations are logged (timestamp, service, parameters, trigger type, acting user for self-service, utilization data for Auto-Flux, status, and errors) and accessible to Customer Administrators in the Platform.
6.4 Export and Retention. On request within 30 days after termination, Vigilis will export Platform data in a standard machine-readable format (e.g., CSV/JSON). Monitoring data is deleted within 30 days after termination; other Customer Data and audit records are retained 12 months post-termination, then securely deleted, unless law requires longer.
6.5 Aggregated Data; Personal Data. Vigilis may use aggregated, anonymized Platform data that identifies no customer or individual for benchmarking, product improvement, and marketing. Where Customer Data includes personal data, Vigilis’s Data Processing Addendum applies upon mutual execution (request via Section 13).
7. Disclaimers
Vigilis warrants the Platform is provided in a professional manner consistent with industry standards. OTHERWISE THE PLATFORM IS PROVIDED “AS IS” AND “AS AVAILABLE”; VIGILIS DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, UNINTERRUPTED OPERATION, AND ANY PARTICULAR COST-SAVINGS OUTCOME.
8. Service Level Objectives
The following are targets, not credit-bearing commitments: platform uptime 99.5% monthly (excluding scheduled maintenance on 24 hours’ notice, carrier API outages, force majeure, and Customer-caused issues); scheduled changes processed within 30 minutes of scheduled time; self-service and monitoring-triggered changes submitted to the carrier API within 5 minutes; failure notification within 5 minutes via the configured channel; unplanned-downtime notification within 1 hour, with updates every 4 hours.
9. Limitation of Liability
9.1 Cap. Vigilis’s aggregate liability under these Terms will not exceed the greater of (a) Platform fees paid by Customer in the 12 months preceding the event, or (b) $2,500.
9.2 Exclusions. Carrier charges and other third-party amounts from authorized actions are Customer’s responsibility under Section 3.2 and are excluded from Vigilis’s liability regardless of configuration errors. Neither party is liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or lost profits, revenue, or savings. Nothing limits liability for gross negligence, willful misconduct, Customer’s payment obligations, or liability that cannot be limited by law.
10. Indemnification
Customer will indemnify, defend, and hold harmless Vigilis and its members, officers, employees, and agents from third-party claims arising from: carrier charges from authorized actions; Customer-provided carrier credentials; Customer’s breach of these Terms or violation of law; and actions of Customer’s users.
11. Governing Law; Disputes
Georgia law governs, without regard to conflict-of-laws principles. Disputes are resolved by binding AAA arbitration (Commercial Rules) in Atlanta, Georgia, before a single arbitrator; judgment may be entered in any court of competent jurisdiction. Either party may seek equitable relief in Fulton County, Georgia courts to protect intellectual property, confidential information, or payment obligations.
12. Changes to These Terms
The current version is always posted at this page with its version and effective date. Updates take effect immediately for new subscriptions and, for existing subscriptions, at Customer’s first billing cycle beginning at least 30 days after posting — each renewal constitutes acceptance of the then-posted Terms. Vigilis may, but need not, provide additional notice. Customer’s remedy for an unacceptable update is cancellation before it takes effect. Pricing changes are governed by Section 4.1.
13. Notices; Assignment; General
Legal notices to Vigilis: comms@vigilis.io; to Customer: the account email on file. Email notice is effective when sent absent delivery failure.
Vigilis may assign these Terms at its sole discretion — including to a successor, affiliate, or third party in connection with a merger, acquisition, sale of assets or equity, reorganization, spin-off, or other change of control — without Customer consent or notice as a condition to effectiveness, provided the assignee assumes Vigilis’s obligations. Customer may not assign without Vigilis’s prior written consent; violating assignments are void.
These Terms (with Customer’s order selections and any executed addenda) are the entire agreement for Platform access and supersede the previously posted Master Services Agreement, Terms of Service, and Addendum F at fluxiod.com. The parties are independent contractors; there are no third-party beneficiaries; unenforceable provisions are severed; waivers must be written; neither party is liable for delay (other than payment) due to causes beyond its reasonable control.
Socium IT LLC dba Vigilis · 8735 Dunwoody Pl, #5746, Atlanta, GA 30350