Boards
One card, several boards
Put a card on as many boards as it belongs to. Each board keeps its own columns, and the card keeps its own place in each of them: in progress here, waiting there, and still one card with one history.
Pre-release
One card.Every board it belongs to.
Tecto is a kanban project manager for work that does not fit in one board. A card can sit on the team board and on the release board at once, in a different column on each — and it is the same card, not a copy of it. Hosted in Germany.
Ask for early access by email
One email when we open. No newsletter.
The problem
Work belongs to more than one board.
A task is on the team’s board and in the release, and the client wants it in their view too. Every tool answers that with a copy, a link, or a board so wide nobody reads it — and from then on you are maintaining three places where one thing is happening. Tecto answers it with one card that is genuinely on all three, and a column of its own on each. Move it in the release and the team’s board does not twitch.
What it does
A board that holds the work, and explains it.
Cards
A card is a real document
Not a title with a description field. A card is a page: write in it properly, at length, with someone else at the same time. Comments, mentions, version history and search all work in it, because they work on every page here.
Context
The board can say what it is for
Above the columns sits a document, not a heading. Write the plan, the decision, the definition of done — and pin the cards you are talking about right into the text. The context stops living in a separate wiki nobody opens.
Together
Everyone on the same board at once
Live editing with everyone visible where they are working. Two people sorting the same column is a normal Monday morning, not a conflict to resolve afterwards.
Fields
Fields defined once, for everyone
Priority, estimate, customer, owner: defined once for the whole workspace rather than per board, so the same field means the same thing everywhere and a report across boards is possible at all.
Markdown
Your work is text you can take away
Every card reads and writes as Markdown, field values included. Take it out whenever you want, edit it elsewhere, put it back. Nothing stays behind and nothing needs converting.
Compare
A board that is not a copy of another board.
The two middle columns are categories rather than named products — feature lists move faster than a table can keep up, and the point here is the shape of the tool, not whose logo is on it. Tecto is pre-release, so read its column as a commitment rather than a shipped feature list.
| A kanban board | An issue tracker | Tecto | |
|---|---|---|---|
| The same item on several boards | a copy, or a link between two | one issue, one place, saved filters | one card, its own column on each |
| An item you can write in properly | a description field | a description and comments | a page: long text, history, mentions |
| A board that explains itself | a title | a wiki somewhere else | a document above the columns, with cards pinned in it |
| Everyone in it at once | usually yes | rarely | live, everyone visible |
| Fields that mean the same everywhere | per board | per project | defined once for the workspace |
| Take everything with you | a CSV | a CSV or an API | Markdown, out and back in |
| Data in Germany | depends on the vendor | depends on the vendor | data centre in Germany |
Categories rather than products, on purpose: a table naming vendors is out of date the week after it is written, and we would rather be accurate than pointed. Written July 2026.
Markdown
A card, as text.
A card is stored the way you would write it out by hand: a document with its field values at the top. That is not an export format sitting next to the real one — it is the card. Read it with anything that reads Markdown, write it back, and the fields come back with it.
GET /v1/workspaces/{id}/pages/{id}?format=markdown
---
title: Rewrite the onboarding mail
fields:
status: In progress
owner: "@mara"
due: 2026-08-14
---
# Rewrite the onboarding mail
It explains the product. It should explain the first week.
- [x] Read the six newest support threads
- [ ] Decide what paragraph two is forOn two boards, and one document either way.
Data protection
Hosted in Germany. Under the GDPR.
A project board says who is doing what, how long it took and what went wrong. That belongs in a German data centre rather than in a US cloud wearing a European label. The data processing agreement belongs to the plan, not to the invoice.
- Data centre in Germany, processing inside the EU
- Data processing agreement under Art. 28 GDPR — in every plan, including the free one
- Your content is never used to train AI models
- Full Markdown export, any time, without asking us
Early access
Tecto is not open yet.
Boards, cards and the parts you would notice were missing are what we are finishing now. Leave your address and we will write once — when you can sign up, not before.
Ask for early access by email
See pricingOne email when we open. No newsletter.