DOCSEARCHbyAlgolia
Submit Docs

Latitude.sh Documentation

website·Indexed 35 days ago

https://www.latitude.sh/docs

Documentation for Latitude.sh, covering account security (MFA, Passkeys), account setup, and a comprehensive API reference for managing servers, virtual machines, VLANs, firewalls, elastic IPs, and storage volumes.

Tokens
67.9K
Snippets
346
Records
641
Agent score
72%

What's inside Latitude.sh

  1. Overview of Network Bonding on Latitude.sh

    Network bonding joins a server's two NICs into a single redundant bond0 link. This ensures the server remains connected if one link or switch port fails. A bonded server uses an IP address from a user-owned public network instead of a standard public IP. Bonding configuration is handled automatically by Latitude.sh OS images and does not require manual OS configuration. A public network is required to use this feature.

  2. Overview of Latitude.sh Firewall

    Latitude.sh Firewall provides centralized management of resource-level iptables rules across servers and virtual machines. Unlike perimeter network firewalls, it runs directly on each protected resource.

    Critical Requirement: The protected resource must run an operating system that supports UFW (Uncomplicated Firewall).

  3. Overview of the Latitude.sh API

    The Latitude.sh API provides programmatic access to all platform resources, allowing developers to build custom dashboards, integrations, and server management clients. The API includes built-in filtering and sorting capabilities to manage infrastructure efficiently.

  4. Overview of Latitude.sh Private Networking

    Private networking allows grouping servers within the same location to enable private communication. By default, servers use a Layer 3 topology; enabling private networking switches this to a Layer 2 topology, allowing L2 traffic between instances. This applies to both bare-metal servers and VMs. Traffic on private networks does not go through the public internet, does not count against bandwidth quotas, and is not filtered by Latitude.sh.

  5. Overview of Latitude.sh File storage

    File storage is a high-performance, persistent storage solution for bare metal servers on the Latitude.sh platform. It provides scalable storage that ensures data is retained across reboots, making it suitable for data-intensive applications and long-term data management. Note: File storage is currently in private preview.

  6. Overview of SAML Single Sign-On (SSO) in Latitude.sh

    SAML Single Sign-On (SSO) allows organizations to manage team members and control dashboard access through an external identity provider (IdP). Once SAML SSO is active, any user with an email address from a configured domain must authenticate via SAML SSO to access their account.

  7. Overview of LKS Clusters

    An LKS Cluster consists of a managed Kubernetes Control Plane (operated by Latitude.sh) and one or more Node Pools of bare metal Nodes. Users are responsible for managing the Cluster's Workloads and Node Pools. The Control Plane is fully managed; users do not size or access Control Plane Nodes, and no SSH keys are required for cluster creation.

  8. Overview of Latitude.sh Model Context Protocol (MCP) Server

    The Latitude.sh MCP server is a hosted remote server that allows AI agents and chat-based IDEs to manage Latitude.sh infrastructure (bare metal, networking, VMs, etc.) using natural language. Because it is hosted, most clients do not require local installation; they only need to point to the server URL.

  9. Overview of Latitude.sh Cloud Gateway

    Cloud Gateway provides a private, secure, and direct connection between Latitude.sh servers and major cloud providers. To initiate a connection, users must navigate to Interconnection > Cloud Gateway in the Latitude.sh dashboard, select a project, and submit a request with the required configuration details. Once submitted, the Latitude.sh team handles the final configurations.

  10. Overview of Out-of-Band (OOB) serial console access

    Out-of-Band (OOB) provides direct access to a server's hardware-level serial console over SSH. This allows interaction with the system during BIOS, GRUB, and early kernel output, and provides a way to administer Linux when standard SSH is unavailable. Note that OOB is a Serial-over-LAN console, meaning it has lower bandwidth, text-mode BIOS, and no graphical KVM output (use Remote Access for graphical needs).

  11. Overview of Latitude.sh Instance Metadata Service

    The Instance Metadata Service is a link-local HTTP API accessible only from within a running Latitude.sh bare metal server. It allows servers to query their own metadata (hostname, IP addresses, network config, storage, etc.) without external API credentials.

    Constraints:

    • It is NOT part of the main Latitude.sh REST API; regular API keys will not work.
    • It is currently NOT available in the SAO and SAN3 regions.

  12. Overview of BYOIP on Latitude.sh

    BYOIP (Bring Your Own IP) allows users to use their own publicly routable IPv4 address prefixes on Latitude.sh infrastructure instead of using Latitude.sh-assigned addresses. This is typically used to preserve IP reputation, meet regulatory compliance, maintain brand consistency, or facilitate workload migration without changing public-facing IPs.