Home / Product overview
PRODUCTForceLink in three parts.
No deep networking knowledge required. ForceLink is built on just three elements. The complex initial build is handled by Forcenet — you place the BOX and distribute invitation codes.
ForceLink BOX
A palm-sized device you place in the office. It becomes the secure gateway into your internal network. Forcenet pre-configures it before shipping — you just place it and connect it to the LAN.
The small box that sits in your officeCloud relay
A secure relay point on the internet. Each company gets a dedicated relay — traffic from other tenants does not mix with yours. Staff connect to their company's ForceLink BOX through this relay. The relay is operated in a domestic (Japan) data center.
Provisioned and operated by ForcenetDedicated app
Enter an invitation code and setup is complete. Your private key is generated inside this PC and never leaves it — only the public key is sent to the cloud.
Staff's Windows PC (standard)The product interface is currently Japanese-first.
From a staff member's PC to the office LAN.
The VPN segment from the staff member's PC to the ForceLink BOX is encrypted. The contents cannot be read in transit over the internet.
Communication inside the office LAN depends on each system's own protocol. Encrypting the VPN segment (staff PC ↔ ForceLink BOX) is ForceLink's role.
Limiting reach after connection.
Even after a VPN connection is established, the entire office LAN is not exposed. The ForceLink BOX enforces which internal PCs, servers, and NAS each user is allowed to reach. By narrowing down the destinations reachable after connection, the design helps contain the lateral movement risk in the event of a compromise.
* Illustrative diagram. Rather than opening the full LAN, only the necessary connections are permitted on the ForceLink BOX side (the full office LAN is not opened).
Per-user allowances
Control who can reach which internal resources. Scope can be divided by department or role.
Destination and port-level control
RDP endpoints, NAS (file shares), business servers, web admin interfaces — access can be configured in operationally meaningful units.
Enforced by the ForceLink BOX
Permissions are enforced on the ForceLink BOX in the office. They do not depend solely on client-side configuration changes.
Control is at the destination IP, port, and protocol level — application names are not auto-identified. ForceLink does not claim to be a complete zero-trust solution. This feature is designed to narrow the reachable scope after connection and help contain lateral movement risk.See the security approach →
Who does what.
Enter an invitation code in the app and connect. No technical knowledge needed.
Invite and deactivate staff from the web console. Monitor connection status.
Handles the initial build and cloud operations. The complex parts are left to us.
Plain-language definitions.
A mechanism for connecting securely to the office network from a remote location.
The internal company network — file servers, business systems, and so on.
A one-time, time-limited registration code that staff enter in the app.
The small device placed in the office that serves as the secure gateway into the internal network.
Frequently asked questions about how it works.
What arrives, and what do we need to do?
A pre-configured ForceLink BOX is shipped to you. Your team's job is three steps: place the BOX, distribute invitation codes, and connect via the dedicated app. Forcenet handles cloud provisioning and the initial build in advance.
Do we need to change our existing router or network?
In most cases, no. You connect the ForceLink BOX to your office LAN, and your existing router and network configuration can remain largely unchanged.
Does the private key ever leave the device?
With the standard dedicated Windows app, the private key is generated inside the device and never leaves it. Only the public key is sent to the cloud. The tunnel is not opened with a password.
Which operating systems are supported? What about multi-factor authentication (MFA)?
The standard client is the dedicated Windows app. Mac, iPhone, and Android can be supported on a case-by-case basis. MFA is not currently supported; support is under consideration. Connections are key-based.
That's how it works. Talk to us about the rest.
Even at the "would this work for our network?" stage, feel free to reach out. Security design consultations are available at no charge.