In March 2026, Salesforce confirmed what most Quip customers had been bracing for: Quip is being retired. The official timeline gives existing customers about a year to plan. New paid, free, and trial accounts stopped being available to non-customers on February 17, 2026. Subscriptions cannot be renewed after March 1,
A state agency buys a cloud-hosted wiki. Three years in, a new data sovereignty regulation passes. The wiki vendor stores data across multiple regions and can't guarantee single-country residency. The agency has six months to migrate 8,000 pages of internal documentation to a compliant platform, while also
A regional bank's compliance team discovered that loan officers had been documenting workout strategies for troubled commercial loans in the company wiki. The wiki was hosted by a US SaaS vendor with servers split across three AWS regions. Some of those workout strategies included customer financial details, risk
A hospital's IT team set up a wiki for their clinical documentation group. It was supposed to hold care protocols, department procedures, and training materials. Within six months, clinicians had started using it for case discussion notes. Some of those notes included patient initials, medical record numbers, and
A government contractor spent nine months preparing for their FedRAMP audit. They had their system security plan in order. Their continuous monitoring was running. Their vulnerability scans were clean. Then the assessor asked where the team stored their internal documentation: architecture decisions, runbooks, security procedures, onboarding guides. The answer was
In most organizations, policies are scattered across shared drives, email threads, outdated PDF attachments, and that one Google Doc someone created three years ago that nobody can find anymore. An employee asks about the remote work policy and gets three different answers from three different managers, each referencing a different
Most product requirements documents don't get read. That's not a guess. Ask any engineer on your team when they last opened a PRD before starting work, and watch them try to remember. The silence tells you everything. PRDs have become a ritual. Product managers spend days
Obsidian is a Markdown-based knowledge management tool that stores everything as local files on your device. It has a plugin ecosystem, a graph view for visualizing connections between notes, and a loyal community that has built thousands of extensions for it. But Obsidian has real limitations that become obvious once
If you're evaluating MediaWiki and XWiki, you already have a certain kind of problem. You need something open-source. You probably need self-hosting. And you've likely looked at the lighter wiki tools on the market and decided they don't have the power you need for
Every few months, the same question shows up on Reddit, Hacker News, and a dozen Slack communities: should we use Notion or Coda? The thread fills with people who swear by one and dismiss the other. Both sides usually talk past each other because they're solving different problems.
Your developer docs are a mess. Maybe they live in a GitHub repo as Markdown files that nobody updates. Maybe they're scattered across a wiki that was never designed for API references. Maybe you have docs, but developers keep opening support tickets for things that are clearly documented,
Slab is a knowledge base tool for internal team documentation. It has a clean editor, unified search that reaches into connected tools like Slack and Google Drive, and a free plan covering up to 10 users. At $6.67 per user per month on paid plans, it's one