What it is
Trina AX is a hub for companies whose people use Claude and want it to work with the company's own files and ways of
working, without sharing one login.
- Each person keeps their own Claude: their own Team, Pro or Max seat, or the company's API key through the hub.
- The hub (this repository) runs at
https://<company>.trina.app when Trina hosts it, or on your own Mac mini or
Linux server. It holds the team folder, the company skills and the usage records.
- Claude usage is billed by Anthropic to your account. Nobody shares a subscription, and Trina does not resell tokens.
Why Trina AX
- Nothing new to learn. People keep the Claude they already use: the desktop and phone apps, claude.ai, Cowork and
Claude Code. On Claude Team, nothing is installed on their PCs.
- Company files, each person's permissions. One set of folder rules for people and groups, enforced on every request
from every app. A folder someone may not open does not even show up. Korean HWP/HWPX, PDF and Office files are read as
text, and every change can be undone for 90 days.
- One way of working for everyone. Write a skill once (a quote, a weekly report) in the team folder; every person's
Claude gets it, per group, and gets the new version when it changes.
- Pay the way that fits each person. Heavy users on their own Claude plan, light users on one company API key with a
monthly limit per person. Nobody needs a seat just to ask a question once a week, and nobody shares a login.
- See what is actually used. Usage per person, group, model and skill, with CSV export, plus a record of which file
each person's Claude opened.
- Open source, your server or ours. Apache-2.0. Run it yourself for free, or let Trina host it at
https://<company>.trina.app and run the rollout. Leave any time with your files and the same software.
What employees do
On Claude Team or Enterprise, nothing is installed on a PC:
- The admin adds the hub once as an organization connector and pastes the managed settings the hub generates
(Admin › Claude 조직 설정 in the hub).
- Each employee opens their invite link, picks a password, and clicks Connect on the company connector in Claude.
- They ask Claude about company files, on the desktop app, claude.ai, the phone app, Cowork or Claude Code.
On Pro or Max, each person adds the connector address once (Claude › Customize › Connectors › Add custom connector).
People on the company API key connect Claude Code with one command from their hub page.
Features
- Company files with each person's permissions. The team folder reaches Claude as tools (
list_files, read_file,
search_files, write_file, edit_file, move_file, delete_file, ...). Permissions are set per folder, for people
and groups; a folder someone may not open answers exactly like one that does not exist. Reads PDF, Word, PowerPoint,
Excel and Korean HWP/HWPX as text. Files can also be uploaded, downloaded and organised in the browser.
- History and restore. Every change keeps the previous version; deleted files go to a trash. Both are kept for 90
days and can be restored.
- Company skills. Skills in the team folder's
skills/ are packed into a Claude Code plugin and kept up to date, and
Claude apps can read them through the connector.
- Two ways to pay for Claude, per person. Own subscription (the default; usage arrives from Claude Code's telemetry,
attributed by the Claude login email) or the company API key through the hub's model relay, with monthly limits per
person, group and company. The key never leaves the hub.
- Usage. By person, group, model and skill, with CSV export.
- Invites. Admins invite people one by one or by pasting a list; each person gets a single-use link instead of a
temporary password.
- Phone chat and scheduled jobs (optional, company API key): the hub runs a few Claude sessions itself, with
built-in tools off, so they only touch files through the same permissions.
- Web pages in Korean for setup, admin (people, groups, folder permissions, budgets, usage, skills, Claude
organization setup, settings, audit log, restore) and each person's first-run page.
- Operations. A
trina-ax command (status, doctor, backup, restore, users, logs, ...), an always-on
macOS LaunchDaemon installer, a Linux systemd unit, deploy/cloudflare/customer-address.ts for <company>.trina.app
addresses, and a Korean operator guide.
How it compares
O yes · △ partly or with conditions · X no · ? not confirmed from official documentation
| Trina AX | Claude Team (+ Google Drive connector) | ChatGPT Business | Microsoft 365 Copilot | Google Gemini (Workspace) | Glean | One Claude login, shared |
|---|
| Each person keeps the Claude they use (apps, web, phone, Claude Code) | O | O | X | △ ¹ | X | O ² | X ³ |
| Google Drive, including shared drives | △ ⁴ | △ ⁵ | △ ⁶ | O ⁷ | O | O ⁷ | X |
| Korean HWP / HWPX files | O | X | X | X | ? | ? | X |
| Each person sees only the files they may | O | O | O | △ ⁸ | O | O | X |
| Company skills or agents for everyone, per group | O | △ ⁹ | △ ⁹ | O | △ ¹⁰ | O | X |
| Usage per person | O | O | O | O | O | O | X |
| Pay per use without a seat, with a monthly limit per person | O ¹¹ | X | △ ¹² | △ ¹² | X | △ ¹² |
- Claude is a selectable model inside Copilot; people use the Copilot app.
- Glean's MCP server can be connected to Claude Desktop.
- One subscription used by several people is against Claude's terms.
- Today files go into the hub (upload or copy).
- Open bug: shared drive content comes back empty (anthropics/claude-code#53442).
- Shared-drive controls are documented for Enterprise only.
- Needs domain-wide delegation set up by a Google Workspace admin.
- The Google Drive connector needs its permission mode chosen; the default shows files to all users.
- Organization-wide, yes; per group is Enterprise only.
- Gems are shared like Drive files; they become skills in 2027.
- People on the company API key pay only for what they use, with a monthly limit each.
- Seats first, then extra usage as credits.
- File access logs (Compliance Platform) are Enterprise only.
- Closed source; a single-tenant install in your cloud exists.
- Trina hosts, sets up and runs it every month (optional, quoted).
Based on each vendor's official docs, help centers and pricing pages as of 2026-10-26 (Claude, OpenAI, Microsoft Learn,
Google Workspace, Glean). Something out of date? Open an issue.
When something else fits better
- Everything already lives in Google Drive and people mainly want to search and ask about it. Gemini in Drive
(included from Business Standard) or Claude's Google Drive connector may be enough. Trina AX does not read Google
Drive; files go into the hub.
- Already on Microsoft 365 and SharePoint. Microsoft 365 Copilot sits closest to those files.
- One developer. Claude Code on its own is simpler.
- Hundreds of people across many tools (chat, tickets, CRM). Enterprise search such as Glean is built for that.
How it works
Claude apps (desktop · claude.ai · phone · Cowork) Hub https://<company>.trina.app Anthropic
└── organization connector, OAuth per person ──────────► ┌─────────────────────────────────┐
│ authorize() on every file path │
Claude Code (signed in with the company account) │ team folder, versions, trash │
├── same connector │ company skills (plugin, tool) │
└── managed settings: telemetry + skills ──────────────► │ usage per person (telemetry) │
│ web pages, invites, audit log │
Claude Code on the company API key (optional) │ model relay + budgets │ ──► api.anthropic.com
└── one-line installer: relay + MCP + skills ──────────► └─────────────────────────────────┘ (company key)
Design and module contracts: docs/DESIGN.md.
Self-host
Try it on your computer
Needs Bun 1.3.12. ripgrep, pandoc and poppler are optional; they add file search and text from
documents.
git clone https://github.com/potenlab/trina-ax && cd trina-ax
bun install
bun run dev # http://127.0.0.1:47900/setup : create the owner (data in ~/TrinaAX; set TRINA_AX_HOME to change)
bun run typecheck
bun test tests/unit
bun run test:e2e # the whole flow with a real Claude Code (needs `claude` and `cloudflared`)
bun src/cli.ts help # admin commands
Run the hub on a Mac mini
Use a dedicated macOS administrator account for the hub. No sudo up front: the script asks only at the steps that
need it, and says why.
git clone https://github.com/potenlab/trina-ax ~/src/trina-ax && cd ~/src/trina-ax
bash deploy/macos/install-hub.sh # system service; sudo is asked per step, with the reason
trina-ax status # shows the first-run setup address: create the owner there
bash deploy/macos/install-hub.sh --tunnel-token-file ~/tunnel-token.txt --public-url https://hub.example.com
trina-ax doctor --live # when everything is green, invite people
- The hub needs a public https address for the Claude apps and for skills. A Cloudflare tunnel works without opening a
port: create one for your own domain (docs/OPERATOR.md, chapter 4), or run
bun deploy/cloudflare/customer-address.ts new <name> --domain example.com with your own Cloudflare API token.
- Set the public address before people connect.
- Update:
git pull && bash deploy/macos/install-hub.sh (settings stay). Remove: --uninstall (data/ and team/ stay).
- Linux: see the header of deploy/linux/trina-ax.service.
Hosted by Trina
Self-hosting is free. If you'd rather not run it, Trina hosts it for you: your hub at https://<company>.trina.app
on Trina's servers, set up with your folders and permissions, connected to your Claude organization, and kept updated
and backed up. Trina can also run the rollout and, every month, turn the tasks people repeat into skills.
Pricing is quoted (it depends on people, files and how much operation you want): ax.trina.app ·
[email protected]. Hosted or not, the software is the same and it is all in
this repository. Claude usage is always billed by Anthropic to you.
Security model
- One door for files. Every path from any client goes through
authorize() (src/policy/). Rules are per person and
per group; a path someone may not see looks the same as one that does not exist.
- Tokens per PC, per app connection, per person, revocable. Stored hashed (sha256), shown once. Connector tokens are
short-lived with rotating refresh tokens and can never use the model relay. The organization token (for telemetry and
the org-wide skills plugin) can do nothing else.
- The company API key stays on the hub. A 0600 file, never shown again, never logged. The relay swaps the device
token for the key, refuses requests that would run code or attach MCP servers on Anthropic's side, and applies budgets
and in-flight caps.
- Untrusted files are parsed in isolation (
sandbox-exec on macOS, bwrap on Linux) with time, size and cell limits.
- Web hardening. CSRF tokens on every form,
__Host- cookies on https (customer hubs share a parent domain), login
lockout per name and address, single-use invite links, exactly one owner.
- Nothing sensitive in logs. Logs, audit rows and errors never contain a token, the API key, a password or file
contents.
What we do not promise: what Claude reads to answer goes to Anthropic under the terms of the plan that pays for it.
Anyone with administrator access to the server can read the team folder and data/; on a hub Trina hosts, that includes
Trina's operators. On an office network without https, traffic between PCs and the hub is plain http. In subscription
mode, costs are estimates from Claude Code's own telemetry. Found a vulnerability? See SECURITY.md.
Language
The hub's pages, messages and the operator guide are in Korean; code, comments and this README are in English.
Translations of the pages are welcome.
Contributing
Issues and pull requests are welcome: see CONTRIBUTING.md. Contributions are accepted under Apache-2.0
with a DCO sign-off (git commit -s). Please follow the Code of Conduct.
License
Apache-2.0, see LICENSE. Copyright 2026 Trina Inc. (주식회사 트리나); notices in NOTICE, third-party
components in docs/THIRD-PARTY.md. "Trina" and "Trina AX" are trademarks of Trina Inc. and are not
licensed by Apache-2.0.
