A knowledge base
for your team.

Write down how things work. Keep your runbooks, project notes, and decisions together, organized by topic and searchable by your team.

Create a workspace See an example

A post in tile.md

Write in the editor or in Markdown. Add a topic so people can find it, and set a review schedule for documentation that needs regular checks.

Comments and version history stay with the post.

Example document

Engineering / Runbooks

Deploying to production

Owner: Engineering
Review: Every 90 days

Deploy from the main branch after the release checks pass. Let the on-call engineer know before starting.

Before you deploy

Check that the build and tests have passed.
Read the migration notes for this release.
Confirm who is monitoring the rollout.

If you need to roll back

Redeploy the previous release. Record the release number and the reason for the rollback in the incident log.

View Markdown source

Deploy from the main branch after the release checks pass.
Let the on-call engineer know before starting.

### Before you deploy

- Check that the build and tests have passed.
- Read the migration notes for this release.
- Confirm who is monitoring the rollout.

### If you need to roll back

Redeploy the previous release. Record the release number
and the reason for the rollback in the incident log.

Working with your docs

From the first draft to the next review.

Writing and feedback: Edit published posts together in real time. Use comments and mentions for feedback, and version history to review earlier changes.
Organize and search: Group posts into nested topics, save frequently used posts, and search posts, people, comments, and files with ⌘K.
Review and reading: Set review intervals and see which posts are due for a check. Mark posts as required reading and track acknowledgements.
Access: Manage workspace roles, private topics, and guest access. Sign in with a password or a registered passkey. Workspace admins can configure SAML single sign-on.
Technical documents: Include code blocks, tables, equations, and Mermaid diagrams. Attach files and link related posts.
Questions: When AI is enabled, ask a question about the posts you can access. Answers include links to the source posts.

Markdown, import, and export

Posts are stored as Markdown.

Import Markdown and Word files, or supported files from Notion and Confluence export ZIPs. Formatting may change during conversion.

Export posts you can access. Workspace owners and admins can download a ZIP of the posts visible to them, organized as Markdown files.

Admins can set up GitHub sync with a repository token. The REST API supports reading and updating posts within your account's permissions.

API reference