ready-to-work computers for AI agents, on your own servers.

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.

Install it on your servernpx hangar up

your AI agent gets its own computer.

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.

1

The agent decides what to do

Appto, Claude, ChatGPT, your automation tool or your own code.

New task
2

Hangar gives it a desktop

A Windows desktop of its own, on your server. Point at a square to watch one.

Working0 Starting0 Free0
3

The work happens in your programs

The same programs your team uses, as they are today.

    it works in the programs you already have.

    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.

    One desktop, many programs
    Desktop 07Windows 10 with the ERP and Excelrecording 00:00

    Works with any Windows or Linux desktop program and any website. Product names are examples of the kind of software, not partnerships.

    who it's for.

    Companies whose daily work still runs in desktop programs, the teams who hand that work over, and the people who build automations for them.

    Companies

    Where the day runs in programs without an API

    • Wholesale and distribution
    • Logistics and transport
    • Manufacturing
    • Clinics and dental practices
    • Accounting and payroll offices
    • Insurance brokers
    • Staffing agencies
    Teams

    The people who hand over the repetitive part of their work

    • Operations and back office
    • Finance and accounting
    • Customer service
    • HR and payroll
    • ITkeeps control, it runs on your own servers
    Builders

    The people who build automations for others

    • Automation agencies
    • Integrators
    • Consultants
    • whose agents need to reach programs that have no API

    what agents take off your team in a day.

    An example day. Scroll to run it: each square is a desktop busy for ten minutes, and the list counts what is done.

    example day

    runs on your infrastructure. takes tasks from the tools you choose.

    Your team asks in Appto, Claude or ChatGPT, or your automation tool sends the task. The request crosses your firewall, an agent does the work on a desktop inside your network, and only the result goes back.

    Where the task comes from

    On your team's side

    Your infrastructure

    Desktop 07Windows 10 with the ERP and Excelrecording
    Hangaron your server
    • Your ERP and other programswhere the work happens
    • Files and shared folderskept on your own file server
    • Saved logins in your vaultthe agent never sees a password
    • Recordings and the logfor review and audit
    Your hardware or your own cloud accountA workstation under a desk, servers in your server room or a VM in your own cloud account.
    One agent, one desktopDesktops are kept apart from each other and from the rest of the network.
    Tasks in, results outThe tools that send tasks get the result back. They never get a way into the network.

    see every click the agent made.

    Activity log  live from this page0 events

    Each step is logged with the time, the desktop, the agent and the program, and every session is recorded on video. Your team and your auditors can check any task later, and it all stays on your servers.

    every desktop is ready on day one.

    Set 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.

    • Your programs, already signed in

      The ERP, Excel, the VPN and the browser your team uses, open the moment the desktop starts.

    • Clipboard and files

      Copy between programs, open attachments, save exports to a shared folder on your network.

    • A real desktop

      Windows or Linux, with a screen, keyboard and mouse the agent uses the way a person would.

    Desktop 14logins from your vaultfresh copy of your setuprecording
    • Logins in your vault

      The agent uses saved sessions and never sees the passwords.

    • A clean start for every task

      When the task ends the desktop goes back to your setup. Nothing carries over to the next one.

    • A recording of everything

      Video and a click-by-click log of each session, kept on your server.

    start with one process.

    • Post supplier invoicesdaily
    • Weekly order reportMondays
    • Timesheets into payrollmonthly
    • Book patient visitsdaily
    1

    Pick one task your team repeats

    Something done by hand every day or week, like invoices, orders or timesheets. One process is enough to start.

    $ npx hangar up checking this server ok desktops ready ready for the first task
    2

    Install Hangar and set up one desktop

    One command on your server, then install the programs and sign in once, like for a new colleague.

    3

    Watch it run, then add the next

    Check the work in the log and the recordings. When it runs well, hand over the next process. Hangar runs as many desktops as your hardware can hold.

    questions

    Short answers for operations, finance, IT and security.

    Do my programs need an API?

    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.

    How many desktops can I run?

    As many as your hardware holds. Most teams start with one process on one server and add desktops when they hand over more work.

    Which tools can send tasks?

    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.

    Where do the desktops run?

    On hardware you control: your own servers, a VM in your cloud account or a single workstation. We do not host your desktops.

    How are logins handled?

    Sessions are saved in the desktop setup or in your vault. The agent can use them but cannot read the passwords.

    What happens when a task is done?

    The desktop goes back to a clean copy and is free for the next task. The recording and the log stay on your server.

    give your agents a desk of their own, on your own servers.