// Aivium Gateway · Company AI gateway
Team AI. Company control.
Your team needs AI. You need control over access and usage.
Connect employees through a server you manage. Choose their models, tools and permissions while company API keys stay on the server.
- Shared models and company knowledge.
- Individual permissions for each employee.
- Office, remote and mobile access.
- Request quotas and usage records.
Sales team
Gateway running
- Approved models
- Permissions and request quotas
- Provider API keys stay here
Who has the key now?
“Send me the API key.” “Who ran up this bill?” “Can our former contractor still connect?” Small requests quickly become an access problem.
Gateway puts those decisions in one place:
Keys in chat?
Connect providers on your company server.
Unexplained usage?
Review activity by employee and model.
Different jobs?
Assign different tools and permissions.
Someone leaving?
Revoke their device access.
Configure once. Connect your team.
Setting up every computer separately slows everyone down. Gateway turns one machine into your company’s shared route to AI.
-
01
Connect AI
Add a provider key and select models.
-
02
Set access
Choose tools, permissions and request quotas.
-
03
Invite people
Send invitations or approve account requests.
-
04
Review activity
Check usage and adjust the setup.
Connected desktops receive policy and toolkit updates automatically.
Diagram
Different locations. One company connection.
Office today, home tomorrow, phone between meetings. Connect each device to your company with the access it needs.
Office
Provision workstation settings centrally.
Remote
Connect through your server’s reachable external address.
Mobile
Open company chats without keeping your desktop online.
When direct access is unavailable, the separately paid Aivium Relay module provides a connection over TLS. Your company server needs to remain available.
Give each person room to work
A new hire and an administrator need different access. Start with a role, then adjust explicit permissions in the person’s profile.
- Approved providers and models.
- Personal API keys and MCP connections.
- Company modules.
- Home device restrictions.
- Company usage and audit visibility.
- Individual device revocation.
Company defaults save setup time; individual settings fit the job.
Example: Maya gets company models and sales guidance, with personal integrations disabled.
← All people
Maya Reed
Sales specialist
This person’s permissions
- Personal API keys Company default Yes No
- Personal MCP connections Company default Yes No
- View company usage and journal Company default Yes No
- Change company rules Company default Yes No
- Work laptop Work Revoke
- Phone Home Revoke
+ Another device
Know what drives your AI bill
Unexplained usage makes planning harder. Gateway records the employee, model, chat, response time, available token counts and estimated cost.
Filter the journal, export CSV and give the right people visibility. Set request quotas per device using individual rules, plus a shared company limit.
| Person | Provider / model | Chat | Input / output | Duration |
|---|---|---|---|---|
| Anna | Company API / Model A | Customer reply | 1,240 / 360 | 3.2 s |
| Maya | Company API / Model B | Document summary | 3,100 / 520 | 5.8 s |
| Leo | Company API / Model A | Spreadsheet review | unavailable | 4.1 s |
-
Anna · Customer reply
- Provider / model
- Company API / Model A
- Input / output
- 1,240 / 360
- Duration
- 3.2 s
-
Maya · Document summary
- Provider / model
- Company API / Model B
- Input / output
- 3,100 / 520
- Duration
- 5.8 s
-
Leo · Spreadsheet review
- Provider / model
- Company API / Model A
- Input / output
- unavailable
- Duration
- 4.1 s
Example quota: 40 requests per 60 minutes per device
A working toolkit from day one
New hires should not have to assemble their tools from old messages. Prepare a shared setup and tailor it for individual employees.
- Models
- Company AI without receiving provider keys.
- MCP connections
- Connected service tools through the company server.
- Agents
- Assistants configured for specific jobs.
- Knowledge bases
- Approved guidance through a company agent.
- Skills
- Reusable instructions for recurring work.
- Brand styles
- Shared design materials.
- Company contacts
- A shared address book with viewing, editing and export permissions.
Example: A Sales Assistant already uses your Sales Playbook. Manage address book access separately in Company → Contacts.
Maya Reed · Custom set
Models and keys
Agents
MCP servers
Skills
Brand styles
Developer tools within company permissions
Developers need capable agents. IT needs control over connected services. In Aivium-managed sessions, MCP tool access goes through Aivium permissions.
Employees sign in with their own CLI accounts and use the tools they are allowed to access. These controls apply to sessions launched inside Aivium.
Codex
Managed sessions.
Claude Code
Beta integration.
Keep key integrations with the company
Does a critical integration depend on one employee’s setup? Transfer its MCP connection and credentials to the company server with explicit owner confirmation.
The company gets an independent working copy.
Conversations that turn into completed work
Decisions disappear in chat. Aivium Work brings team messaging and assignments together on your company server.
- Channels for announcements; groups for collaboration.
- Assignment cards in chat: “Take ownership,” deliver, then get approval.
- A full mobile messaging client: read, reply and share files.
- Guest invitations for contractors, with expiring group access.
- Separate permissions for publishing, inviting people and managing conversations.
On mobile, send selected messages to an agent; review its result before posting back.
Know who owns the next step
Finding the right colleague should not take another meeting. Company structure shows departments, managers and people, with search by name, role or team.
Authorized managers can review assignments by person or department. Weekly reports gather accepted results for a quick review, then save them to the company archive.
Update the customer response playbook
- Requester
- Anna
- Owner
- Maya
- Due
- 29 October 2026
Condition
Add an approval process for unusual requests.
Sales
26 October — 1 November 2026 · UTC
Preview without savingCustomer response playbook updated
Maya · accepted by requester
Open assignment
Turn “please call” into a task
Routine calls interrupt focused work. With AI calling, ask a desktop agent to make the call and confirm who it should contact and why.
Use a compatible SIP provider or your own PBX. Manage company calling connections and number access from Company settings.
Calls run through a connected desktop; calling credentials are held on aivium.app. Inbound AI answering requires the designated desktop to stay online.
Keep keys central. Make access explicit.
An API key copied across employee devices is hard to control. Gateway keeps company keys on your server and checks access from connected devices.
- Company API keys
- Used on the server without distribution to employees.
- Server connection
- TLS encryption with certificate verification.
- Work tools
- Available through company permissions.
- Company knowledge
- Files stay on the server; permitted material is retrieved.
- Departing employees
- Access can be revoked for their devices.
One team. One useful workflow.
A company rollout does not have to start company-wide. Try a recurring task, such as drafting customer replies from an approved playbook.
-
01
Choose a server that stays available.
-
02
Connect your provider and selected models.
-
03
Set up a secure connection.
-
04
Invite people and assign permissions.
-
05
Share an agent, knowledge and tools.
-
06
Review the results and usage.
The setup wizard guides the first steps. Expand when the workflow works for your team.
Download AiviumRun a server, not an open window
Company access should not depend on an administrator keeping an app open. Run Gateway as a Windows service or without a graphical interface on Linux.
- Windows service deployment.
- Headless Linux operation.
- Centralized workstation settings.
- Windows workstation updates distributed through the company server.
- Downloaded installer signature verification.
Provision computers centrally and manage the updates they receive.
Before you connect your team
Do we need dedicated hardware?
Will employees receive our provider keys?
Can people connect from home?
Does mobile messaging need a desktop online?
Can we set a budget per department?
Can managers read every conversation?
Does all data stay inside our company?
What happens if the server goes offline?
Does Gateway support SSO or Active Directory?
How is it priced?
Give your team a place to start
Dozens of setup decisions should not delay a useful workflow. Pick one team, connect a model and give people a toolkit ready for their work.