# tnl > take a shortcut through the internet. tnl gives a public address to the services you run. Share access, connect an integration, or reach a device in another network. Visitor TLS ends in tnl on the publishing device. Explicitly public app services get separate worktree addresses; opt-in OAuth callbacks and webhook endpoints stay stable across worktrees. Reviewers can leave feedback on app previews, and developers and coding agents can follow it through the CLI. Private PostgreSQL, MySQL, HTTP, and opaque TCP services use managed TLS endpoints and authenticated connectors. OpenSSH keeps its own host-key and user authentication inside the opaque stream. Start integrated apps with their normal command and an explicit local publicURL block (public_url in YAML/JSON). Git is optional for local publishing; apply requires a Git source identity. Named publisher groups use managed hostnames and allocated ports even for HTTP: the group's domain/public settings control exposure, with no service hostname/domain or anonymous override. Host-side Compose/Docker discovery needs an exact tnl.worktree label and a published host TCP port; an address target using an explicitly published loopback port avoids those discovery requirements. Authorization continues through HTTP bodies, WebSockets, and database/TCP streams. Rechecks are bounded to 30 seconds while control is available; an outage cannot extend the last accepted deadline. A replacement login/session cannot take over an original stream. Failed HTTP or SQL is never replayed. Node MySQL uses mysql2 with its managed hostname, verifyIdentity and loopback stream factory kept together; libpq disables channel binding across the separate TLS hops while retaining full TLS verification. Native OTLP export is http/protobuf only; JSON support belongs to the website JS exporters and receiver. Start with the quickstart. Read how it works for the visitor path and security for the trust boundaries. The docs links point to Markdown versions of the public pages. ## start - [start](/docs.md): Install tnl and publish a local app. - [install tnl skill](/skills/install-tnl/SKILL.md): Follow a short assistant workflow for installing tnl with `tnl init`. - [how it works](/docs/how-it-works.md): Follow a visitor from its public url to the local app. - [security](/docs/security.md): Encryption, visitor access, credentials, and operator trust. ## use tnl - [development](/docs/development.md): Start apps normally across worktrees and choose visitor access. - [webhooks](/docs/webhooks.md): Register stable project URLs with webhook providers and verify deliveries. - [publish](/docs/publish.md): Publish an app that is already running. - [private services](/docs/private-services.md): Connect native HTTP, database, Kubernetes, and OpenSSH clients through remembered loopback endpoints. - [service access](/docs/service-access.md): Invite a verified email to one service until a deadline, inspect current access, and revoke it. - [workloads](/docs/workloads.md): Prerelease policies for GitHub Actions, Vercel, Fly, and generic OIDC, with exact workload names and generated manifests. - [serverless http](/docs/serverless-http.md): Prerelease native connections from provider-authenticated Node functions, with application-owned HTTP credentials and runtime qualification gates. - [project configuration](/docs/configuration.md): Configure services and project defaults. - [frameworks](/docs/frameworks.md): Register a framework or API server's actual listener with local tnl. - [vite](/docs/vite.md): Vite integration. - [next.js](/docs/next.md): Next.js integration. - [teams](/docs/teams.md): Memberships, invitations, and shared public urls. - [company connections](/docs/company-connections.md): Connect company directories and manage member admission. - [domains](/docs/domains.md): Managed namespaces and claimed domains. ## operate - [installed publishers](/docs/installed-publishers.md): Prerelease Ubuntu/systemd and Compose installation with scoped publisher identity and persistent state. - [self-hosting](/docs/self-hosting.md): Deploy standalone or split tnld with PostgreSQL. - [publisher groups](/docs/publisher-groups.md): Apply desired configuration and operate independently provisioned replicas. - [aws publishers](/docs/aws-publishers.md): Run publishers in your AWS network using your own infrastructure tools. - [operations](/docs/operations.md): Readiness, maintenance, backups, and upgrades. ## reference - [config reference](/docs/config-reference.md): Project fields, formats, and precedence. - [tnl commands](/docs/cli.md): Client commands, flags, and output. - [tnld reference](/docs/tnld.md): Server roles and process settings. - [automation](/docs/automation.md): JSON, NDJSON, and diagnostics. - [releases](/docs/releases.md): Install and verify release artifacts. ## legal - [privacy](/privacy.md): Personal data, cookies, browser storage, and privacy rights. - [terms](/terms.md): Hosted-service terms for business users. - [acceptable use](/acceptable-use.md): Prohibited activity, abuse reports, and review requests. - [providers](/providers.md): Providers that help run tnl.dev. ## optional - [landing page](/index.md): Short product overview.