Anping 中文

Anping · a Thinfinity replacement

Open a remote Windows computer,
right in the browser.

Staff or customers click a link and use the company's Windows computer, or one program on it, in the browser. Nothing to install; it runs inside your own network and can replace Thinfinity.

This opens the contact form: tell us how you use Thinfinity today (how many computers, roughly how many users) and within one business day we reply with how to switch and what it costs.

Illustration

Thinfinity

Using Thinfinity today?

Anping takes the same one-time link requests as Thinfinity Workspace 8.5 and gives the same answers. Once Anping is set up with your computers and allows the ones your app asks for, your app switches by pointing at Anping's address instead, with no rewrite (Migrating from Thinfinity).

- https://thinfinity.yourcompany.com/ws/oturl/get?apikey=…
+ https://anping.yourcompany.com/ws/oturl/get?apikey=…

How it works

Computers and passwords stay inside your company

Users only get a link that works once. They never see where the computer is or get its password.

How a one-time link travels: 1 your app requests a link from the Anping server, 2 gets it back, 3 the user opens it in the browser, 4 Anping shows the Windows desktop there through its remote desktop service. The server, that service and Windows stay inside your company network. Inside your company network Your app keeps the secret key User's browser new tab or your page Anping server Remote desktop service Windows computer 1 Request a link 2 Get the link 3 Open the link 4 Show the desktop How a one-time link travels: 1 your app requests a link from the Anping server, 2 gets it back, 3 the user opens it in the browser, 4 Anping shows the Windows desktop there through its remote desktop service. The server, that service and Windows stay inside your company network. Your app keeps the secret key User's browser new tab or your page Inside your company network Anping server Remote desktop service Windows computer 1 Request a link 2 Get the link 3 4 Show the desktop
The browser never getsComputer names and addressesPasswords and settingsThe remote desktop service
  1. Request a link. Your app sends Anping its secret key, the user's name and which computer setup to use (Anping calls a computer with its settings a "model").
  2. Get the link. Anping answers with a one-time link. Your app puts Anping's address in front of it.
  3. Open the link. The user opens it in a new tab or inside your own web page. It works once: after that, only the same browser can reload or reconnect for a while; every other browser is turned away.
  4. Show the desktop. Anping hands the connection to its remote desktop service, which runs right next to it and can't be reached from outside. That service connects to the Windows computer and shows its screen in the browser.

Specs

Specs for IT

Where it runsOn your own servers or cloud, as Docker containers on a Linux host; connections never pass through us (Deploying). A one-command installer for a Linux host is in progress.
SizingAbout 0.15 vCPU and 170 MiB per open session at 1920x1080 for office work: a 4 vCPU / 8 GiB Linux VM holds about 18 sessions, 8 vCPU / 16 GiB about 37. Screens that change all the time (3D views, animation) need more, so measure one session with your own software first. Measured on a Mac with a Linux test desktop; to be measured again on the first real server.
Thinfinity compatibilityThe same requests and answers as one-time links in Thinfinity Workspace 8.5, with every option in its public documentation; the few that work differently are marked in the API reference.
What it connects toWindows Remote Desktop (RDP): the full desktop, or one program that opens at sign-in.
SecurityRemote computers must prove who they are (certificate or fingerprint) and Network Level Authentication is required by default; links work once; wrong passwords, session time and shared folders all have limits.
Sign-in and MFAAnping has no user accounts of its own: your system decides who gets a link, so your existing sign-in and multi-factor authentication carry over.
PrintingPrints to a PDF that downloads. Off by default: it needs a desktop engine with Ghostscript (AGPL-3, or a commercial license from Artifex).
BrowsersChrome, Firefox, Safari, phones and tablets (Edge not yet tested on its own).
LogOne entry per session: who, which computer, when, how long and how it ended, downloadable as JSON or CSV.
Core componentsguacd 1.6.0 from Apache Guacamole, in Anping's own build with FreeRDP 3.

Features

What using it is like

Still being verified:Tested with Windows Server 2025 and a Linux test desktop. Virtual machines (Hyper-V), connection brokers and single program windows (RemoteApp) are built in but not yet tried on real servers. On Windows Server 2025, sound and the time zone don't work yet. Not supported yet: microphone, pinch to zoom. In progress: the installer for a Linux host, and copying files from the remote to your computer.

Get started

Your first desktop

  1. Get accessAsk whoever runs Anping for its address, a secret key for your app and the name of a computer setup. What to ask for
  2. Ask for a linkYour server sends the key, the user's name and the setup name to Anping in one request. How
  3. Open itPut Anping's address in front of the answer and open it in a new tab or in your page. The desktop appears. Open

Documentation

Read on

Want to replace Thinfinity?

Tell us how you use it today. Within one business day we reply with how to switch and what it costs.

Contact us