Hangar turns a server in your building into desktops for AI agents. They work in your ERP, your warehouse system and the industry software nobody wrote an API for, next to your data and behind your firewall.
Most office work still happens in programs with no API: the ERP, the warehouse system, the clinic calendar, a supplier portal. Hangar gives AI agents their own Windows desktops on your server, so they do that work the way a person does, with screen, keyboard and mouse. No API and no integration project.
Appto, Claude, ChatGPT, your automation tool or your own code.
A Windows desktop of its own, on your server. Point at a square to watch one.
The same programs your team uses, as they are today.
If a person can do it on screen, the agent can too. Old ERPs, warehouse systems, green-screen terminals and web portals without an API all work as they are, with nothing to change on your side.
Companies whose daily work still runs in desktop programs, the teams who hand that work over, and the people who build automations for them.
An example day. Scroll to run it: each task takes its turn on screen, each square is a desktop busy for ten minutes, and the list counts what is done.
Your team asks in Appto, Claude or ChatGPT, or an automation tool sends the task. It crosses your firewall, an agent does the work on a desktop inside your network, and the result goes back.
The same steps every time, whether the task comes from a chat, a schedule or your own code.
From Appto, Claude, ChatGPT, an automation tool or your code.
A fresh copy of your setup starts on your server.
Screen, keyboard and mouse, the way your team does it.
The result goes to whoever sent the task.
The desktop can go back to a clean copy, so nothing carries over. You choose per task.
Every click and a video of the session, on your server.
Install Hangar on a server in your building, set up one desktop with the programs your team uses, and hand over one process. Add the next when it runs well.
npx hangar upSet it up once, like a computer for a new colleague: the programs, the logins, the shared folders. Every task starts from a clean copy of it.
The ERP, Excel, the VPN and the browser your team uses, open the moment the desktop starts.
Copy between programs, open attachments, save exports to a shared folder on your network.
Windows or Linux, with a screen, keyboard and mouse the agent uses the way a person would.
The agent uses saved sessions and never sees the passwords.
When the task ends the desktop goes back to your setup. Nothing carries over to the next one.
Video and a click-by-click log of each session, kept on your server.
Every step an agent takes is written down and recorded, and everything it works with stays on your servers. Here is how it is kept safe.
We will show you an agent doing it on a desktop on your own server, in the program you use today.
RPA scripts and integration projects work while nothing changes. Old programs change all the time: a moved button, a new dialog, an invoice that looks different.
And an integration project? It needs an API in the program, or developers to build one. An agent works with the program as it is today.
Short answers for operations, finance, IT and security.
No. The agent works through the screen, keyboard and mouse, the same way your team does. If a person can do it in the program, the agent can too.
As many as your hardware holds. Most teams start with one process on one server and add desktops when they hand over more work.
Appto, Claude and ChatGPT connect as a tool. n8n, Make, Zapier, Power Automate, UiPath and your own code send tasks through the API or MCP.
An RPA script repeats recorded clicks and usually breaks when the screen changes. The agent looks at the screen each time and decides what to do, so a moved button does not stop it, and it leaves unclear cases for a person.
On hardware you control: your own servers, a VM in your cloud account or a single workstation. We do not host your desktops.
Sessions are saved in the desktop setup or in your vault. The agent can use them but cannot read the passwords.
The desktop goes back to a clean copy and is free for the next task. The recording and the log stay on your server.