AI agents your technical teams already use, run as a company asset
AI, one laptop at a time: each agent lives in one person's window, stops when that laptop sleeps, and nobody else sees what it did. Oasis makes those agents a shared way of working: they keep going on machines you own, and the whole team can watch, read and steer them.
The agents here are the ones engineers and technical staff run on a computer to write code, run tasks and fix things: Claude Code (from Anthropic), Codex (from OpenAI) and Kimi Code. Your company keeps paying those providers directly; Oasis is the shared workplace they run in.
Companies license Oasis per rollout; anyone can try it on their own machine first.
Nothing to sign up for to use the app. Installs on your Mac, Linux or Windows PC; works with Claude Code, Codex and Kimi Code.
Live in your browser
The actual Oasis app in demo mode, with a sample company fleet: four machines and several agents. Nothing to install, nothing to sign up for. Press Play, then open any window. Open the full-page demo to click around.
Loading the live demo…
Every screen on this page is captured from this built-in demo fleet; the colleagues' cursors are staged to show presence.
What changes
The easy way to adopt AI is the way spreadsheets were adopted: one person, one window, one laptop. Good for the individual, invisible to the company.
The same agents your teams use now: Claude Code, Codex, Kimi Code. Oasis launches them, brings them back and reads them; it does not resell them. The AI providers you subscribe to still process what your agents send them: Oasis changes where the agents run and who can see their work, not where the models run.
Continuity
Each agent runs on one of your machines, not inside the app on someone's laptop, so closing the app changes nothing. Disconnect, sleep, go home: the agent keeps working. After a restart, agents and their conversations come back where they were, with the settings they started with.
An AI manager (we call it a Supervisor) keeps a goal and a schedule, hands tasks to agents, and tracks them on a board of to do, in progress and done. It keeps working while nobody is logged in, using an AI model you choose, on an account you hold.
When a machine reboots, its sessions return with the same names, folders and conversations. An agent picks up where it left off, with the settings it started with.
Copy an agent's conversation at any point and run two versions side by side, a safer one and a bolder one. Both keep everything said so far.
One notification centre collects "the agent is waiting for you", finished tasks, builds and machine events, each linked to its machine and session. Every desk sees it.
Every machine keeps a searchable library of its agent conversations, with recording switched on by you. Find every place a topic came up, across the company.
Give an unattended agent its own clean, throwaway computer on a company server, with extra computing power for heavy jobs when needed; on a server set up for it, one starts in seconds. Its mistakes stay off your other machines, and you delete it when the job is done.
If a machine restarts, the conversations and sessions come back; anything an agent had not yet saved at that instant is lost, as with any program. A machine that is switched off is off. When you reconnect you see the recent part of the conversation on screen; the full record is in the searchable library.
Oasis does not stop an agent from acting: it shows you everything the agent does but adds no extra permission step of its own. The limits you set inside the agent still apply. For work nobody is watching, give the agent its own throwaway computer so a mistake stays off your other machines.
Shared work
A machine's workspace is one shared picture that everyone invited sees as it changes: the agents, the files, the notes, the board. Your team looks over an agent's shoulder together, from any desk, with no screen-share call.
Invite colleagues to a shared desktop on a company server and they see the same windows, files and board, live. Each colleague gets their own named login on that server, so access is per person and can be taken away per person; there is no share link to forward.
Faces in the toolbar and live cursors on the work. Colleagues appear as people, not as machine names.
A colleague takes over mid-task from another desk, ticks off the shared to-do list, or hands the next item to the agent in one click.
Notes, checklists and risks next to the agents' own windows, drawn and typed together as it happens.
Chat and direct messages travel over your own private network and are encrypted between people; the server that passes them along cannot read them.
One invite code gives a colleague their login, their identity and their place on the private network; access is withdrawn from the People panel, in one place.
Shared desktops run on a Linux server you administer; Macs and Windows PCs join them. Treat invite codes like passwords.
A scenario built only from what ships. Not a customer story.
Nothing below needs a vendor account, a vendor cloud or a new operations team.
The sidebar shows every machine and who is on each. The overnight AI manager finished two tasks; one agent is waiting for an answer. She reads its plan as prose and replies: yes, but keep the old pricing table.
Same machine, different chair. He sees her cursor, ticks a shared to-do, hands the next one to the agent, and copies the conversation to try a bolder approach beside the safe one.
One invite code creates her login, her identity and her place on the private network. The whiteboard already holds the notes and the live agents; she draws on it from a Windows laptop.
An update reboots the machine. By morning the sessions are back with their names, folders and conversations, and the team carries on from the board.
Ownership
Oasis reaches your machines with the secure connection your IT team already uses (SSH) and joins them on a private network you run yourself: office, home and cloud. The computer that admits machines to that network is one of yours, not ours. No vendor cloud sits between you and your machines.
Roles for owner, admin, operator and member follow the person, not the laptop. Access to a machine is given to a named person for a set period and taken away in one place. A person's identity can be kept on a small USB security key.
Each Mac or Linux machine can be locked to the private network only, and a scan from your own server shows what the internet can reach. Windows PCs rely on Windows' own firewall.
Each machine backs itself up on a schedule, encrypted, to storage you choose and hold the keys to. Restore one file or a whole session from any backup point.
Claude Code, Codex and Kimi Code stay your subscriptions. One view shows how much of each one's allowance is used on each machine and which have room right now. Oasis sells no AI of its own.
Keep a company default for Claude Code and Codex settings on every machine. Where a machine drifts from it, you see the difference; an unauthorised API-key override is reset in a click.
Oasis reaches machines over the keys IT already manages (SSH). Switch Oasis off and the machines, sessions and files are still there.
What leaves your machines. In plain terms: your code, conversations and files stay on your machines. Oasis (made by Varrock Inc.) hears from the app only when it checks for updates. Exactly, with the two small exceptions: the desktop app has no user accounts, no telemetry and no analytics. The desktop app's only contact with Varrock-operated infrastructure is the update check against oasisgui.com; everything else runs on machines you control — except that the Mesh view asks api.country.is for the country of each peer's public IP to draw a flag, and Claude accounts you add are checked against Anthropic. Other connections happen only when you switch a feature on: the AI model you pick for an AI manager, your backup storage, public image servers when you create a virtual machine, and public-address checks for the exposure scan. The security documentation lists every one.
Getting started
Oasis installs like software, not like a service: no account, no vendor cloud, no server to buy before the first install. Your IT lead installs the app, adds the company's machines, and Oasis puts a small background program on each one over the connection IT already uses; nothing is added to a machine without IT choosing it. Grow into it in four steps.
Install on a Mac or Linux laptop and add the servers IT already connects to. From then on, agents run on those servers and outlive the laptop.
Pick a Linux server and invite the team with single-use codes. Shared desktops and the whiteboard switch on.
Create it in Settings and run its control point on a server you own; office, home and cloud join. Add a second control machine for safety. Lock machines to the network.
Backups to your storage, every AI seat in one view, documentation for IT. Talk to us about licensing and a rollout.
Mac: Apple Silicon. Linux: x86-64. Windows PCs join and view; the work itself runs on Linux or Mac machines. Updates are announced and installed only when you choose.
Talk to us about a rollout Write to sales@oasisgui.com with the size of your team and the machines you run; we reply with licensing and a rollout plan.
For your company
Your IT and security reviewers will want the detail: how it is built, what talks to what, how access is granted and taken away, how to run it day to day. Varrock Inc., the company behind Oasis, writes that documentation against what actually ships and rates each security measure as present, partial or missing. Request access for your company; your IT lead signs in once approved.
We'd rather you knew before you asked.
What Oasis is and what talks to what.
The parts, where each one runs, and where your data lives.
What is encrypted, where keys live, what leaves a machine, and what we would not claim.
From the first install to the private network, step by step.
How access is granted to people and taken away.
Running it day to day: updates, backups, logs, what to do when something fails.
Machines, disposable computers, graphics cards, and how to govern agents.
Exists, partial, missing: an honest checklist, with a pilot-to-rollout plan.
Symptom, cause, fix, and where every log lives.
Rolling it out to a team? Write to sales@oasisgui.com with the size of your team and the machines you run; we reply with licensing and a rollout plan. Your reviewers can request access to the documentation.
sales@oasisgui.com
Requesting access asks for your name, work email and company; see the privacy policy.
Free for personal use
Free for personal use on macOS, Linux and Windows. For teams and companies we offer enterprise licensing: talk to us. Licence terms. Updates are announced, verified, and install only after you choose Update & Restart.
Signed with Varrock's Apple Developer ID and notarized by Apple. Local virtual machines need macOS 13 or newer. Intel Macs are not supported.
Needs libwebkit2gtk-4.1, libgtk-3, libayatana-appindicator3,
libssl3, openssh-client. NixOS: use the flake; updates then follow Nix.
Installs for the current user. Windows joins and views; the work runs on your Linux or Mac machines. Windows will ask: More info → Run anyway.
Built in Rust
A native app. The engine, the private network and the helper on each machine are written in Rust. On a Mac the terminal can draw with the native graphics engine.
