TiddlyWiki
Obsidian.md
Zim Wiki
Logseq
DokuWiki
Joplin
Notion
Evernote
Emisar.dev
Emisar is the last MCP server youโll need to install: a Zero-Trust gateway connecting Claude, Cursor, ChatGPT, and any AI agent to your infrastructure. One server handles production access, debugging, alerts, and internal operations, with new capabilities added as packs. Agents can inspect real production state, debug what they shipped, and help resolve incidents. Safe reads run automatically; policy allows, blocks, or routes risky actions for approval. No SSH keys, VPNs, remote shells, or standing shell access โ and every call is recorded.
TiddlyWiki Emisar.devNo features have been listed yet.
No Emisar.dev videos yet. You could help us improve this page by suggesting one.
Emisar.dev's answer:
emisar is for SRE, DevOps, platform engineering, infrastructure, and security teams that want AI agents to inspect and operate production systems. It is especially relevant to teams managing multiple Linux hosts, clusters, databases, cloud services, or regulated environments where unrestricted shell access and incomplete audit records are unacceptable.
Emisar.dev's answer:
The hosted control plane and operator interface use Elixir, Phoenix, LiveView, PostgreSQL, and Tailwind CSS. The host runner and MCP bridge are written in Go. Action packs use YAML and JSON Schema, while production infrastructure is managed with Terraform on Google Cloud. The system communicates through MCP, OAuth 2.1, TLS, and WebSockets.
Emisar.dev's answer:
Emisar.dev's answer:
Founder Andrii Dryga spent a decade working as a CTO, full-stack engineer, SRE, and DevOps engineer. He experienced the cost of running the wrong command on the wrong cluster, while also seeing AI solve operational problems in seconds. emisar grew from the need to preserve both truths: AI agents are useful, and production access must remain bounded. Its answer is to give agents a reviewed catalog of operations instead of a blank terminal.
Emisar.dev's answer:
emisar lets AI agents work on real infrastructure without giving them a shell. Agents choose from a finite catalog of typed, versioned actions. Policy decides what runs, what requires approval, and what is denied, while an outbound-only runner verifies the action again on the host. New capabilities arrive as packs behind the same MCP integration, and every request is recorded in both a searchable audit trail and a tamper-evident host journal. [
Emisar.dev's answer:
Choose emisar when you want an agent to keep investigating and handling routine operations without handing it SSH credentials or supervising every call. Compared with raw shell access, copy-paste workflows, or one-off MCP servers, emisar provides reviewed action contracts, host-level enforcement, risk-based policy, scoped access, approvals, pack integrity checks, and a durable audit trail. It is built specifically for governed infrastructure access rather than generic automation.
Not too far ago, I invested several days into "mastering" and tuning TiddlyWiki. It was an interesting experience. I loved it on the whole and felt very enthusiastic about using it store all my knowledge. It's super flexible and use of tags, filters and macros make it unique. However, it's a bit complicated for mass adoption. Also, the extended use of its powerful features may make your computer tangibly slow.
That's why I found "Obsidian", that's what I'm using today to store my knowledge.
Based on our record, TiddlyWiki seems to be more popular. It has been mentiond 200 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
I don't think anyone you're calling a "shop" would do anything business-critical with it, but fwiw, Tiddlywiki fits in this category. https://tiddlywiki.com/. - Source: Hacker News / 4 days ago
Https://tiddlywiki.com/#WidgetMessage%3A%20tm-http-request A community version of TiddlyWiki called Bob (by OokTech) implements real-time, two-way communication between the server and the browser, and between different wikis managed by the same server. This is the closest functional equivalent to what Joe and Jeremy discussed, it's built on WebSockets and Node.js. - Source: Hacker News / 6 months ago
What is your innovation over https://tiddlywiki.com/. - Source: Hacker News / 8 months ago
Not a dig, but it reminds me of how much I used to like tiddly wiki. https://tiddlywiki.com/. - Source: Hacker News / 10 months ago
I have slightly different needs I suppose, but I settled for https://tiddlywiki.com/ as my SOHO wiki. There is a learning curve, but once you grasp some rather uncommon concepts it's quite good and very easy to setup, backup and manage locally or remotely. - Source: Hacker News / 11 months ago
Obsidian.md - A second brain, for you, forever. Obsidian is a powerful knowledge base that works on top of a local folder of plain text Markdown files.
Zim Wiki - Zim is a graphical text editor used to maintain a collection of wiki pages. Each page can contain links to other pages, simple formatting and images.
Logseq - Logseq is a local-first, non-linear, outliner notebook for organizing and sharing your personal knowledge base.
DokuWiki - DokuWiki is a simple to use and highly versatile Open Source wiki software that doesn't require a database.
Joplin - Joplin is a free, open source note taking and to-do application, which can handle a large number of notes organised into notebooks. The notes are searchable, tagged and modified either from the applications directly or from your own text editor.
Notion - All-in-one workspace. One tool for your whole team. Write, plan, and get organized.
