Skip to main content

FAQ

Is Larktun SaaS or private deployment?​

Larktun is a SaaS service. You can start directly with free shared relay, then use dedicated or user-managed relay only when needed.

What is the relationship between Larktun, Tailscale, and Headscale?​

Larktun is built on top of the work made possible by Tailscale and Headscale. We are deeply grateful for these open-source projects and community practices. Without their foundations in WireGuard-based networking, device identity, control-plane protocols, and node management, Larktun would not have the technical starting point it has today.

At the same time, Larktun is not just a thin rebrand or wrapper around Tailscale and Headscale. To better serve individual users, developers, and teams in China, we have done substantial engineering and product work on top of the original foundation:

  • We added device aliases and Chinese device-name display. This is not only a console UI change; it also requires changes on both the Tailscale client side and the Headscale control-plane side.
  • We transformed Headscale toward a SaaS model, including multi-tenancy, multiple networks, tenant isolation, independent policies, and related management flows. This involves major changes to the control-plane model, data boundaries, permissions, and operations.
  • We independently developed the iOS app, including an in-app networking mode that does not require system VPN permission. We also improved the Android app and open-sourced it so community users can review, use, and contribute to it.
  • We independently built the SaaS console, turning account, device, ACL, route, relay, and network management capabilities into a product experience suitable for everyday use.

The relationship can be understood this way: Tailscale provides mature networking ideas and a client ecosystem, Headscale provides an important open-source control-plane foundation, and Larktun continues from there with localization, SaaS productization, mobile experience, and access-governance capabilities.

Larktun respects and appreciates the upstream open-source projects. We will keep building on this foundation while adding capabilities that are especially useful for China’s network environment, remote work, safe AI Agent usage, and device access management.

Do I need to manually select free relay?​

No. Free shared relay is enabled by default for all users. You only need Derper changes for dedicated or user-managed relay.

Can tenants see each other's devices?​

No. Each tenant is an isolated network with separate device inventory, policy, and logs.

Is ACL shared globally?​

No. ACL is configured and enforced per tenant.

Can individuals use Larktun for personal NAS and dev workstations?​

Yes. Personal NAS, home devices, and personal dev workstation access are common use cases.

Can I run my own relay servers?​

Yes. User-managed relay is supported for region, performance, or compliance-specific requirements.

What is the easiest way to set up ACL for the first time?​

Use least scope first: one account (or one group), one target device, one protocol/port. Validate success, then expand gradually.

Why do I still fail even when device is online?​

Most often, subject, target, or port does not match in ACL. Check ACLs first. If subnet resources are involved, also check Routers.

Does the client interrupt endpoint users?​

The default target is a low-memory, background runtime designed to stay non-intrusive.

Why can cross-region sessions still be unstable sometimes?​

Typical causes include network jitter, relay load, or destination-side resource pressure. Start with default free relay checks, then move to dedicated or user-managed relay when optimization is needed.

What benefits do free users get?​

Device Quota​

Free users start with 5 devices by default. Each successful invite — where the invited user completes phone-registered signup — adds one more device to your free quota, up to a maximum of 10 devices.

Access Speed​

Inter-device access has no traffic limits and no speed caps. The actual speed you experience depends on the connection path:

  • P2P direct connection: Speed is determined by the bandwidth of both sides. A higher upload bandwidth on your end means a better connection.
  • Relay server: If a direct connection cannot be established, traffic automatically routes through a relay server. In this case, speed depends on the relay server's bandwidth and how many users are sharing it at the same time. Free users share relay resources, so speed may be limited during peak usage. For consistently faster performance, consider upgrading to a paid plan or using a dedicated relay.