LARUS handles
Identity continuity, renewal, rDNS workflow, Identity Passport, provider change, and the customer continuity record.
Support
Support
Support for identity records, delivery, and documented access.
Identify whether you need LARUS identity support or local delivery support before a deployment, provider change, renewal, rDNS request, allowlist onboarding, or reputation escalation.
Support split
LARUS manages identity records. Delivery partners handle local service
Delivery Partner handles
Installation, broadband, DIA, SASE, local routing, on-site work, and local service operations.
Deployment prerequisites
What should be ready before activation
Selected Identity Location
Confirm the home, office, certified venue, API edge, or enterprise site where the Identity Unit will be deployed.
Delivery path
Choose a Certified Partner, request existing provider review, or use a managed LARUS One delivery path.
Customer controls
Firewall, SASE, device posture, access policy, secrets, application authorization, and endpoint security remain customer-controlled.
Operational requests
Common support workflows and ownership
Provider change process
A provider or deployment Location change requires a new technical and delivery assessment. LARUS can retain the account record when approved, but cannot guarantee the same address activation, delivery design, or third-party treatment.
Renewal process
Renewal keeps subscription and account records current while the approved delivery and allocation remain active; renewal alone does not guarantee delivery or address continuity.
rDNS changes
Customers request reverse DNS updates through the operational workflow; LARUS reviews and records approved names.
Allowlist onboarding
Use Identity Passport and Allowlist Pack evidence when asking banks, clients, suppliers, API providers, or security teams to review an Identity Address. Recognition and allowlisting remain each third party's decision.
Abuse and reputation handling
LARUS can review the Identity Unit record and coordinate identity-side evidence, but cannot guarantee third-party reputation or acceptance. The customer remains responsible for endpoint behavior and application security.
Escalation path
Start in the client portal with the Identity Unit, deployment, partner, and affected Identity Address. Delivery issues route to the selected provider; identity continuity issues route to LARUS.
Response expectations
Critical identity continuity issues should include affected Identity Addresses, timestamps, destination systems, partner ticket numbers, and business impact.
Public support contact
Contact LARUS One support without signing in
Email support@larus.net for account access, billing, identity records, rDNS, or service escalation. Include your account email and affected Identity Unit reference when available.