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.
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.
- 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").
- Get the link. Anping answers with a one-time link. Your app puts Anping's address in front of it.
- 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.
- 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 runs | On 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. |
|---|---|
| Sizing | About 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 compatibility | The 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 to | Windows Remote Desktop (RDP): the full desktop, or one program that opens at sign-in. |
| Security | Remote 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 MFA | Anping 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. |
| Printing | Prints to a PDF that downloads. Off by default: it needs a desktop engine with Ghostscript (AGPL-3, or a commercial license from Artifex). |
| Browsers | Chrome, Firefox, Safari, phones and tablets (Edge not yet tested on its own). |
| Log | One entry per session: who, which computer, when, how long and how it ended, downloadable as JSON or CSV. |
| Core components | guacd 1.6.0 from Apache Guacamole, in Anping's own build with FreeRDP 3. |
Features
What using it is like
- DesktopA whole Windows desktop, one program that starts when you sign in, or a single program window. It fits the browser window or keeps a fixed size.Not yet: virtual machines (Hyper-V), Remote Desktop server farms (Connection Broker) and single program windows (RemoteApp) are built in but not yet tried on real servers.
- One-time linksSomeone else who gets the same link cannot open it. The same requests as Thinfinity's one-time links, with every documented option (what each one does).Not yet: user accounts: your app decides who gets a link. A link opens only on the Anping server that made it, and restarting that server forgets it (deploying).
- ReconnectIf the network drops, the page reconnects by itself for up to a minute. Reloading, or opening it again in the same browser, picks the session up. End closes the session and its link for good.
- TouchTap to click, double tap, press and hold for a right click, drag, and scroll with two fingers. A tap brings up the on-screen keyboard.Not yet: pinch to zoom, scrolling sideways, using the screen like a trackpad.
- FilesPaste copied files with Ctrl+V and they land where you paste on the remote, such as the desktop or an open folder. Each session also has its own shared folder: drag or upload files there (up to 100 MB each by default). Files you save there come to your browser by themselves. The folder is deleted when the session ends.Not yet: dropping files straight into any Windows folder; copying files on the remote to your computer (in progress).
- ClipboardCopy and paste text both ways. Chrome and Edge do it by themselves after you allow it once; in Firefox and Safari, use paste or the Clipboard panel.
- KeysCtrl+Alt+Del, the Windows key and Alt+Tab are in the toolbar; in full screen those keys simply work. On a Mac, Cmd shortcuts work like Ctrl.
- Typing other languagesType Chinese and other languages with your own computer's input method, or with the remote computer's own (Windows IME).
- Sound and printingThe remote computer's sound plays after your first click, in four quality levels. Printing makes a PDF that downloads; it is off by default (see Printing in the specs).Not yet: sound from Windows Server 2025, which sends it on a channel the desktop engine doesn't have yet; microphone.
- Time zoneThe page sends your time zone, so the remote computer can show your local time if a Windows setting allows it (Windows computers).Not yet: Windows Server 2025 keeps world time (UTC) even with that setting on; summer time changes, since Windows only gets your current time difference.
- SecurityYour sign-in is checked before anything is shown, and the remote computer must prove who it is. Wrong passwords are limited, a link can never unlock more than the computer's setup allows, and sessions and shared folders have time and size limits.
- Connection logOne line per session: who, which computer, when, how long and how it ended. Read it as a page or download it (JSON, CSV).
- Your brandYour product's name, logo and colour in the toolbar and the browser tab. Without them the page shows no product name.
- BrowsersChrome, Edge, Firefox, Safari, phones and tablets.Not yet: Edge isn't tested on its own, and our newest automatic tests so far run only in Chrome's engine.
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
- 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
- Ask for a linkYour server sends the key, the user's name and the setup name to Anping in one request. How
- 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
- Quick startMake a link, open it, put it in your page.
- DeployingWhat you need, and how Anping runs.
- API referenceEvery option, answer and error.
- EmbeddingThe desktop inside your own web page.
- Migrating from ThinfinitySame requests, a new address, a dry run first.
- SamplesReady-made code in C#, Node.js and a web page.
- User helpFor users and the helpdesk.
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.