Open source
AGPL-3.0, free
- The full app, free on every computer
- Source code public for anyone to read
- If you modify it and offer it to others, including over a network, you share those changes under the same license
Enterprise · Inquiries open
Murage for your whole company.
Give every person an AI Chief of Staff and the same trusted team, on the AI your company already pays for. A commercial license if your policy needs one, one team package your staff import on their own computers, and controls your security team can read line by line.
Today Murage runs on each person’s own computer. Shared, always-on workspaces come with Murage Cloud, which isn’t open yet.
One company team packageBots, skills and routines, built once and exported
Sales
Ask mode- Ember
- Patch
- Mira
- Coin
- Sentry
Same team · own logins
Support
Ask mode- Ember
- Patch
- Mira
- Coin
- Sentry
Same team · own logins
Finance
Ask mode- Ember
- Patch
- Mira
- Coin
- Sentry
Same team · own logins
Operations
Ask mode- Ember
- Patch
- Mira
- Coin
- Sentry
Same team · own logins
A commercial license when AGPL won’t do.
The Murage app is free under AGPL-3.0. If your company’s policy won’t allow AGPL software, the commercial license gives you the same app without its obligations.
Commercial license
Available on request
- The same app, without the AGPL obligations
- For companies whose policy rules out AGPL software
- Terms agreed with you, company by company
The same team on every seat.
Build one team package and share it with your staff. Each person imports it on their own computer and connects their own accounts. When you change the team, share the new version and they import it.
- Step 1Build onceDesign the company’s teams, skills and routines on one computer, with the House Rules and approval settings you want.
- Step 2ExportExport the team. Logins never travel with it, so no one inherits anyone else’s accounts.
- Step 3Each person imports itEach person imports the team on their own computer and connects their own accounts.
- Step 4Share new versionsWhen you change the team, export it again and share the new version. Each person imports it to update.
This is package distribution, not a shared workspace or central policy console. Talk to us about an assisted rollout.
On each person’s computer
Each seat runs its own copy of Murage with the imported team, while that computer is on.
A bot’s desktop on your server
A bot can work in its own Linux desktop on a server you own, over SSH. The agent itself stays on the person’s computer. Tell us if a self-hosted company setup matters to you.
Murage Cloud
Shared, always-on workspaces that keep working when laptops close. Choose Murage Cloud in the form to hear first.
Control your security team can check.
Every setting below is in the app today, and the code that enforces it is public.
Ask mode by default
Every new bot starts on Ask and checks with the person before each action it tells Murage about. Trust is granted one bot at a time, and taken back the same way.
A stop line on Full access
New bots start on Ask. On Full access, a bot stops before messaging anyone new, posting publicly, paying, or deleting outside its folder, unless you have allowed it for that task. On Hermes and other ACP engines, Ask and the stop line cover only what the engine asks Murage about: shell commands and file edits. Replies in an existing conversation go ahead on Auto and Full access. No limits turns the stop line off.
House Rules for every bot
Write how bots should work once: what they never promise, what they treat as information rather than orders. Every bot reads them.
Memory on your computers
Memory, conversations and files are stored on the company’s own machines, in Murage’s data folder. Not on our servers.
Open source, every line
The code is public under AGPL-3.0, so your security team can read exactly what the app does instead of taking our word for it.
Your engines, including local models
Run Claude Code, Codex, Hermes or a local model through Ollama or LM Studio. With a local model, prompts can stay inside your network.
Runs on the AI you already pay for, with no lock-in.
- Claude Code
- Codex
- Hermes
- + local models and more
Claude, Claude Code, Codex and Hermes are trademarks of their respective owners. Murage is not affiliated with or endorsed by them; names and logos are used only to identify the engines Murage runs.
Rolled out by people who know it.
Today that’s us. Certified partners join once the first cohort is listed.
Certified partners (first cohort coming)
Consultants and integrators who will have passed a practical exam in building and deploying Murage teams. Until they’re listed, we do the rollout with you ourselves.
About the partner programWith us
Work with the team that builds Murage on the commercial license, the rollout plan and the questions your security review raises. Or just have us set it up: tick “Set it up for us” in the form.
Talk to usInquiries open
Tell us about your company.
A few details and we’ll reply by email to talk through the license, the rollout and what your team needs.
- Commercial license available on request
- No commitment to talk it through
- Your security team can read every line of the source
Questions about a company rollout.
Why would we need a commercial license?
Murage is open source under AGPL-3.0. Some companies have a policy that rules out AGPL software, or plan changes they don’t want to publish. The commercial license gives you the same app without the AGPL obligations. It’s available on request; tell us about your company in the form.
Does everyone share one always-on workspace?
Not today. Each person runs Murage on their own computer, and the team runs while that computer is on. Shared, always-on workspaces come with Murage Cloud, which isn’t open yet.
How do we give everyone the same setup?
Build the team once, export it, and each person imports it on their own computer. They get the same bots, skills and routines, and connect their own logins. When you change the team, share the new version and they import it. This is package distribution, not a shared workspace or central policy console. Talk to us about an assisted rollout.
Can we lock settings centrally?
Not yet. Each person controls their own copy of Murage, so any user can choose No limits for their own bots. Imported teams arrive on Ask with nothing switched on.
Where does our data go?
Memory, conversations and files are stored on each person’s computer. What a bot sends to an AI, or to an app or service you connect, goes to that provider under their terms. Pick a local model and model processing stays in-house. The security overview lists every destination.
Are you SOC 2 audited?
No. There’s no SOC 2, HIPAA or outside security audit yet. What exists: the full source under AGPL-3.0, signed installers with published SHA-256 checksums, data that stays on your own computers, and a one-page overview for security reviews.
Can we run it on our own servers?
Not the agents themselves. Murage runs on each person’s computer. A bot can get its own Linux desktop on a server you own, over SSH, while the agent stays on that computer. If a self-hosted company setup matters to you, choose Self-hosted in the form and tell us what you need.
Who does the rollout?
Today, we do it with you. Certified partners will join once the first cohort has passed and is listed.
Read before your security review.
- Security overviewOne page for your reviewers: where data lives and goes, access levels, what isn’t there yet, and the license.
- Privacy and securityWhere the data lives, what agents can do without asking, and how to report a vulnerability.
- Open sourceThe license, the repository and how to build Murage from source.
Try it on one computer first.
Murage is free. Download it, build a team for one department and see it work before you roll it out.
No account needed · Runs on the AI plan you already pay for