> For the complete documentation index, see [llms.txt](https://docs.remote.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.remote.it/features.md).

# Features

- [Services](https://docs.remote.it/features/services.md): A Remote.It service maps an application, port and host address on a target device so you can reach it remotely. Learn the attributes of a service.
- [SSH](https://docs.remote.it/features/services/ssh.md): Connect over SSH to devices behind NAT, CGNAT or a firewall with no port forwarding — auto-launching Terminal, PuTTY or Termius from Remote.It.
- [RDP and VNC](https://docs.remote.it/features/services/rdp-and-vnc.md): Set up Remote.It RDP and VNC services to reach a remote desktop across NAT using the remote desktop clients you already use.
- [SMB and CIFS](https://docs.remote.it/features/services/smb-and-cifs.md): Reach SMB and CIFS network file shares remotely as if you were on the same LAN, by adding a Remote.It service to the device hosting the shared folders.
- [HTTP/S](https://docs.remote.it/features/services/http-s.md): Host a private website or API behind NAT and reach it through a Remote.It HTTP/S service pointed at the port your web server is listening on.
- [Database](https://docs.remote.it/features/services/database.md): Query remote databases securely over Remote.It — Microsoft SQL on port 1433 by default, or any database reachable on a TCP port via the service host address.
- [Redis](https://docs.remote.it/features/services/redis.md): Connect to a remote Redis instance on port 6379 through Remote.It, or any other cache service listening on a TCP port.
- [UDP](https://docs.remote.it/features/services/udp.md): Create a Remote.It UDP service on any port you need. There is no default service port for UDP — you specify the one your application listens on.
- [VPN](https://docs.remote.it/features/services/vpn.md): Register one or more VPN services on a device to reach multiple VPNs through Remote.It without constantly reconnecting and disconnecting.
- [Connection Options](https://docs.remote.it/features/connection-options.md): Ways to route a Remote.It connection — peer-to-peer, proxy, LAN sharing, and jump services that reach devices where Remote.It isn't installed.
- [LAN Sharing](https://docs.remote.it/features/connection-options/lan-sharing.md): Share a Remote.It peer-to-peer connection with others on your local network, scoped to a single LAN address or a range of IPs.
- [Jump Service](https://docs.remote.it/features/connection-options/jump-service.md): Use one device as a jump box to reach TCP services on other devices on the same LAN — printers, appliances or an AWS VPC — without installing Remote.It on each.
- [Peer-2-Peer & Proxy](https://docs.remote.it/features/connection-options/peer-2-peer-and-proxy.md): How Remote.It peer-to-peer and proxy connections differ, and when each routing method is used.
- [Logging](https://docs.remote.it/features/logging.md): Event logging in Remote.It — audit device, service and connection activity across your account.
- [Organizations](https://docs.remote.it/features/organizations.md): Create a Remote.It organization to share devices with your team, manage seat licenses and member roles, and integrate SAML single sign-on.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.remote.it/features.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.