Services · Your own company chat assistant

Your own company chat assistant, in place of a seat for every person.

You pay a monthly seat for every person who uses a chat assistant. We set up an open-source chat assistant on your own servers, with your company sign-in, and connect it to the models you choose.

100%
Of released code written by AI, and proven by an eval suite
Your sign-in
Staff log in with the company account they already have
Your choice
A model on your own server, a paid model, or both

The same kind of screen, on a server you run.

Chosen by licence

We read what each project's licence allows a business to do before setup.

Company sign-in

Access follows the company account, and ends when the account ends.

Any model behind it

Your own model server, a paid model billed by use, or both.

Rules per team

Who can use which model, who can upload files, how long conversations are kept.

A planned move

Instructions for staff and an end date for the paid seats.

Built to fit your work

Connections to your documents and your other systems, built in the same project.

A paid chat assistant charges for each person each month. Add people and the bill rises with them. What your staff type into it is stored by the vendor, under the vendor's terms.

Open-source chat assistants give your staff the same kind of screen on a server you run. Our pages on alternatives to ChatGPT and alternatives to Claude list them, among them LibreChat, Open WebUI and AnythingLLM. They differ in licence: the directory marks LibreChat and AnythingLLM as open source and Open WebUI as source available, which means its licence puts conditions on some uses.

What we do

Choose the project for your company. By its licence, the sign-in methods it supports, and the features your staff use today.

Set it up on your servers, with your sign-in. Staff log in with the company account they already have. When a person leaves the company, their access ends with their account.

Connect the models. The assistant is a screen. Behind it, the answers come from a model. That can be a model on your own server, a paid model billed by use, or both. We set up the ones you choose.

Set who can do what. Which teams can use which model, who can upload files, and how long conversations are kept.

Move your people over. Short instructions, saved prompts carried across where the paid tool lets you export them, and a date when the paid seats end.

Add what your work needs. A button that sends an answer to your ticket system, a connection to your documents, a report of use by team. This is ordinary software work and we do it in the same project.

The cost to compare

Paid seats cost a fixed amount per person. Your own assistant costs the server, the model use behind it, and the time to look after it. Which is lower depends on how many people you have and how much they use it, so we work it out with your figures before you decide. We publish no saving, because nobody has measured yours.

Common questions

What is an open-source alternative to paying for ChatGPT seats?

Open-source chat assistants such as LibreChat, Open WebUI and AnythingLLM give staff a chat screen on a server the company runs. Our directory lists them on its alternatives to ChatGPT page with each project's licence. Reveneau chooses one for your company, sets it up with your sign-in, and connects it to the models you choose.

Which model answers the questions in our own chat assistant?

You choose. The chat assistant is the screen your staff type into, and it passes each question to a model. That model can run on your own server, can be a paid model billed by use, or you can offer both and let each team pick. LibreChat's own description lists Anthropic, OpenAI, Google and Ollama among the providers it connects to.

Can staff log in to the chat assistant with their company accounts?

Yes, where the project supports your sign-in method. LibreChat, for example, describes multi-user sign-in with OAuth, LDAP or email in its own documentation. Reveneau connects the assistant to your company accounts, so a new employee gets access with their account and a person who leaves loses it when their account is closed.

Where are our conversations stored with our own chat assistant?

On the server Reveneau sets up for you, in your own account. You decide how long conversations are kept and who may read them. If the assistant sends a question to a paid model, that question goes to the model's vendor under the vendor's terms, and Reveneau shows you which models keep data on your side and which send it out.

Is our own chat assistant cheaper than paying per seat?

It depends on your numbers. Paid seats are a fixed amount per person. Your own chat assistant costs a server, the model use behind it, and time to look after it. Reveneau works out both sides with your headcount and your real use before you decide, and we publish no general saving because none has been measured.

Can we move our saved prompts and chats from the paid tool?

Only what the paid tool lets you export. Each vendor decides what an account can download, and that changes over time, so Reveneau checks the vendor's own export page on the day. Where prompts or chat history can be exported, we load them into the new assistant. Where they cannot, staff copy the ones they need by hand.

Can our own chat assistant read our company documents?

Yes, as a second step. An assistant that answers from your own files needs those files prepared for search and needs rules for who may see which document. That work is its own service at Reveneau, your own search over company documents, and it can be built in the same project as the chat assistant.

What does source available mean for a chat assistant?

Source available means you can read and run the code, and the licence puts conditions on some business uses. The conditions differ from project to project. Our directory marks Open WebUI and LobeHub this way. Reveneau reads the exact licence against what you plan to do before choosing a chat assistant for you.

Other services

Replace a paid AI service with one you own.

You pay an AI vendor by the month, by the seat or by use, and the bill grows with your business. We set up an open-source replacement on your own servers, connect it to your product, and build the software around it. At the end the servers, the data and the code are yours.

Your own AI model server, in place of a bill for every request.

You pay a model vendor for every request your product makes. We set up an open language model on your own machines, give it the request format your code already uses, and test it on your real work before you switch.

Your own search over company documents, on servers you control.

You pay for a tool that searches your company's files and answers questions from them. We set up an open-source replacement on your own servers, connect it to where your documents live, and keep each person's view limited to what they are allowed to see.

Your own automation platform, in place of a bill for every task.

You pay an automation service for every task it runs, and the automations your business depends on live in someone else's account. We set up an open-source automation platform on your own servers and rebuild your automations on it.

Your own voice AI: speech, transcripts and phone agents on your servers.

You pay a voice service for every character it speaks or every minute it listens. We set up open-source speech models on your own hardware, connect them to your product or your phone system, and test them in your language before you switch.

Your own AI coding tools, with your code kept on your machines.

You pay a seat for every engineer who uses an AI coding assistant, and parts of your source code are sent to the vendor with each request. We set up open-source coding tools for your team, connected to a model you choose, including one on your own servers.

What are you building?

We would love to hear about it and see how we can help.

Send us a message
Start a project