Skip to content

Engineering

The spec, the board, and the thread — pointing at each other.

Engineering teams don't lose time to a missing feature. They lose it to the gap between the doc that says what to build, the ticket that says who's building it, and the thread where it quietly changed.

Start freeSee pricing

A task reaches Done. The project's bar rises. The goal hits 100%.

A spec that stays attached to the work

The design doc that no longer matches the thing that got shipped is a tax every team pays. Fora doesn't solve discipline, but it removes the excuse: the doc is one click from the board, on the same page as the work, in the same product.

  • The doc links the project; the project shows the doc back
  • Open the task, and the spec that governs it is right there
  • Backlinks, so you can see everything pointing at a decision
  • Blocks, slash commands, code blocks and images
DocsHow we ship
Saved Share
🚢

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.

A board without a ceremony

Fora's board is deliberately plain. If your team needs heavyweight agile tooling, keep it — this isn't trying to be that. If your team has been using a heavyweight tool to do something a board would have done, this is the board.

  • List and kanban, drag between columns
  • Subtasks with their own owners and dates
  • A side-peek editor that doesn't lose your place
  • No story points, no sprint ritual, no workflow builder
Hero animation pass
P2Launch Website
Launch site under 1s load
P1Launch Website

Decisions that survive the person who made them

Six months later, the question is always the same: why is it built this way? In most companies the answer left with someone. Here it's a search away, because the thread never got detached from the work it was about.

  • Every project has a chat whose roster is the project
  • Any message becomes a task, keeping the link back
  • Search finds the decision and the thread it was made in
  • Ask Fora AI why, and get the post it came from
Work Chat
Hana SatoStandup
Jamal CarterSSO walkthrough deck
Noor RahmanMobile tab bar

Questions

Does it integrate with GitHub?
A person's shelf can show their open pull requests. Deeper integration — branches and PRs attached to tasks — is honest future work, not something we'll pretend is shipped.
We already use Linear and Notion. Why change?
If both are working and the seams between them don't cost you anything, don't. The argument for Fora is that most teams are paying for the seams — in copied links, stale docs and status meetings — and haven't counted it.
Is there an API?
Yes, and org-wide export. Your data is yours and leaves in a format you can use.

Keep reading

Chat & feedThe company square, group chat, and windows that dockDocs & knowledgeThe handbook and the specs, written down and findableProjects, tasks & goalsBoards, subtasks, and progress that rolls up on its ownMeetings & virtual officeA floor you can walk, knock on, and split into roomsFora AIAsk the company a question and get the decision, with receipts

Run the whole company from one place.

Start free

Free for up to ten people. No card. Bring the company. Leave the stack.