✍️ 필사 모드: Project Management Tools 2026 Shootout — Linear · Notion · Height · Plane · Jira · GitHub Projects · ClickUp · Asana · Monday Deep Dive

• Prologue — Asking again in 2026, "What tracker should the team use?"
• 1. Comparison axes — what should I look at?
• 2. Linear — the Apple of issue trackers
• 3. Notion — wiki and light PM, together
• 4. Height — the AI-native bet
• 5. Plane — the open-source Linear
• 6. Jira — still the enterprise default
• 7. GitHub Projects — on the same graph as code
• 8. ClickUp / Asana / Monday — the non-engineering camp
• 9. The shootout matrix — 9 tools x 9 axes
• 10. AI integration in practice — actually useful in 2026?
• 11. The self-host reality — should you actually self-host?
• 12. Real scenarios — how should a 10-person team choose?
• 13. Decision tree — "what should I adopt right now?"
• 14. Anti-patterns — common mistakes
• Epilogue — a tool is the shape of a workflow
  • Pre-adoption checklist
  • Next post
• References

Prologue — Asking again in 2026, "What tracker should the team use?"

Ask any engineering team in spring 2026 what PM tool they use, and 80% of answers cluster around three names: Linear, Notion, Jira. Within that 80%, satisfaction is bimodal. A 5-person team on Linear is delighted, a 200-person company that just bought Linear is hitting column limits, a 100-person team on Jira has redesigned its workflow three times this year. The 50-person startup that bolted a PM database onto the middle of their Notion debates "do we need to buy another tool" every week.

The truth about tools is simple. The shape of the workflow a tool enforces is the tool. Linear enforces cycles, keyboard shortcuts, a minimal state machine. Jira enforces workflow graphs and custom fields. Notion enforces freedom (and therefore the weight of freedom). Plane lets you take Linear's shape and self-host it. Height and ClickUp each try to bend that shape — Height around AI, ClickUp around the "everything app" thesis.

This post compares nine tools along the same axes.

1. Linear — the Apple of issue trackers. Keyboard-first, design-first.
2. Notion — wiki + light PM combo. Notion AI included.
3. Height — AI-native PM. Positioning after Height 2.0.
4. Plane — open-source Linear alternative. Self-hostable.
5. Jira (Atlassian Cloud) — still the enterprise default. Atlassian Intelligence on top.
6. GitHub Projects — the built-in one. Lives on the same graph as PRs.
7. ClickUp — the "everything app." Loved or hated, never ignored.
8. Asana — non-engineering-friendly. Loved by marketing and ops.
9. Monday.com — visual boards and automation recipes. Enterprise sales.

Prices and features move fast. Every number here is as of May 2026, and the decision framework should outlast the next pricing reshuffle. The point is the shape each tool enforces.

Choosing a tool is choosing a workflow. A workflow changes the personality of a team.

1. Comparison axes — what should I look at?

Nine tools, decomposed along nine axes.

Axis 1 · Strength of opinion about workflow. How hard does the tool push its own shape? Linear pushes hard — cycles, triage, minimal states. Jira pushes nothing (infinite custom). Notion starts from a blank page. Strong opinions mean low cost to adopt, high cost to escape.

Axis 2 · Keyboard-first. Cmd-K, J/K navigation, Tab to change state. Linear rewrote the standard. Height, Plane, GitHub Projects followed. Jira and Asana remain mouse-shaped.

Axis 3 · Depth of AI integration. The biggest 2026 axis. (a) First-class — Linear AI (triage, auto-labels, summary), Notion AI (Q&A, writing), Height's Copilot (its original bet), Atlassian Intelligence (Jira Cloud), Asana AI. (b) Second-class — GitHub Copilot reads Issues context. (c) Partial — Plane is OSS and can host its own LLM. ClickUp Brain.

Axis 4 · Self-host viability. Linear is SaaS-only. Notion is SaaS-only. Jira ships Data Center for self-host (expensive). Plane is properly open-source. GitHub Projects ships with GitHub Enterprise Server. ClickUp, Height, Asana, Monday are SaaS-only. Decisive when Korean public, EU GDPR, or finance compliance is in play.

Axis 5 · Pricing model. Per-seat per-month dominates. Linear's free tier and Standard, Notion's per-seat plus AI add-on, Jira's free-up-to-100 with Standard and Premium tiers, Plane's free self-host plus Cloud, GitHub Projects effectively free (bundled with GitHub), ClickUp's aggressive free tier, Height's Pro tier. Numbers in the table.

Axis 6 · Code (Git/PR) integration depth. Are issues and PRs on the same graph? GitHub Projects is integration by definition. Linear has deep GitHub/GitLab plus automatic PR mapping. Jira has Smart Commits, Bitbucket depth, and GitHub for Jira. Plane has bi-directional GitHub/GitLab. Notion is weak. Height ships PR previews inline.

Axis 7 · Wiki / docs integration. Are issues and docs in the same tool? Notion's main job is docs. Linear has Linear Docs as a separate product. Jira pairs with Confluence (separate product). Plane has Pages built in. ClickUp has Docs as a module.

Axis 8 · Friendliness to non-engineering. Can design, marketing, sales, CS use the same tool? Asana, Monday, ClickUp shine. Linear deliberately stays in engineering. Notion is universal. Jira extends with Jira Service Management.

Axis 9 · Mobile / offline / accessibility. Linear's mobile is genuinely usable. Notion mobile is fast. Height mobile is weak. Jira mobile is feature-heavy but heavy. ClickUp covers many platforms.

2. Linear — the Apple of issue trackers

Since launch in 2019, Linear has pushed one belief for seven years: "If every engineer saves five seconds every day, the team accelerates by the month." Every UI choice converges on keyboard shortcuts, instantaneous response, and minimalism.

What Linear does well:

• Cmd-K is the entry to everything. Create issues, change state, assign, label, filter — all from one shortcut.
• Cycles. Enforced 1-2 week windows. Replaces 80% of what scrum sprints did.
• Triage inbox. Externally created issues land in a single triage queue.
• Five workflow states. Backlog, Todo, In Progress, In Review, Done. Simplicity equals speed.
• GitHub, GitLab, Sentry, Slack integrations run deep. Merging a PR moves the issue to Done automatically.
• Linear AI in 2026. Auto-triage, dedup, label suggestions, cycle summaries, PR description drafts. Some features ship from the free tier.

The shape Linear enforces:

[Triage Inbox]
     |
     v
[Project (long-running) - Cycle (1-2 week)]
     |
     v
Backlog -> Todo -> In Progress -> In Review -> Done
                  ^                          |
                  +--- auto on PR merge -----+

Pricing (May 2026, per seat per month): Free with 250-issue limit, Standard about 10 USD, Plus about 14 USD, Enterprise via sales. AI activates seriously from Plus. See linear.app/pricing.

Weaknesses:

• SaaS only. No self-host. Bad fit for Korean public, finance, defense, parts of EU compliance.
• Too minimal for non-engineering. Marketing campaigns feel awkward in Linear.
• Custom workflows are intentionally limited. "Our seven special states" is not allowed (a feature, also a constraint).

Linear has strong opinions. Agree and you live in paradise; disagree and you should leave. The Linear of 2026 is no longer just a tool for tiny startups. Vercel, Cloudflare, Ramp, Mercury — series C and beyond — adopted it as standard.

3. Notion — wiki and light PM, together

Notion is not a "PM tool," it's a workspace. Wiki, docs, DB, light PM, notes — bet on doing them all in one place. The 2026 Notion went through two big shifts. First, Notion AI became a first-class citizen (search, Q&A, writing, summary, translation). Second, database views expanded to kanban, timeline, gallery, calendar, chart — bringing real light-PM functionality.

What Notion does well:

• DB plus page. An "issue" isn't just a row but a full page (i.e., a document). Rich context.
• Free-form schema. Add and remove fields freely. Reshaping the workflow weekly is cheap.
• Tight wiki integration. RFCs, ADRs, onboarding docs live in the same tool.
• Notion AI. Beyond autocomplete — RAG over the whole workspace. Spring 2026 enabled multi-model routing (Claude, GPT, Gemini backends).
• Public pages, embeds. Best-in-class external sharing.

The shape Notion enforces:

Workspace
  - Wiki (RFCs, ADRs, On-boarding)
  - Projects DB
      page-as-issue
  - Meetings DB
  - Tasks DB (personal)

Pricing (May 2026): Free, Plus about 12 USD, Business about 18 USD, Enterprise via sales. Notion AI is a separate add-on at about 8-10 USD per seat. See notion.com/pricing.

Weaknesses:

• Issue tracking depth is shallow. Cycles, burndown charts, automatic PR transitions are not at Linear or Jira level.
• Performance. Large workspaces report slow loads (still not fully resolved in 2026).
• The weight of freedom. Being able to redesign the workflow every week means someone has to redesign it every week.
• No self-host. Hard for data-sovereignty-bound orgs.

Notion shines for 5-30 person teams that need "wiki plus lightweight tracking" together. Past 50 people the usual move is to separate wiki from tracker (Notion + Linear/Jira).

4. Height — the AI-native bet

Height shipped from day one with the identity "PM tool with AI at the core." Since Height 2.0 the positioning is sharper still: Copilot is not assistive but operational. Auto-triage, auto-labels, auto-priority, extracting tasks from meeting notes, inferring "does this PR close this issue?" — AI does the first pass.

What Height does well:

• Copilot runs in the background. Inbound issues are auto-classified, assigned, dedup-checked.
• Natural-language search and filter. "P0 bugs we didn't close last week" as English.
• PR previews and inline comments. Code change visible inside the PM tool.
• Kanban, list, gantt, spreadsheet views. One data set, multiple views.

The shape Height enforces:

[Inbox - AI auto-triage]
     |
     v
[Tasks DB - AI auto-label / priority]
     |
     v
Plan -> In Progress -> Review -> Done
       +-- auto PR mapping --+

Pricing (May 2026): Free tier + Pro about 10-15 USD per seat. AI activates seriously from Pro. See height.app/pricing.

Weaknesses:

• Smaller user base. Thin ecosystem versus Linear or Jira. Fewer integrations and plugins.
• AI consistency. When auto-triage misclassifies, it can break things faster than a human.
• No self-host.

Height bets on "we can delegate the cognitive load of PM to AI." Teams that buy that bet love it. Teams that don't find it over-automated.

5. Plane — the open-source Linear

Plane started with a simple bet: take Linear's shape and make it open source. Through 2024-2025 it hit GA, and by 2026 it's mature enough to deploy seriously in self-hosted environments. AGPL license, Docker Compose / Kubernetes deployment, Postgres + Redis + S3-compatible storage backend.

What Plane does well:

• Self-host is first-class. Run it on your own infrastructure. Solves data sovereignty and compliance.
• Shape resembles Linear. Cycles, modules, pages, views. Low learning curve.
• Plane Cloud option. If self-hosting is too much overhead, there's a SaaS version too.
• Bi-directional GitHub and GitLab.
• Plane AI module in 2026. Attach your own LLM (Ollama, vLLM) as the backend. Keeps data sovereignty while still adopting AI.

The shape Plane enforces:

Workspace (self-hosted or Cloud)
  - Projects
      - Issues
      - Cycles (1-2 week)
      - Modules (long-running)
      - Pages (wiki)
  - Views (saved filters)

Pricing (May 2026): Self-host free under AGPL. Cloud free tier + Pro about 8-10 USD/seat + Enterprise. See plane.so/pricing.

Weaknesses:

• Thin ecosystem. Far fewer integrations than Linear or Jira.
• Self-host operational cost. Postgres backups, Redis ops, S3 costs, upgrade noise. You give up SaaS convenience.
• AI is not cutting edge. You can route to your own LLM, but the polish of Notion AI or Linear AI is missing.
• AGPL license matters. Internal hosting is fine; redistributing as SaaS needs legal review.

Plane is a strong answer when "we need Linear's workflow on our own infra" is an explicit requirement. Adoption is rising in Korean public sector, finance, and EU GDPR-strict orgs.

6. Jira — still the enterprise default

Jira is not dead. In 2026 most engineering orgs over 1000 people still run on Jira. Not because it's heavy, but because that weight is an asset at scale. Custom workflow graphs, the permission model, Insight and Forge plugins, Data Center self-host, the Confluence pairing, Jira Service Management — all together it's the enterprise Atlassian stack.

What Jira does well:

• Unlimited workflow customization. Design states, transitions, conditions, validators, post-functions as a graph.
• Permissions, audit logs, SAML SSO, SCIM. Compliance as a first-class concern.
• Atlassian Intelligence (2025-2026). Auto-summary, draft creation, priority recommendations, natural-language search across Jira Cloud. Serious in Premium and above.
• Forge and Connect plugins. Thousands of integrations and automations.
• Data Center self-host. Enterprise-grade self-host option (expensive, needs ops team).
• Confluence pairing. Wiki, docs, RFCs on the same Atlassian account.
• Jira Service Management. ITSM, CS, internal helpdesk extension.

The shape Jira enforces:

Project
  - Workflow Graph (custom)
      To Do -> In Progress -> In Review -> Done
      (+ custom states / transitions / conditions / post-functions)
  - Boards (Scrum, Kanban)
  - Sprints (optional)
  - Custom Fields (many)

Pricing (May 2026 Jira Cloud, Free up to 100 seats): Standard about 8-9 USD/seat, Premium about 16-17 USD/seat, Enterprise via sales. Atlassian Intelligence from Premium. Data Center self-host has its own license model. See atlassian.com/software/jira/pricing.

Weaknesses:

• Heavy. Page loads, issue creation, filter responses run 5-10x slower than Linear.
• Constantly shifting UI. "Next-gen", "Team-managed", "Company-managed" confusion.
• The cost of custom. Being able to design the workflow means someone has to. A "Jira admin" becomes a real job.
• Overkill for small teams. Jira on a 10-person team is using a hammer for a thumbtack.

Jira still makes sense at 1000+ people. Under 100, most teams escape to Linear or Plane.

7. GitHub Projects — on the same graph as code

GitHub Projects v2 went GA in 2022 and has steadily matured through 2026. Default integration, built in, sitting on the same graph as code. Issues, PRs, Projects share one entity model.

What GitHub Projects does well:

• PRs and issues are on one graph. No bridging needed. Closes #123 just works.
• No per-user surcharge. Bundled with GitHub.
• GraphQL API and GitHub Actions automate everything. Custom workflows as code.
• Board, Table, Roadmap views.
• GitHub Copilot sees issue context. AI assist on PR review and issue triage.
• Self-host via GitHub Enterprise Server.

The shape GitHub Projects enforces:

Repository / Organization
  - Issues (same entity)
  - Pull Requests (same entity)
  - Discussions
  - Projects (curating the above)
      - Board / Table / Roadmap
      - Custom Fields

Pricing (May 2026): GitHub Team about 4 USD/seat, Enterprise about 21 USD/seat. Projects included in every tier. See github.com/pricing.

Weaknesses:

• Shallow PM. Cycles, burndown, complex workflow graphs are weak.
• Docs are separate. GitHub Wiki is clearly a secondary product.
• Bad fit for non-engineering. Hard to pull design or marketing into GitHub Projects.

GitHub Projects fits engineering-only teams with a hard requirement of "code and issues on the same graph." 5-50 person OSS projects, devtool companies, anything already deep in GitHub.

8. ClickUp / Asana / Monday — the non-engineering camp

These three are used more by marketing, CS, and operations than by engineering.

ClickUp — bills itself as "the everything app." Tasks, Docs, Goals, Whiteboards, Time tracking, Chat, Email, even CRM under one roof. Loved by teams who want everything in one tool; hated by teams allergic to feature bloat. In 2026 ClickUp Brain (AI copilot) is standard. Free tier plus about 7-12 USD/seat.

Asana — the easiest tool for marketing, design, and operations. Clean list, board, timeline, calendar views. Asana Intelligence (AI) shipped seriously in 2026. About 10-25 USD/seat. Engineering often runs Asana alongside Jira or Linear.

Monday.com — color and automation recipes are the strengths. "If status changes, then notify Slack" type automations designed visually. Strong for marketing campaigns and sales pipelines. Monday Dev exists for engineering but adoption is low.

What the three share: engineering is not a first-class citizen here. Candidates when a company wants design, marketing, and CS on the same tool. Engineering usually keeps Linear, Jira, or Plane alongside.

9. The shootout matrix — 9 tools x 9 axes

Every number is May 2026. Pricing is the most common paid tier, per seat per month USD.

In one line: Linear and Plane push opinionated engineering workflows, Notion and ClickUp leave it free, Jira leaves it customizable, GitHub Projects is one with code, and Asana/Monday lean non-engineering.

10. AI integration in practice — actually useful in 2026?

AI is the marketing keyword every PM tool reaches for. The gap between "useful automation" and "demo automation" is still wide.

Linear AI (Plus and above). The most restrained integration. Auto-triage, dedup, cycle summary, PR description drafts. Automation runs in places you don't notice. You don't have to explicitly invoke it for it to help. Limitation: deep automation (modifying the workflow itself) is restricted.

Notion AI (add-on). RAG over the whole workspace. Writing, summarizing, translating, generating tables. Spring 2026 enabled multi-model routing (Claude, GPT, Gemini), boosting answer quality. Limitation: stronger at content generation and search than at task automation.

Height Copilot. Bet on AI as operator from day one. Auto-triage, auto-labels, auto-priority. When it works, cognitive load drops. When it misclassifies, you can break things faster than a human. Plan 6-8 weeks of tuning at rollout.

Atlassian Intelligence (Jira Premium and above). AI across Jira, Confluence, Bitbucket. Issue summaries, drafting, priority recommendation, natural-language search. The deepest enterprise integration. Limitation: only really activates from Premium.

ClickUp Brain. AI on top of ClickUp data. Task drafting, summary, auto-assign, doc writing. The everything-app's everything-AI.

Asana Intelligence. Smart summary, smart status reports, task creation. Marketing and ops feedback is positive.

Plane. Official hosted AI module plus the ability to attach your own LLM (Ollama, vLLM). Fits orgs that want data sovereignty alongside AI. Limitation: less polished UX.

GitHub Projects. No native AI, but GitHub Copilot sees issue context. Useful for PR review, issue triage, summarizing code changes.

The 2026 truth: AI genuinely helps in triage, labeling, summary, and search. AI is still partial at workflow design, priority decisions, and assignment.

11. The self-host reality — should you actually self-host?

Data sovereignty, compliance, cost — these push some orgs toward self-host. But self-host is operational cost more than license cost.

Self-hostable tools:

• Plane — AGPL. Docker Compose / Kubernetes. Postgres + Redis + S3.
• Jira Data Center — enterprise license. Postgres, OpenSearch, CDN, load balancer. Ops team required.
• GitHub Enterprise Server — GitHub Projects included. Separate license. VM or OCI containers.

Non-self-hostable:

• Linear, Notion, Height, ClickUp, Asana, Monday are SaaS-only.

Real cost of self-host (Plane reference):

• Infra (VMs, DB, S3, backup): 50-500 USD/month at typical scale
• Operator time (upgrades, backup verification, incident response): 4-8 hours/month
• Downtime risk
• Cost of building integrations and extensions

Recommendation: if legal or security requirements are not clear, stay on SaaS. Self-host only when data sovereignty is part of the business decision. It makes sense for Korean public sector, finance, defense, EU GDPR-strict orgs, and healthcare.

12. Real scenarios — how should a 10-person team choose?

Enough abstraction. Real scenarios.

Scenario A — Seed / Series A startup, 8-15 people (engineers 6-10, design/PM 2-5). Default is Linear + Notion. Issues in Linear, RFCs and onboarding and meeting notes in Notion. Around 22 USD/seat. As the team grows past 6-8 months, Notion becomes wiki-only and Linear becomes tracker-only.

Scenario B — Series B/C, 30-80 people. Linear + Notion still works. As non-engineering grows, Notion expands to company-wide wiki, OKRs, meeting management. With AI add-ons, expect 30-35 USD/seat all-in.

Scenario C — Series D and beyond, 150+ people. Forks. (a) Stay on Linear — Vercel and Cloudflare pattern. (b) Move to Jira — when enterprise SSO, audit, permissions, SOC2 become loud. (c) Run both — engineering on Linear, non-engineering on Jira or Asana. 25-50 USD/seat all-in.

Scenario D — Korean public sector or finance, self-host required. Plane (self-hosted) + Wiki. Plane handles cycles, issues, pages. If a separate wiki is needed, run Outline or BookStack alongside. Ops cost matters but license cost is near zero.

Scenario E — 100% engineering OSS project. GitHub Projects only. Issues, PRs, projects on one graph. Adding another tool is overkill. Copilot helps with issues and PRs.

Scenario F — Marketing-heavy / ops-heavy company. Asana or ClickUp + Linear/Jira. Non-engineering on Asana or ClickUp, engineering on Linear or Jira. Sync between them (Zapier, n8n, custom) costs.

Scenario G — All-in on AI automation. Height or Linear + Notion AI. Height bets on AI as operator, Linear plus Notion AI bets on AI as assistant. Pick based on team trust level.

13. Decision tree — "what should I adopt right now?"

Start: team size and domain?

- 5-15 people, engineering-heavy
    -> Linear + Notion (default)
    Heavy on AI automation? -> Linear + Notion AI, or Height

- 15-50 people, mixed engineering and non-engineering
    -> Linear + Notion (engineering-driven)
    Larger non-engineering? -> add Asana or ClickUp

- 50-150 people, departmentalized
    -> Linear (eng) + Notion (wiki) + Asana/ClickUp (non-eng)
    Or Jira Software (eng) + Confluence (wiki)

- 150+ people, enterprise compliance loud
    -> Jira + Confluence + JSM (Atlassian full stack)
    Or stay on Linear (Vercel and Ramp pattern)

- Self-host required by law
    -> Plane (eng) + Outline/BookStack (wiki)
    Or Jira Data Center + Confluence Data Center

- 100% OSS / GitHub-native
    -> GitHub Projects only

- Marketing, CS, ops are the main business
    -> Asana / Monday / ClickUp anchored
    Engineering keeps Linear or Jira separately

14. Anti-patterns — common mistakes

Anti-pattern 1 — "Put everything in Notion." Works fine at 5-15 people. Past 30 people you lose cycles, burndown, priority, automatic PR transitions, and it falls apart. Separate wiki from tracker.

Anti-pattern 2 — "Jira on a 10-person team." Jira's customization is an asset at 100+. On 10 people it eats a week setting up permissions, fields, and transitions. Use Linear or Plane.

Anti-pattern 3 — "Run marketing campaigns inside Linear." Linear deliberately stays in engineering. Marketing campaigns and sales pipelines feel awkward. Run Asana, Monday, or Notion alongside.

Anti-pattern 4 — "Trust Height's AI 100%." When auto-triage misclassifies it can break things faster than a human. Plan 6-8 weeks of human review at rollout.

Anti-pattern 5 — "Plane self-hosted, backups later." Self-host cost is operational. If backups, upgrades, incident response are not designed up front, you regret it within a year.

Anti-pattern 6 — "It ships with AI, adopt it." AI in beta, AI English-only, AI weak in your domain language — all dilute the win. Do a 2-4 week pilot first.

Anti-pattern 7 — "Switch tools every year." PM migration is expensive. Moving issue history, integrations, automation, and habits takes 3-6 months. Pick a tool you'll keep for 2+ years.

Epilogue — a tool is the shape of a workflow

Back to the start. The shape of the workflow a tool enforces is the tool. Linear enforces cycles and minimalism. Jira enforces the freedom and weight of unlimited custom. Notion enforces the freedom and burden of the blank page. Plane lets you take Linear's shape with infra control. Height tries the shape of "AI as operator."

Choosing a tool is choosing a workflow. A workflow changes the personality of a team. Answer "what shape do we want to work in?" first, then pick the tool closest to that shape. Go the other way and the tool reshapes the team on its own terms.

Pre-adoption checklist

• Have you written down team size now and projected in 12 months?
• Have you decided whether non-engineering uses the same tool?
• Have you confirmed whether self-host is a legal or policy requirement?
• Have you decided whether AI is first-class or assistive?
• Have you decided whether wiki and tracker live together or apart?
• Is there a 2-4 week pilot plan post-adoption?
• Have you estimated migration cost (issue history, integrations, automations)?
• Have you named the tool admin (who owns the workflow)?
• Is this a tool you'd keep for 2+ years?

Next post

The next post tackles "Engineering management in the AI era." When AI writes 70% of the code, how should 1:1s, reviews, onboarding, evaluations change? Which parts of the manager's job does PM-tool automation replace, and which parts will it never touch?

References

• Linear — linear.app, pricing, Linear method
• Notion — notion.com, pricing, Notion AI
• Height — height.app, pricing
• Plane — plane.so, GitHub, pricing
• Jira (Atlassian Cloud) — atlassian.com/software/jira, pricing, Atlassian Intelligence
• GitHub Projects — github.com/features/issues, pricing, Projects docs
• ClickUp — clickup.com, pricing, ClickUp Brain
• Asana — asana.com, pricing, Asana Intelligence
• Monday.com — monday.com, pricing, Monday AI
• Atlassian — Data Center
• GitHub Enterprise Server — github.com/enterprise
• Outline (open-source wiki) — getoutline.com
• BookStack (open-source wiki) — bookstackapp.com