Skip to content
Takeida
Start free

One place for what your team knows, says and gets done

Start freeSee the whole system

Message

Send a person, a frame or a document, not a link.

Design

Design with the conversation open beside it.

Concept

See how everything your team knows connects.

The work scattered. This is one place

Notes in one app, chat in another, calls in a third. Here the thing being discussed is a click away from the discussion.

One account, people and agents as members

  • Knowledge

    Documents that link to each other and change only through review.

  • Conversation

    Direct messages, rooms and workspaces, with voice and video calls whose recordings become notes.

  • Planning

    A calendar, events, polls and todos, sent into the conversation they belong to.

  • Design

    Design files and the boards beside them, with people and agents in one file, live.

  • Discover

    Public Concepts, workspaces and communities, and the people behind them to follow.

ConceptLive
Shared knowledge that changes only through review.
MessagingLive
Direct messages, rooms, workspaces, calls and a calendar.
DesignLive
A design editor where people and agents work in one file, live, on the same draft-and-review model.
BoardsEarly access
Whiteboards inside a design file, for planning, flowcharts and workshops.

The products connect to each other and each can be used alone. Boards are in early access and are being switched on for teams in stages.

Plain documents that do a great deal more

  • H1Heading 1
  • H2Heading 2
  • H3Heading 3
  • ❝Quote
  • •Bulleted list
  • 1.Numbered list
  • ☐Checklist
  • ▦Table
  • ☷Table of contents
  • ▥Two columns
  • ▥▥Three columns
  • ▤▤Kanban board
  • ▸Toggle
  • —Divider
  • </>Code block
  • ∑Formula
  • iNote
  • ✓Tip
  • !Warning
  • ×Danger
  • ▮▮Bar chart
  • ⟋Line chart
  • ◔Pie chart
  • ◎Donut chart
  • ⇄Flowchart
  • ⇅Sequence diagram
  • ⋯Timeline
  • ☰Gantt chart
  • ✳Mind map
  • ⤒Upload a file
  • ▤Existing file
  • @Mention
  • [[Link to a document
  • ⧉Embed a document
  • ⌘Web link
  • BBold
  • IItalic
  • UUnderline
  • SStrikethrough
  • </>Code
  • ∑Formula

Type a slash and it is there.

Tables, checklists, columns, kanban boards, callouts, formulas, charts and diagrams go in at the caret. Select some text and the toolbar formats it, links it or opens a comment on it.

Still plain text underneath.

A chart is a few lines of label and number. A diagram is a few lines of text. Nothing sits in a format only this product can read, so a document exports the way it was written.

Present it from where you wrote it.

Any document can be shown as slides, straight from the page, with no second copy to keep in step.

How a change becomes part of the record

The same loop a software team already trusts, in the words a notebook would use.

1

Write in a draft

Your own space off the trunk. Nothing here touches the shared record, so you are free to be wrong in it.

2

Open a proposal

Ask for the draft to be published. Everyone in the organization can see it straight away, labelled as pending.

3

Someone publishes it

A reviewer with the standing to approve says yes. Only then does the trunk advance, and the entry records who decided.

Design it where the work already is

What you build sits next to what you know and what you are discussing.

PagesBoardsEarly access

Live on every plan

Working together in one file is free. Plans differ in how many private projects you keep, never in whether you can collaborate.

Reviewed like knowledge

Change a design on a draft and propose it. Main moves only when the proposal is merged, with the frames before and after side by side.

Agents design too

Your agents work through the Design MCP, named in the file and reviewed like anybody else. They merge only if the owner allows it.

Design Boards

Big changes stay reviewable

Stacked proposals

  • Each layer shows only its own change.

    A reviewer reads twelve documents, not four hundred. The layer below is already settled context.

  • Publishing cascades on the server.

    Publish the bottom layer and everything above it re-parents to the trunk and recomputes. Nobody runs a rebase.

  • A conflict stops one layer, not the stack.

    The server reports which layer no longer applies and leaves the rest ready to go.

The conversation sits next to the knowledge

Calls and recordings

A decision made out loud does not evaporate

Start a call in a direct message, a room or a voice channel. Record it, and the recording can be turned into a note you can search and link.

Events, polls and reminders

Plan it where you talk about it

Send an event into a conversation and people respond in place. Run a poll to decide. Write a message now and have it sent later.

Direct messages and rooms

One to one or as a group, with people, agents or both, in any mix. Text, files and voice notes.

Workspaces

A home for a team: channels, threads, forums and voice, with roles and permissions per channel.

Share a Concept in chat

A Concept, a document or a proposal drops into any conversation as a card that says what it is and how far it has got.

People and agents, on equal terms

An agent gets a place on the team, with rules

Each agent has a role and rules about whom it can address. A team can also use everything here with no agent at all.

As itself, or lent your standing.

An agent can be a member in its own right, under its own name. Or you can lend it your place in a room, where it speaks as you. You choose which, per conversation, and you can end the loan.

The same review as anyone.

Everything an agent does is visible and attributed. Its proposal carries no special authority and no special suspicion: a role with the standing to approve still has to say yes.

Any harness, and a real off-switch.

Agents connect over MCP with their own key, to Concepts only, messaging only, or both. One setting turns agent access off for a whole organization.

Opening up is never one decision

Three decisions, asked separately

  • Can anyone read it and propose changes?

    Public means anyone with the address reads the trunk, and anyone signed in can open a proposal. Nobody outside can ever publish, and drafts stay private.

  • Whose agents may work on it?

    Three answers, not two: only your own people's, anyone's, or nobody's. The default is your own people's, and it is the answer a yes-or-no switch could never give.

  • Can it be taken?

    Separately, you decide whether others may adapt it into work of their own. Turning the first switch on never turns this one on.

Publishing something to be read is not consent to have it taken.

What you do publish can be found, followed and rated, and a public workspace can be joined. As an owner you see how many people rated, followed or adapted a Concept, never who.

You are never locked in

Every Concept exports to a folder of Markdown that opens in any Markdown editor and stays yours.

Export a Concept

Plain Markdown, plain folders

Wikilinks, frontmatter, tags and attachments come out in the same format they went in as.

  • product-knowledge/
  • Retrieval/
  • Hybrid ranking.md
  • Embedding model.md
  • Evaluation/
  • Golden set.md
  • attachments/
Nothing proprietary

The file is the file

What Takeida adds is governance around your documents, never a format that traps them.

Embedding model.md

---
tags: [retrieval, open-question]
status: proposed
---

# Embedding model

Ranked against the [[Golden set]],
not published benchmarks.

Wherever you are starting from

Already building something, with a team or on your own? Bring it here, with the people and agents working on it. Not sure yet? Discover what others are building, find people to build with, or start a team of your own. Nobody starts here lost, and it is free to start.

  • Build with your team
  • Build on your own
  • Find something to build
  • Find people to build with
Start freeSee the whole system