Know
If it's not written down, it didn't happen.
Two kinds of writing live in Fora. Docs are where the work gets thought through. The Knowledge Library is where the company's settled answers live — the handbook, the policies, the onboarding — and it looks official because it is.
Knowledge Library
What's true here, who says so, and when they last checked.
Design 1
Engineering 2
People 2
How we ship
We ship from main. Every change lands behind a flag and is off for everyone.
Flags flip on Tuesday and Thursday at 10:00 Toronto. Nothing flips on a Friday, and nothing flips during launch week without Marcus.
If it isn't written in Fora, it did not happen: the release note is the source of truth, and it links the task it shipped.
Team — we're officially announcing FORA on October 12. All hands behind @Sarah Chen's launch plan.
The Knowledge Library, the doc behind it, and a search that finds the decision.
A library, not a folder of files
The failure of every company wiki is that a page nobody has confirmed in two years looks exactly like a page confirmed this morning. Fora puts the owner and the date on the shelf, so you can tell at a glance which answers are still answers.
- Sections by subject — policies, guides, onboarding
- Every entry shows its owner, when it was last true, and who's read it
- An Official label, so a settled answer doesn't read like a draft
- Nothing stale: the library tells you what hasn't been touched
Knowledge Library
What's true here, who says so, and when they last checked.
Design 1
Engineering 2
People 2
A doc editor that knows what it's about
Writing in Fora feels like the editors people already like. What's different is that a doc can point at the project it specifies, and the project shows the doc back. Open the task and the spec is right there — nobody has to remember to paste a link.
- Blocks: headings, lists, todos, toggles, quotes, callouts, code, images
- Slash commands to insert, drag handles to reorder
- @ a person, / link a task, project, goal or another doc
- Links are live pills, and they work in both directions
How we ship
We ship from main. Every change lands behind a flag and is off for everyone.
Flags flip on Tuesday and Thursday at 10:00 Toronto. Nothing flips on a Friday, and nothing flips during launch week without Marcus.
If it isn't written in Fora, it did not happen: the release note is the source of truth, and it links the task it shipped.
Private until you share it
A doc you started this morning is yours until you decide otherwise. The server enforces it, so a doc you haven't shared doesn't appear in anyone else's list, and doesn't appear in their search either.
- New docs are private by default — your drive, not the company's
- Share with a person, a group, or the whole workspace
- Read-only links for people outside the company
- Owners and admins never lose access to their own docs
Everything in it
- Knowledge Library with sections by subject
- Owner, last-updated and reader count on every entry
- Block editor with slash commands and drag-to-reorder
- Headings, lists, todos, toggles, quotes, callouts, code, images
- Text colour and highlight
- @ mentions and / links to any object
- Bidirectional backlinks
- Folders, list and gallery views
- Private by default, with group and workspace sharing
- Read-only public links
- Global search across docs, posts, tasks, people and meetings
- Markdown export
Questions
How is this different from Notion?
Can we import our existing wiki?
Who can see what I write?
Keep reading
Run the whole company from one place.
Start freeFree for up to ten people. No card. Bring the company. Leave the stack.