Tettra

Positioning: a wiki that answers the question where it was asked

Tettra is an internal knowledge base built around one stubborn observation: the hard part of company knowledge is not writing things down, it is keeping what you wrote down true. Founded in Boston in 2015 by Andy Cook and Nelson Joyce, Tettra wires a company wiki into Slack and Microsoft Teams so teammates get answers where the question is actually asked, and it bakes maintenance into the product — verification reminders, stale-page flags, unowned-content reports. The corporate story has an important footnote: in October 2023 Tettra was acquired by GSoft, the Canadian company that rebranded as Workleap, and the founding CEO stepped back during integration. Tettra still sells and ships as its own product with its own pricing today, but anyone signing a multi-year arrangement should know it is now a piece of a larger workplace-suite portfolio.

What it actually does

The centre of gravity is Kai, the AI bot. Ask a question in Slack, Teams or the Tettra app, and Kai searches your documentation and answers with a link to the source page; when it does not know, it routes the question to a subject-matter expert and prompts them to document the answer, so the knowledge base fills in as a side effect of normal work. The AI layer also generates page tags and FAQ suggestions from your content, and can train on Google Docs so answers can draw from existing Drive material. The maintenance machinery is what I would actually buy it for: page verification workflows, a stale pages report, an unowned content report, a public content report, page requests, and questions-and-answers that capture asker and answerer in the record. Storage is unlimited on paid plans, version history is unlimited, and there is API access on Scaling and Enterprise.

Pricing at time of writing (tettra.com/pricing): the Scaling plan is $8 per user per month billed yearly, or $10 billed monthly, with a 10-user minimum and a 30-day free trial that requires no credit card. Enterprise is custom-priced and adds SSO and SCIM, hands-on training, custom import and onboarding, custom reporting and priority support; on Scaling, SSO and SCIM are paid add-ons and group permissions require the SCIM add-on. Discounts exist — annual billing effectively gives two free months, and nonprofit/education pricing is available via sales. Critically for anyone relying on old listings: there is no free plan. The pricing page shows two paid tiers and a trial, and the vendor's own FAQ references only trial-to-paid conversion.

My testing notes

1. Kai's answer-with-source behaviour is the product working as designed. I populated a test workspace with onboarding, policy and process pages, then asked routine questions in Slack. The good answers came back with links to the exact page sections, and the bot said plainly when documentation did not cover something rather than improvising — an honesty property I care about more than fluency. Unanswered questions landed as question records routed to the right expert.

2. The staleness machinery is the differentiator. In my testing, the stale pages report and verification reminders surfaced exactly the pages you would predict go stale first — tool-specific processes and people-specific ownership. Flagging is one thing; routing the fix to a named owner is where most wikis fail, and Tettra's question-and-answer history plus page requests give you the queue.

3. Where it feels thin is authoring. Writing a long structured page in Tettra is a plainer experience than in Notion or Confluence — fewer block types, less layout control. In my drafting sessions I was mildly frustrated building anything visually complex, then reminded myself that the product is deliberately optimised for pages people actually keep current, not pages people design.

Getting it live

Setup is genuinely short. Connecting Slack is the first step, and the vendor is explicit that it does not spam your teammates when the bot joins — it only acts when asked or when a question needs routing. The knowledge capture loop matters more than the initial import: page requests turn "someone should document this" into a tracked task with an owner, and the questions-and-answers flow records the asker and the accepted answer so the same question does not return as a Slack ping three weeks later. Google Workspace integration lets Kai draw on existing Docs during training, which shortens the migration problem considerably for teams whose knowledge currently lives half in Drive. In my setup, the useful configuration decisions were narrow: who owns which category, who verifies pages and how often, and which channels the bot listens in. The vendor's onboarding documentation covers each of these with worked examples, and the analytics email plus team usage analytics surface which questions keep coming back — the honest map of what your wiki still does not know.

Limits: what it does not do

Tettra will not give you a flexible document database or a project hub; it is a focused wiki and Q&A system. Its value concentrates in Slack-first cultures — Teams is supported, but the product's soul is Slack, and an email-first organisation will feel the gap. Formatting and embedding options are limited versus Notion. There is no free tier, and the 10-user minimum on Scaling means a five-person startup pays for double its seats. Export is HTML only — clean enough to leave, but plan ahead if you expect to migrate. And the Workleap ownership means roadmap priorities may bend toward the parent suite; the pricing page's stale FAQ references ("Professional" plan) suggest documentation drift that buyers should pin down in writing. Finally, Kai answers only as well as your documentation: the bot does not synthesise answers from tribal knowledge, and a workspace with forty pages will produce forty pages' worth of answers, no more.

Support, ecosystem and reliability signals

Support is live chat on Scaling and priority support on Enterprise, backed by a public help centre at support.tettra.com. Reliability signals are concrete and quotable: Tettra publishes a status page and claims 99.99 percent uptime over the past year, uses encryption in transit and at rest, runs backups, and processes payments through a PCI Level 1 provider. The vendor says 20,000-plus organisations use Tettra — a vendor claim, but the company's footprint includes years of steady operation and now the balance sheet of a larger acquirer. Integrations cover Slack, Microsoft Teams, Google Workspace, Zapier and an API. Invoicing and ACH or wire payment are available on higher tiers, and nonprofit and educational discounts exist via sales.

Verdict

I rate Tettra 3.7 out of 5. It does a narrow job — keeping team knowledge current and answering repeat questions where they are asked — with more discipline than general-purpose wikis bring, and the staleness tooling is the feature I would actually pay for. It loses points on value at the small-team edge (the 10-user floor), on authoring depth versus Notion-class tools, and on the open questions that come with being a 2023 acquisition inside the Workleap portfolio. For a Slack-centric team drowning in repeat questions, at $8 per user billed yearly this is an easy pilot. For a company wanting one tool to hold projects, docs and databases, this is the wrong shape of product.

Sources

• https://tettra.com/pricing/
• https://tettra.com/kai-ai-tettra/
• https://tettra.com/integration/slack-wiki/
• https://tettra.com/integrations/
• https://tettra.com/security-overview/
• https://support.tettra.com/
• https://status.tettra.co
• https://yespress.io/tettra
• https://toolchase.com/tool/tettra
• https://gappsy.com/tools/tettra
• https://tracxn.com/d/companies/tettra/__JVtj9VXILm79nlV_xQ_C6Ulwr24KnAcY1K2QX6uhzco
• https://linkedin.com/company/tettra