For one author, a team wiki is a folder of Markdown with full-text search and an ask box that pulls the best passages and has a model answer with links, which an agent builds in a sitting. Slite is sold to teams, though: live co-editing with comments and mentions, doc owners and a verification workflow that flags stale pages, permissions, and an assistant that searches Slack, Drive and other connected tools. The writing and searching are easy to copy; the sync, permissions and connectors take the weekend, and a solo build only helps if you are the main author.
Before you buildSlite has no free plan, only a 14-day trial. For solo notes, a plain Markdown folder in an editor you already own may be all you need.
Build me a personal team-style wiki to replace Slite. Requirements: - Node.js 22 + TypeScript: a Hono server with server-rendered pages and CodeMirror 6 for editing. `npm start` serves http://localhost:4840. WIKI_DIR in .env points at a folder of .md files (default ~/Wiki), which stays the source of truth. - Docs: YAML front matter with title, owner, tags, verified (a date) and review_every (days); folders are collections; [[wiki links]] with backlinks; images pasted into the editor are saved to WIKI_DIR/_files/. - Index: better-sqlite3 in ./data/index.db with an FTS5 table kept current by a file watcher (`chokidar`), plus embeddings of 400-token chunks in `sqlite-vec`, created through an OpenAI-compatible embeddings endpoint (EMBED_MODEL in .env). - Search: a box with FTS5 ranking, snippets, and the filters `tag:`, `owner:` and `stale:`. - Ask: take a question, fetch the top 6 chunks by combined FTS5 and vector score, send them to LLM_MODEL, and answer in Markdown with numbered links to the source docs. If nothing relevant comes back, say so instead of guessing. - Verification: a Needs review page lists docs past their review date; a Mark verified button writes today's date into the front matter; show a badge on every doc. - Sharing: up to 10 people with email and password (signed cookie), per-collection read or edit rights in ./permissions.json; export any collection as a zip of Markdown. - No telemetry, local-first; outbound calls go only to the embeddings and LLM endpoints in .env. - Out of scope: real-time co-editing, comments, Slack and Drive search, SSO, public sites. - README: a Docker run line, Ollama setup for local embeddings and answers, and a warning that answers are only as good as the docs.
Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.
The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Slite.
Add an importer to the wiki in this folder. Requirements: - `npm run import -- ./slite-export.zip` unzips a Slite Markdown backup, keeps its folder tree as collections and fixes internal links to [[wiki links]]. - Create front matter with title and today's date as verified; leave owner empty. - Copy images and files into WIKI_DIR/_files/ and rewrite their links. - Print a report of docs imported, links it could not resolve and files skipped. - Update the README.
Add a weekly digest to the wiki in this folder. Requirements: - `npm run digest` emails each doc owner the list of their docs past review_every, through SMTP settings in .env, with a link to each doc and its last verified date. - Docs with no owner go to a DIGEST_FALLBACK address. - Include a cron example for Monday morning. - Update the README.
Add a Slack slash command to the wiki in this folder. Requirements: - `/ask how do we rotate API keys` verifies the Slack signing secret, runs the same retrieval and answer pipeline as the web page, and replies in the channel with the answer and links. - Reply within 3 seconds with an acknowledgement and post the answer through response_url. - Only search collections that the mapped user can read. - Update the README with the Slack app setup.
Small teams pay for a wiki that stays trustworthy: owners, review dates and verified badges stop old pages from rotting, and the AI answers from the docs with sources. The editor is simple enough that non-technical colleagues actually write in it.
Estimate · Free on your own machine with a local model, or a $5 VPS plus a few dollars of API tokens for answers. The build is token usage on your agent plan. A 5-person team on Slite Basic pays $50 a month on the annual price.
| Plan | Monthly | Annual, per month | What you get |
|---|---|---|---|
| Basic | — | $10 | Unlimited docs, real-time editor with comments, doc verification workflow, Knowledge Management Panel, Ask (30 questions a month per seat, within Slite docs), 30 AI edits a month per user, 5 GB storage per user, 200 MB file uploads, PDF, Markdown and HTML export, MCP and API access. |
| Pro | — | $20 | Basic plus the Slite Agent, search across connected tools, doc fact-checking with suggested fixes, agent workflows (50 monthly credits per seat), unlimited AI writing assistant, OpenID SSO, custom domain for public docs, 10 GB per user. |
| Enterprise | custom | — | Pro plus reader-only seats, audit logs, SCIM, an SLA, priority support, a dedicated account manager, custom agent sources and migration help. |
Kinda. The core is a weekend build with the prompt on this page, but real gaps remain: A real-time editor where several people write together, with comments, mentions and notifications, The verification workflow and Knowledge Management Panel that keep a whole team's docs fresh.
About $10 a month on the Basic plan per seat, $120 a year (checked 2026-10-19).
A real-time editor where several people write together, with comments, mentions and notifications; The verification workflow and Knowledge Management Panel that keep a whole team's docs fresh; The Slite Agent and search across Slack, Google Drive and other connected tools; AI answers inside Slack, the Chrome extension and public docs with a custom domain; SSO, audit logs and enterprise permissions. If any of those matter to you, keep paying.
Yes: Docmost (open source), BookStack (open source), Wiki.js (open source).