MURAGE
How it worksFeaturesSolutionsUse casesComparePricingDocs
DownloadDownload
MURAGE

An AI Chief of Staff and a team that does the work. Free and open source, from Ferrox Labs.

Product

  • Features
  • How it works
  • Engines and apps
  • Privacy and security
  • Pricing
  • Murage Cloud
  • Download
  • Changelog
  • FAQ

Solutions

  • Solopreneurs
  • Founders and startups
  • Agencies
  • Ecommerce
  • Small business
  • Creators and educators
  • Developers
  • SaaS
  • Nonprofits
  • Consultants and freelancers
  • Customer success teams
  • Legal and professional services
  • Small teams
  • Sales teams
  • Operations managers
  • Industries
  • Use cases
  • Build your team

Compare

  • vs Claude Code
  • vs Codex (ChatGPT Work)
  • vs Claude (Cowork)
  • vs Paperclip
  • vs OpenClaw
  • vs Hermes Agent
  • vs Manus
  • vs Genspark
  • vs n8n
  • vs Zapier
  • vs Grok Bot
  • vs Viktor
  • vs Lindy
  • vs Tasklet

Resources

  • Docs
  • Team library
  • Skill library
  • AI Chief of Staff
  • How we test
  • Limits
  • Switching to Murage
  • Open source
  • Blog
  • Release notes

Company

  • About
  • Partners
  • Enterprise
  • Contact
  • Privacy
  • Terms
  • Cookies
© 2026 Ferrox Labs. Murage is open source under AGPL-3.0.
Customer support and success

Write the article. Stop answering the same question.

A support team reads your tickets, finds the questions customers keep asking that your help center doesn’t answer, and drafts the missing articles in your voice. You review and publish.

Download Murage

Free and open source. macOS, Windows and Ubuntu.

Help center articles

Read the last 90 days of support tickets. Find the ten questions we answer most that the help center doesn’t cover, and draft an article for each. Publish nothing.

Your Chief of Staff put a team on it

  • Support
  • Research
  • Copy
  • Quality Gate

10 missing articles

  • 1,240 tickets read from the last 90 days
  • Top gap: changing the billing email, 86 tickets
  • Next: exporting invoices, 61 tickets
  • 10 articles drafted, 3 with screenshots to take

Needs your answer

Review the billing email article first?

Reply to your Chief of Staff

An example of the job. Your team works on your own work.

A software company owner leaning back at his office desk with a glass of tea in afternoon light.

The team it puts on it.

Your Chief of Staff picks the specialists the job needs. Each one has its own role, instructions and engine.

  • Support

    Reads the tickets and groups the repeat questions

  • Research

    Checks each question against the articles you already have

  • Copy

    Writes the articles plainly, in your voice

  • Quality Gate

    Marks any step it couldn’t confirm from your docs

How it runs.

  1. Step 1Bring the ticketsYour support inbox through connected apps, or a ticket export.
  2. Step 2Find the gapsThe questions asked most, checked against your current help center.
  3. Step 3DraftsOne article per gap, with the steps written out and screenshots to take marked.
  4. Step 4You publishEdit the drafts and publish them in your help center.

What the team does, and what waits for you.

On their own

  • Group repeat questions
  • Find what the help center misses
  • Draft articles
  • Suggest which tickets to link them from

Waits for you

  • Publishing any article
  • Replying to customers

Start from a ready-made team.

From Murage’s library. Import one, look inside, and give it your brief.

  • Support StackPrepare ticket triage, onboarding guidance, retention follow-ups, and reusable responses in your brand voice.3 bots
  • Customer Success OrgReview account health, identify customers needing attention, and prepare renewal priorities and support follow-ups.4 bots

Skills the ready-made teams load.

What the library teams above bring with them. Skill Guard scans each one.

  • Ticket triageSort incoming tickets by urgency and draft replies from your support material.
  • Onboarding flowReview the steps from signup to a customer's first useful result.
  • Churn preventionReview signs of account risk and prepare follow-up drafts.
  • Membership ManagerGuide to membership program management including tier design, benefits, onboarding, engagement strategies, renewal campaigns, communications and events.
  • Operating rhythmIf they ask for a tool stack first, push back: rhythm before tools.
  • Discovery callIf the deck comes first, push back: discovery before pitch.

What you need.

What it takes to run this job. The Murage app is free; your AI provider bills you as usual.

  • Murage and an AI engine (your existing Claude or ChatGPT plan, or an API key)
  • A ticket export, or your support inbox through Flux Router credits or your own connected-apps key
  • Your current help center, pasted in or as a link

What you pay, and who you pay

Rather have it set up for you?

We build your first help center articles team with you, connect your tools and write your House Rules. Tell us what you need and we’ll quote before anything is booked.

Get it set up for youPartner program: apply for the founding cohort

Questions about help center articles.

Can it publish to Zendesk or Intercom?+

Only if your helpdesk is in the connected-apps catalog, and publishing waits for you. Most teams paste the drafts in.

How do I know the steps are right?+

It drafts from your docs and past good replies, and marks anything it couldn’t confirm so you can check it.

Put a team on something else.

  • Support queueRoutine replies drafted. Urgent tickets brought to you.
  • Write the SOPExplain a job once. The skill is saved, and you can open and edit it.
  • Review repliesA drafted reply to every review, and a ranked fix list.

Help center articles: hand it to a team tonight.

Give your first job to Murage.

Download the free app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.

Free · Download Murage

No account needed · Runs on the AI plan you already pay for