Platform
- HumanikOSThe operating system for AI employees.
- How it worksDescribe the job, and Nova sets up an AI employee.
- Humanik CloudWe host and run the offices your humi work in.
- HumiYour AI employees, each with a name and a role.
- OfficesThe computer each huma works in, with its tools and logins.
- PermissionsChoose what each person and each huma can see and do.
- Frameworks and modelsPick the agent framework and AI model each employee uses.
- Your own machinesRun employees on a computer you own.
- Connect anythingYour tools, our built-in apps, or both.
- Bring your agentsAgents from other platforms join your team as members.
- NovaThe assistant that operates HumanikOS for you.
Built-in apps
Company
Your own machines
Run an AI employee on a computer you own.
HumanikOS can handle the machines and the cloud for you. Or run an AI employee on your own computer instead, and give it only the work you choose.
- Runs onyour computer
- Keys stayin the office
- Startsread-only
- Falls back toa hosted model
Devices
Let a huma work on your own computer.
Install one small program, enrol the computer, and point a huma, your AI employee, at it. The huma thinks there and works with the files there, and it keeps its office, its place in your workspace, its schedule and its permissions. Work done on your computer uses no Humanik credit.
Credentials
Your keys stay in the office.
When the huma needs a contact, a calendar or one of your connected apps, that step runs in its office, with the office's own credentials. Only the result comes back to your computer.
Your accounting key, your CRM token and your other credentials are never written to the computer and never sent to it. The huma still reaches the same software as a huma that works in our cloud.
Limits
You set the limits.
Three limits apply to every job, and none of them can widen another. What the computer allows is a file on that computer, written by you, and it starts read-only. The agent there can change files or run commands only if you add them to that file. We never send a list of tools, so nothing on our side can widen it.
Models
Run the model on your computer too.
In the common setup the agent runs on your computer and uses the model that comes with your own account. You can run a local model on the computer instead. Only then does the work never reach a model vendor.
A local model thinks and answers. It does not act on the computer, and the huma's tools still run in its office.
When it is away
Falls back when your computer is busy or offline.
A closed laptop is normal. If the computer is offline, or it fails a request before any answer arrives, for example because its account reached its usage limit, the work can go to a hosted fallback model that you chose, paid from Humanik credit. The board shows when a huma is on its fallback.
Work never moves to a second computer. After many failures in a row the fallback pauses for a few minutes, so a broken computer cannot send work to paid models all day.
Your fleet
See every computer, and when it was last seen.
Each computer has its own page: whether it is online, what it serves, which workspaces use it, and when it was last seen and last connected.
Enrolling a computer, revoking it and choosing which workspaces may use it are console steps for the account owner. Once it is assigned, an office operator can point a huma at it without being able to change any of that.
Your browser
Let a huma use your own browser, if you choose.
A huma can drive the browser on that computer, in your own profile, already signed in. It ships off, and turning it on is a deliberate step.
Read this first
It acts as you, everywhere you are signed in, and nothing in the configuration file makes that smaller. Which sites it can reach is decided inside the browser extension. For work that should never touch your own accounts, use the office browser, which starts with nothing.
Setting it up
Set it up with a few commands.
A computer joins your workspace by running one small program, humanikd, on macOS, Windows or Linux. It takes a few commands in a terminal and a settings file, and then the program keeps running in the background. It is technical, and it is worth knowing that before you start.
The program connects out to HumanikOS and waits for work. HumanikOS never opens a connection to it. It never installs anything on your behalf and never runs a command we send it. The private key that identifies the computer never leaves it.
# macOS or Linux curl -fsSL https://github.com/humanikio/humanikd-dist/releases/latest/download/install.sh | sh humanikd setup # Windows (PowerShell) irm https://github.com/humanikio/humanikd-dist/releases/latest/download/install.ps1 | iex humanikd setup # any time humanikd status
Part of HumanikOS
Each huma has the same permissions and the same bill, whether it works in our cloud or on your computer.
Bring a computer of your own.
Start on the platform, then enrol a computer when you want the work, the files or the model to be on hardware you hold.