A coworker on every team
Finance, support, sales, RevOps, marketing, HR. One workspace, one memory of the company.
Finance, support and sales each get a coworker. You set what it may read and what it may spend.
What you get
Hire once. Every team gets a coworker that already knows your company.
Finance, support, sales, RevOps, marketing, HR. One workspace, one memory of the company.
Put a job on a schedule or a trigger. It runs overnight and reports in the morning.
Waiting on you
Pay invoice #4471 to Northwind
£4,280
Above your £2,000 limit
Set the limit above which it must ask. It stops, asks a named person, and records the answer.
Why Alfera
Give it the work and the access. It gets sharper every week.
Same workspace, same memory of the company. Different jobs, different permissions.
See workspace credit usage in one place.
See completed runs, who started them, and their credit usage.
Money
Follow credit usage over time and see what each job costs.
Review each run, who started it, and its credit usage.
Pick the models your teams may use. Ban the rest.
Your own provider keys. The model bill stays yours.
Every job carries what it cost.
Access
It reads what you attach and nothing else. Narrow the scope and it forgets, that second.
Reading an inbox and sending from it are two permissions. Grant them separately.
Okta, Entra, Google. They leave the directory, the access goes.
One person, one team, or the whole company. You decide.
Choose which connections exist in your workspace at all.
Permissions sit outside the model. No message argues past one.
Data retention
Zero retention is off until you ask. Your workspace admin requests it, and we turn it on.
It starts the day we turn it on. It does not reach backwards.
Models
190+ models, 70+ of them open weight. Approve the ones your teams may use.
Use a recommendation or choose a model for the conversation.
Use your provider contract and the model bill goes to you, under your own data agreement.
Cheap models on the volume work, the strong one where it matters. Switch any time.
Deployment
Same product, same controls. What changes is whose network it sits in.
We host it, in the region you pick. You set the retention.
Your own deployment, managed by us. Nothing shared with anyone.
Inside your account, on your network. The traffic never leaves.
Start on our cloud today and move later. Everything moves with you.
Rollout
No pilot committee. Two teams, then the company.
Channels
No new tool, no new tab, no new password.
Channels, private channels and DMs. It answers in the thread it was asked in.
An address on your own domain. It replies like staff.
For the people who never open Slack. Coming soon.
Single sign-on, the audit log, and every admin control.
A coworker inside your own product, same permissions.
3,000+
3,000+ connections, every one respecting the permissions you set. Missing one? We build it, on a date in the contract.
In the region you choose. You set the retention period, and we delete on it. Everything exports while it exists.
No. We do not train on it, and we never opt you into a provider’s training. Providers may hold API traffic briefly under their own terms. Ask us for stricter terms, or bring your own keys.
Yes, on a sales-assisted contract. Single tenant or your own network.
Two teams in a week. The company in a month. Your security review is the long pole, not the software.
Every read, tool call, message, approval and cost. Filter by person, team or coworker, then export it.
It stops at your limit and asks a named person. Reading and sending are separate permissions, enforced outside the model.
Start on your own today, or bring us into the security review.