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
The browser
A browser your huma can sign in to.
For the systems that have no API.
- Stayssigned in
- Watch itlive
- Replayssaved steps
- Used bymembers only
No API needed
Use the systems that have no API.
A supplier portal, a city permit site, a bank's document page. Nobody will build a connector for them, so the work stays manual. Give your huma a browser and it does that work the way a person would: open the site, find the page, fill the form, save the file.
A day at a trade business
A plumbing company checks prices on a supplier site.
Step 1
Signed in once
The supplier’s website has no API. Someone at the company signs in to it once, in the huma’s browser.
Step 2
Ask in a message
Before a quote, the owner asks the huma for the price of each part on the job.
Step 3
It looks them up
The huma opens the supplier site, still signed in, finds each part and replies with the prices.
Sessions
It stays signed in.
Sign in once. The same browser comes back for every run, with the same cookies, the same saved logins and the same profile. The machine can sleep between runs and the session is still there when it starts again.
You can also choose the country each browser appears to browse from, so sites show the right language, prices and pages.
Live view
Watch it work.
Open the browser in your workspace and you see the real page, live, while the huma is on it, with the steps it has done beside it. Not a log written afterwards. If a step needs a person, you can do that step yourself in the same view.
Watching is just that: you see the work. Afterwards you can read each run, what was asked, what it used and how it finished.
Scripts
Do it once. Replay it after.
The first time, the huma finds its way through the pages. Then the steps are saved as a script you can read. Each run after that replays the same steps, without the huma working them out again, so it does the same thing every time and costs less.
Each script is saved on its browser, next to the logins it needs.
Members
Choose who can use it.
Two things decide it, and both must say yes: a person's permissions, and a place on that browser's member list. A role in the workspace is not enough. Even the owner of the workspace must be added as a member. A huma is added the same way, and then it can use the browser on its own.
Use it
Drive its pages, talk to the employee in it, start it and stop it. Needs the use permission and a place on its member list.
Read what happened in it
Its chats, sessions and runs. Only members can read them. Managing the browser does not give this.
Set it up
Name it, choose its country, add and remove members, give it passwords and databases. Needs the manage permission, not a place on the list.
Know that it exists
Anyone with the read permission can see it in the list, marked "Not a member" when they cannot open it.
Reach your data
A browser reaches the databases you give it. Give it the fewest the job needs.
Your own computer
Or let a huma use your own browser, if you choose.
A huma working on a computer you own can use the browser on that computer, in your own profile, already signed in. It is off until you turn it on.
Read this first
It acts as you, everywhere you are signed in: mail, bank, admin pages. Nothing in the configuration file makes that smaller. Which sites it can reach is decided in the browser extension.
A browser in your workspace
Starts with nothing. Signed in only where you sign it in. Has its own member list.
Your own browser
Already signed in to everything you are. For work that needs an account only you hold.
Good to know
What to expect.
Three things people find out later and would rather know first.
Not every site
Sign-in walls, bot checks and captchas are real, and sites differ. This is for the systems whose only way in is a browser. It is not a promise that every address will work.
A site can still sign you out
The browser keeps its session. It does not change a site’s own rules, so a site that asks everyone to sign in again will ask again.
Scripts break when a site changes
When a page changes enough, its script stops matching and has to be written again. Editing a script replaces it. There is no version history.
Part of HumanikOS
The browser is one of the tools that come with HumanikOS, beside your data, CRM and phone. Use it, or use none of it.
Name the system nobody could connect for you.
Create a browser, sign in to the site once, and ask for the task. Watch the first run, then let it repeat.