Ship it, and keep the docs true.
Tickets, cycles and GitHub pull requests in one app, with Iris, who updates your help center with real screenshots each time you ship.
Free plan, no card. Your Jira or Linear tickets come over with the same keys and numbers.
InputKit runs its help center in Alori.
InputKit sells software to 2,000 service businesses. Every help center article came over from Intercom in one click, next to its CRM, calls, support chat and email.
Read InputKit's story →One app instead of your build-and-docs stack.
From a bug report to a fixed feature and a fresh article.
Here is one ticket going from a customer's message to a merged pull request and an updated help article, without leaving Alori.
- 1A customer's report lands in Triage
- 2It goes into this cycle
- 3A pull request moves it on its own
- 4Iris updates the help article
- 5Customers find the answer at /help
What changes on Monday.
- 01
BeforeTickets in one tool, pull requests linked by hand
With AloriA pull request that names DEV-7 moves the ticket on its own
- 02
BeforeHelp articles that show last quarter's screens
With AloriIris retakes the screenshots that changed after each release
- 03
BeforeA seat to buy for every person who files a bug
With AloriUnlimited users, so support and sales file tickets too
A tracker your whole team can use.
Tickets have a key, a team, a type, a priority, labels and links. Work from a list or a board, save the views you use, and start each ticket from a template.
- Views like Mine, Triage and Cycle, plus your own.
- Cycles roll unfinished tickets into the next one.
- Projects with milestones show how far along you are.
GitHub moves the ticket for you.
Add your repositories once. A pull request that names a ticket shows on it, moves it to in progress when opened and to done when merged.
- One repository serves every team.
- Pull requests are listed on the ticket.
- Triage rules and auto-close keep the backlog clean.
Docs that keep up with the product.
Iris reads what shipped, opens your product on her own computer and updates the help articles it touches, with a fresh screenshot under each step, in English and French.
- She only retakes the pictures that changed.
- Her first drafts wait for your Publish.
- A monthly limit keeps her cost in check.
Add up your tools. See what you save.
Add the tools you pay for. We count their public prices for your team, take off your Alori plan and show what you save.
Today
Client experience
Zendesk
Support email, tickets and a help center
Suite Team plan, 5 users
$3,300 a year
Work delivery
Linear
Triage, cycles and tickets next to your customers
Basic plan, 5 users
$600 a year
Office time
Calls, emails and paperwork Alori's bots take on
Potential savings
$6,892 a year
69% of what you spend today.
- Client experience$3,300Zendesk
- Work delivery$600Linear
- Office time$5,9805 h a week at $23 an hour, estimated
- Alori Business plan−$2,988
Estimated from public list prices checked in November 2026, billed yearly when that's cheaper. Your results will vary. Calls, texts, video and AI work use your plan's monthly credits. What Alori replaces, tool by tool
Change it by asking.
Your app isn’t frozen on day one. Write what you need, the way you’d text it. Alori makes the change and shows you before anything goes live.
- Show me the tickets in this cycle that haven't started
- Make a ticket template for bug reports
- Which tickets took longest to close last month?
- Have Iris run her help center round now
The full guide
Everything above, in detail: how it works, what it replaces and what it does not.
Short answer: Alori gives a software team one place to plan and ship: tickets with teams, labels, templates, links and saved views, cycles and milestones, and GitHub pull requests that move tickets on their own. Next to it sits your help center, in English and French, and Iris, the help center guardian, who watches what you ship and updates the articles with real screenshots. Your Jira or Linear tickets come over with the same keys and numbers, and everyone on the team gets a login on every plan.
The problem: the docs fall behind the product
A small software team usually ships from a stack of separate tools:
- An issue tracker like Jira or Linear, paid per seat.
- A docs tool like GitBook, Zendesk Guide or Intercom articles for the help center.
- GitHub, where the real work lands, linked to the tracker by hand.
- Somebody's memory to update the help article after each release, which mostly doesn't happen.
The product moves every week. The help center shows last quarter's screens, and customers ask the support team what the docs should have told them.
What Alori does for software teams
| What you need | What Alori does | What it replaces |
|---|---|---|
| Track the work | Tickets with keys like DEV-7, teams with their own steps, labels, types, priorities, sub-tickets and links (blocks, related, duplicate) | Jira, Linear |
| Find the right list fast | A list or a board, views like Mine, Triage and Cycle, your own saved views, filters and keyboard shortcuts | Tracker filters |
| Start tickets the same way | Templates in New ticket fill in the title, details, type, priority and labels | Issue templates |
| Plan the next weeks | Cycles of 1 to 4, 6 or 8 weeks where unfinished tickets roll over, optional sizes, and projects with milestones | Sprints, epics, roadmaps |
| Tie tickets to code | Watched GitHub repositories: a pull request that names DEV-7 shows on the ticket, moves it to in progress when opened and to done when merged | Jira and Linear GitHub apps |
| Keep the tracker tidy | Triage rules, people who take triage in turn, auto-close and auto-archive, and Insights on lead time, cycle time and more | Tracker automations and reports |
| Keep the docs true | A help center at /help with sections, your own order and English and French articles, kept up to date by Iris | GitBook, Zendesk Guide, Intercom articles, manual doc updates |
How it works
- Bring your tracker. In Import data, connect Linear or Jira Cloud. Tickets keep their keys and numbers, with comments, history, cycles and projects. Import again catches what changed until you switch.
- Set up your teams. Each team has a key like DEV or SUP, its own steps from Triage to Done, and its own cycles.
- Plan a cycle. Pick the tickets for the next weeks. The Cycle view shows the scope, what started and what's done. What isn't finished moves to the next cycle.
- Link GitHub. In Settings › Tickets › GitHub, add your repositories. Name the ticket in a pull request and the ticket moves on its own.
- Turn on Iris. Give her your product's address and your repository. She signs in to your product with her own email, on her own computer.
- Ship as usual. Each day, Iris looks at what shipped, writes or updates the help articles it touches, takes a fresh screenshot of each step, and translates them.
Iris keeps the help center in step with the product
Iris is the help center guardian, an AI teammate you turn on from your bots. She reads your repository to see what shipped, opens your product in her own browser, and writes the article a customer needs, with a picture under every step, in English and French. When a screen changes, she compares the published picture with the screen today and only retakes what changed.
She earns trust like a new hire: her first drafts come to you as a card with one Publish button. Once you approve a couple, she publishes on her own and tells you what she did. A monthly limit on her credits keeps her cost in check. See how the self-updating help center works with Claude Code too.
Tickets that know the customer
A ticket can start from a customer's conversation, so the bug report and the person who reported it stay together. The customer gets an email when the ticket moves, and a comment can go to them too. Feature requests and feedback can feed your roadmap: see product feedback to roadmap.
What Alori doesn't do yet
- No custom fields on tickets, workflow transition rules or a query language like JQL.
- No customer portal: customers write in, and the team files the ticket from their conversation.
- Jira Data Center (Jira on your own servers) can't be imported yet.
- AI developers that write code on their own computer and open pull requests are only in Alori's own testing for now, not open to every account.
- No public docs site separate from the help center, like GitBook's versioned docs.
Who it is for
Software companies and SaaS teams that plan and ship in short cycles, and agencies that build software for their clients. See Tech and SaaS.
Questions
Another question? Ask it when you start.
Yes. Jira Cloud and Linear workspaces come over with the same keys and numbers, comments, history, cycles and projects. Import again brings only what changed, and Undo import takes it all back out.
Yes. Add a repository in Settings › Tickets › GitHub. A pull request that names a ticket shows on it, and moves it to in progress when opened and to done when merged.
Your product's address, your GitHub repository and a way in, like an invitation to her own email address or a demo login. She does the rest.
Not at first. Her drafts come to you with a Publish button. After you approve a couple, she publishes on her own and lists what she published.
Alori is free to start, no card needed. Solo starts at $99 a month and Business at $249, with unlimited users on every plan. Iris uses your plan's credits. See pricing.
Related pages
See all →- Get foundYour website, campaigns, posts, reviews and leads in one place
- SellFrom the first call to the signed quote and the upsell
- Support customersChat, email, texts, calls and tickets in one place
- Deliver the workDeliver what you sold, on time
- Get paidBill the work and get paid on time
- Run my teamFiles, hours, time off and Team chat