Documentation

Getting started

• The onboarding vault — what's inside and how to keep its API key safe.
• Admin panel tour — where to manage readers, access and payments.
• How trip2g works — the path a note takes from Obsidian to readers and AI agents.
• Publishing notes — title, URL, access and publish time.
• Markdown syntax — which formatting renders on your site.

Publishing and sync

• Two-way sync with Obsidian — changes made on the server reach your vault.
• Git sync — clone your site, edit anywhere, push back.
• In-browser editor — edit notes and roll back versions without Obsidian.
• Live editing — turn on "Live reload" in the ☰ menu and the open page reloads by itself after every edit.
• Wikilink resolution — which file [[Name]] opens when names collide.
• Note validators — check notes against your rules on every sync: required fields, sections, images.
• Jsonnet in trip2g — the language of patches, validators, note queries and webhook transforms, in ten minutes.
• Note queries — give a JavaScript page a list of notes by frontmatter, without exposing the frontmatter.

Telegram

• Telegram publishing — posts from your notes go to your channel on a schedule or right away.
• Preview in a test channel — you see the finished post before your readers do.
• Import from Telegram — your channel archive becomes Obsidian notes.
• Custom emoji — animated emoji from sticker packs in your posts.

Monetization

Leave free: true off and only subscribers can read the note; everyone else gets a preview and a sign-in form.

• Monetization — access through a Patreon or Boosty subscription, or for crypto.
• Subgraphs — a public blog, a paid course and an internal wiki in one vault.
• Telegram group access — group members read gated notes.

Templates

• Default template — set up the page layout in frontmatter, no HTML.
• Theming the default template — your own colors and fonts in one CSS block.
• Custom templates — your own page design: one HTML file in _layouts/.
• Template components — templates built from small reusable blocks.
• An app on top of trip2g — a note as an app, such as a kanban board.
• Calls dashboard — a timeline of call threads and a screen to check one call.

AI agents and automation

• MCP server — an AI client answers questions from your knowledge base.
• Instructions for a knowledge base — teach the agent how to search your base.
• Fleet — agents you describe as plain notes.
• Webhooks — call external services on note changes or on a schedule.
• Forms in notes — collect requests and reader answers right on the page.

Hosting and setup

• Hosting — the demo, managed hosting or your own server.
• Self-hosted — a single binary on Linux, Docker Compose or fly.io.
• Deploy on fly.io — one machine and one volume, no separate database.
• Backups — database snapshots to S3-compatible storage, or Litestream replication.
• Multi-domains — your own domain or subdomain for sections of the site.
• Multilingual sites — one vault in several languages.

Use cases

For writers with paid channels, teams with internal wikis, course authors and open-source projects.

• What can you do with trip2g — where to start: a site, a wiki, agents, Telegram, sales.
• Telegram blog from Obsidian — a channel without copy-paste or manual formatting.
• Sell access to your Obsidian notes — paid access from your own domain.
• Team knowledge base for AI agents — people read a site, agents query over MCP.
• Self-hosted wiki on SQLite — compared with Wiki.js, BookStack and Outline.
• Team knowledge base on a bare VM — deployment on a single virtual machine.
• Digital garden — a site readers explore by links, not by date.
• All examples — YouTuber, AI consultant, Telegram channel, project documentation.

What's new: see the changelog.