Product : $590, installed by me
It knows your business: your rules, your files, what your team agreed last month. It reaches the tools you connect. You decide who on your team gets how much of it.
Ava
Your own chat
Jira and GitHub, connected by you. It acts only at the level you gave it.
You pick the name, the avatar, the chat app, and who gets in.
$590
Once, and I do the install myself
2 days
From your empty server to your first scheduled job
3 levels
Owner seat fixed to you, two more you hand out
5,000+
Services it can connect to, through integrations.sh
Write to it in Telegram, Slack or Discord, whichever your team already opens every morning. It carries the name and the face you give it.
Your standing rules, your files, and the history of every chat it sits in. It answers from what your company actually knows, not from a blank page.
What did we promise the supplier on delivery, and does the contract in the shared drive say the same?
Your standing rules, your files, and the history of every chat it sits in. It answers from what your company actually knows, not from a blank page.
What did we promise the supplier on delivery, and does the contract in the shared drive say the same?
It runs commands, edits files, searches the live web, and works in the tools you connected, all from the chat.
Pull last month's orders out of that spreadsheet and tell me which customer slipped.
Ask for a plan first and it writes one and waits. Approve it, or tell it what to change.
Write me a plan for moving the price list into Notion, then wait.
A connections layer between the assistant and the tools you already run. Google Workspace, Atlassian, Git, and almost anything with an API.
The connections layer is powered by integrations.sh, one registry of every service an agent can speak to. It bills separately, and everything else on this page works without it.
An access layer between your team and the assistant. The owner seat is fixed to you on install day and cannot be granted or talked into changing from a chat. Below it you hand out two levels, and a group chat always gets the weakest one, whoever is in it.
You: The owner. Fixed on install day. Few: The people you pick. All: The rest of the team.
| You | A trusted few | Everyone else | |
|---|---|---|---|
| Answers in your team's group chats | You: Yes | A trusted few: Yes | Everyone else: Yes |
| A private helper of their own | You: Yes | A trusted few: Yes | Everyone else: Yes |
| Runs commands and edits files | You: Yes | A trusted few: Yes | Everyone else: No |
| Reaches the services you connect | You: Yes | A trusted few: Yes | Everyone else: No |
| Sets up scheduled jobs | You: Yes | A trusted few: No | Everyone else: No |
| Adds and removes people | You: Yes | A trusted few: No | Everyone else: No |
Add it to the group chats your team already uses. It reads along, speaks only when called, and remembers what the room agreed.
Sales team
6 members
Say its name and it answers. Ignore it and it stays quiet.
An answer from a conversation three weeks ago that nobody scrolled.
Say it and it answers. A question, a reminder, a whole scheduled job, all dictated.
In your own chat you can photograph the invoice and ask what it says, or forward the contract and ask what you signed up to on delivery times. Several photos at once count as one question.
Reminders take plain words. "Remind me about the invoice on Friday" is all of it.
Every reminder carries Done and Postpone. They arrive when they are due, once, and never twice.
Set up a job by describing it once. Any schedule you like, in your own timezone.
Last week's sales, posted in your chat
A check that the backup ran, and a message only if it did not
Every invoice still unpaid
Run now fires even while a job is paused
Show it the steps once and it saves them, and from then on that job replays for pennies instead of thinking it through again. Replaying saved steps needs the service connected, and every other kind of job runs without it.
Ava
Your own chat
No command to remember: say the schedule and it is set.
How a job gets set up, in the chat you already have open.
The task list
Shows each job with its next run and how the last one ended, with pause, delete and run now on each.
When a run fails
It tells you once, in one sentence, then tries again on schedule.
Who can schedule
Only you can set up a job, because a job acts with your authority.
It sits on your server and calls out to your chat app. There is no door into it from the internet, and no shared database with other companies' data next to yours.
The machine is yours and it runs nothing but this assistant, so there is no customer database and no payroll sitting on it to lose.
It restarts itself after a crash and comes back after a reboot, and an update does not kill work in progress. Crash in a loop and it stops retrying and waits for a human, rather than thrashing.
Copy that folder and you have the lot. I switch on the nightly database backup at install, and it keeps 14 days of snapshots, catching up if the machine was off.
Every run appends one line to a log file on your server with who asked, which model answered, how long it took, and what it cost.
Voice notes leave once, to be turned into text. Your message text goes to the model that writes the answers. Beyond that, only what you point it at: a web search you asked for, or a service you connected yourself.
Standing rules and saved multi-step workflows live as plain files in your workspace, so they outlive any reinstall.
$590, once, and I do it. Two days from your empty server to your first scheduled job.
It goes on a small server of your own, under a bot carrying the name and the avatar you choose, so your team meets a new colleague rather than somebody else's software.
It works with the ChatGPT plan you already pay for, connected once from your phone with a code posted in the chat. Which models it can reach depends on that plan.
Telegram, Slack or Discord. It joins the group chats you pick, answers to the name you pick, and posts one message telling the room how to get its attention.
The services you run connected through integrations.sh, everyone added at the level you want them on, and the owner seat fixed to you.
We set up your first scheduled jobs and reminders together, so you have watched it done before I leave.
Past the $590 you are paying for that plan and a small server of your own. Connecting outside services runs through integrations.sh, which bills separately, and everything else works without it.
Running assistant, wired to your business
A personal assistant in your team's Telegram that runs on your own server, knows your business context, and works with the services you already use.
Tell me which chat app your team uses and which tools you run. If it fits, I install it on your server in two days.
$590 once. After that you pay your own plan and your own server, not me.