People ask in plain words: answer this email, set up the meeting, draft the proposal from our template, find what the client wrote in Telegram. The assistant does the work on your server and asks before it sends anything on someone's behalf.
Every action the assistant wants to take is checked on your company's server before it runs. The model cannot talk its way past a rule: the server decides, the assistant can only ask.
Text from emails, chats and web pages reaches the model marked as data, not as instructions, so a message from outside cannot order the assistant around.
Try it: set the rule for each action the way your admin would. The log on the right shows what happens.
We set it up for one team first, check it on real work, and only then open it to everyone else.
One command installs it on a server in your company: HTTPS, nightly copies, updates with a rollback. It brings its own database or keeps its data in your PostgreSQL.
Your admin decides, action by action, whether the assistant does it, asks first or never does it. Models, accounts and systems are chosen for each team.
Each person gets an invitation by email, sets a password and adds a code app on the phone. Then the assistant works in any browser, on a phone, or in the Windows app.
We connect your mail, calendar and systems, add your templates and run the assistant on a set of your real tasks, with the pass mark agreed before the run.
Your admin works in one console: who has access, which team may use which model, mailbox or internal system, and what the assistant did yesterday. A change there reaches every person at once, with nothing to update on their computers.
Honest note: the assistant makes mistakes, like any model. That is why anything that leaves the company waits for a person's yes, and why the log shows exactly what it did.
The assistant, people's chats, files and connected accounts live on your company's server. Models run on your own hardware by default; a cloud model is used only where your admin allows it, team by team.
Open models on your own hardware by default. When a task needs more, your admin can allow a cloud model for a specific team. We test the model on your kind of tasks before the team relies on it.
No. Those actions are not available to it at all, whatever the rules say.
Nothing for the browser or a phone: they open your company's address and sign in. The Windows app adds work with files, the screen and the browser.
Every update starts with a copy of the database and the keys, and one command rolls it back. Copies are also made every night and kept for 14 days.
Yes. It comes with its own PostgreSQL, or it uses yours if your IT team prefers to run the database.
We set it up with your rules, connect the accounts one team uses and check it on real tasks. If it does not save that team time, the log will show it, and we will tell you so.