TrueStack is a device-based VPN, which means we secure and trust computers directly — not users, usernames, or passwords.

Everything begins in the Computers tab.

Quick note before we start:
This walkthrough assumes your Network Routes are already created in the Network tab.
Network Routes define which servers or subnets computers are allowed to access.
We’ll focus here on adding and connecting the computer itself.

Step 1: Add a Computer

From the TrueStack interface, go to Computers and click Add Computer.

Give the computer a name.
This can be a hostname, asset tag, or anything meaningful to you.

You’ll also see an option for Group.

Groups are used only for organization.
They don’t affect security or how the VPN works.

You might group computers by company, location, or department — whatever makes management easiest.

You can add new Groups on the left panel.

Step 2: Assign Network Routes (Important)

Next, select the Network Routes for the computer.

Network routes are created on the Network tab and define what traffic is allowed to go through the VPN tunnel.

When adding a route, you can specify:

  • A single server IP, if the computer only needs access to a specific system
  • Or a CIDR subnet, if access to an entire network is required

If the server you are adding is a DNS server, such as an Active Directory domain controller, make sure to check the DNS Server checkbox.

If the server is a WINS server, which is very rare in modern environments, check the WINS Server checkbox.

Only the routes selected here are eligible to use the VPN.

Now this part is important, because the VPN behavior depends on two things:

  • Whether any network routes are selected
  • And whether Route all traffic is enabled

There are three possible outcomes.

Option 1: Access Specific Servers Only (Split Tunnel — Most Common)

If you select one or more network routes and leave Route all traffic unchecked:

  • Traffic to those servers goes through the VPN
  • Internet traffic continues to use the computer’s normal network connection

This is classic split tunneling, and it’s the most common setup.

Option 2: Route Everything Through the VPN (Full Tunnel)

If you enable Route all traffic, all traffic is sent through the VPN tunnel.

This includes two common use cases.

Full access use case

  • If network routes are selected:
    • Server traffic routes to those networks
    • Internet traffic exits from the TrueStack server

Internet-only use case

  • If no network routes are selected:
    • All internet traffic is encrypted and routed through the VPN
    • Traffic between the device and the TrueStack server is hidden, including traffic on public or untrusted Wi-Fi
    • Websites see the public IP of the TrueStack server, not the user’s local network
    • The computer appears to be browsing from the location of the TrueStack server, for example an Azure or AWS data center, rather than the user’s physical location
    • No internal servers or cloud networks are accessible

This configuration is similar to how consumer VPNs are typically used — to hide internet traffic and mask location — with the difference that you control the server and the infrastructure.

Option 3: No VPN Traffic at All (Usually Not Intended)

If you do not select any network routes and do not enable Route all traffic:

  • No traffic uses the VPN tunnel
  • Internet traffic behaves as if the VPN were not installed
  • The VPN connection is active, but it carries no traffic

This setup is valid, but usually indicates something was missed.

Step 3: Create the Computer

Once everything is selected, save the computer.

At this point, the computer exists in TrueStack, but it’s not connected yet.

Step 4: Get the Security Code

Each computer has a unique Security Code.

Click the security code icon to reveal it.

This code is used one time, during installation, to authenticate the agent.

You can copy it manually or email it directly to the user from the interface.

Step 5: Download or Self-Install the Agent

You can download the TrueStack Agent yourself from the Download TrueStack Agent menu and install it locally.

Or, for remote users, click Self-Install and send the installation link to the user.

Step 6: Install the Agent

After downloading the agent, the user runs the installer and follows the setup wizard.

Installation requires administrator privileges, because the agent installs network components and configures routing and DNS.

The agent can be installed either:

  • Manually by a local administrator, or
  • Automatically through Group Policy or other centralized deployment tools

No usernames or passwords are required during installation.

Step 7: Connect the Agent to Your TrueStack Server

After the agent is installed, a web browser automatically opens to complete the connection.

At this screen, the user must enter:

  • The TrueStack Server URL, provided by the administrator
  • The Security Code for this specific computer

Once both values are entered, the user clicks Connect.

The agent authenticates, establishes the VPN tunnel, and completes setup automatically.

What Happens After Connection

After a successful connection:

  • The browser window can be closed
  • The agent runs silently in the background
  • Network routes and DNS settings are applied
  • The computer appears as connected in the admin portal

There is no VPN app to open and no connect button for the user.

The VPN is always on.

Summary

  • Ensure network routes exist if needed
  • Add the computer
  • Choose routing behavior
  • Install the agent
  • Enter the server URL and security code

From there, TrueStack handles everything automatically.

That’s how TrueStack delivers secure, device-based connectivity — without passwords, without user interaction, and without VPN support tickets.

How to add computers and connect them to the TrueStack VPN.