Dillinger

Best Self-hosted Alternatives to Dillinger

A curated collection of the 3 best self hosted alternatives to Dillinger.

Browser-based Markdown editor for writing, previewing and exporting Markdown documents. Provides live preview, export to HTML/PDF/MD, and integrations with GitHub, Dropbox, Google Drive and local file export.

Alternatives List

#1
Mycorrhiza Wiki

Mycorrhiza Wiki

Lightweight filesystem wiki engine using Git for history and Mycomarkup for content, suited for personal wikis, digital gardens and small teams.

Mycorrhiza Wiki screenshot

Mycorrhiza Wiki is a lightweight wiki engine that stores content as plain files and keeps history in Git. It is implemented in Go and uses a custom markup language called Mycomarkup, targeting personal wikis, digital gardens and small-team knowledge bases.

Key Features

  • Filesystem-backed content (no database) with Git-based history and web feeds (RSS/Atom/JSON).
  • Content model built around "hyphae": modular content units that can transclude and link each other.
  • Mycomarkup as the primary, unambiguous markup format for authoring.
  • Keyboard-driven navigation and shortcuts for power users.
  • Optional authorization (username/password and Telegram login widget) and Open Graph meta support.
  • Interwiki support and simple deployment: a one-liner initializes a Git repo, prepopulates config and runs a server (default :1737); repository contains Dockerfile and build artifacts.

Use Cases

  • Personal knowledge base, digital garden or commonplace book for individuals.
  • Documentation or lightweight wiki for small teams and communities.
  • Public or private instances where Git-based history and file-editability are desired.

Limitations and Considerations

  • Uses a custom markup (Mycomarkup) rather than CommonMark/Markdown; this may require learning different syntax.
  • Reliant on Git for history and workflows, which assumes users or administrators are comfortable with Git operations.

Mycorrhiza is a focused, minimal wiki engine that emphasizes plain-file content, Git provenance and a connective "hyphae" model for building hypermedia documents. It is well-suited where simple deployment, file-editability and Git history are priorities.

367stars
26forks
View Details
#2
Markopolis

Markopolis

Web app and API server that publishes Markdown notes as websites and exposes REST APIs for programmatic access, with Obsidian-flavored Markdown and full-text search.

Markopolis is a web application and API server that publishes Markdown notes as websites while exposing a REST API to manage and interact with those notes programmatically. It is designed for personal knowledge bases and simple documentation sites, with an emphasis on Obsidian-compatible Markdown and easy self-hosting.

Key Features

  • Publish a folder of Markdown files as a website with instant rendering and theme support
  • REST API to upload, list, and retrieve Markdown content and document sections
  • Obsidian-flavored Markdown compatibility (callouts, equations, code highlighting)
  • Full-text fuzzy search across the notes vault
  • CLI and Python package for automating uploads and publishing workflows
  • Docker images and docker-compose examples for simple deployment
  • API key protection for endpoints and simple site configuration via environment variables

Use Cases

  • Host and publish a personal notes vault or Obsidian vault as a searchable website
  • Drive static sites or custom frontends by consuming Markdown content through the REST API
  • Lightweight documentation site for projects or teams that prefer Markdown-first workflows

Limitations and Considerations

  • Relies on a PocketBase-backed datastore (SQLite by default), which may limit scalability for very large deployments
  • CLI requires Python 3.12 or newer for some tooling and automation features
  • Focused on personal/technical documentation use cases; advanced multi-tenant user management and enterprise access controls are limited

Markopolis is intended for users who want a simple, extensible Markdown publishing platform with an API-first approach. It balances quick setup and practical API access for building custom frontends or automations around Markdown notes.

181stars
4forks
View Details
#3
eziwiki

eziwiki

Modern, lightweight static wiki and documentation site generator using Markdown and Next.js with TypeScript-configurable navigation and themes.

eziwiki screenshot

eziwiki is a minimal, static wiki and documentation site generator that builds documentation sites from Markdown content. It uses TypeScript for site configuration and outputs static files suitable for deployment to common static hosts.

Key Features

  • Write content in plain Markdown with optional frontmatter for pages
  • Configure site metadata, navigation, and theme via a TypeScript payload/config file
  • Built with Next.js and TypeScript, exports a static site for deployment
  • Hash-based URLs for page privacy and stable internal linking
  • Customizable navigation structure (folders, hidden pages, colored folder entries)
  • Simple developer workflow: local dev server, build, and commands to validate payload and list generated URLs

Use Cases

  • Personal knowledge base or notes site authored in Markdown
  • Project or API documentation site with configurable navigation and themes
  • Lightweight internal docs portal that can be exported and hosted as static files

Limitations and Considerations

  • Uses hash-based URLs which can hinder conventional SEO and direct pretty-linking
  • No built-in server-side features, user accounts, or in-browser editing; content must be authored and built from source
  • Lacks an integrated full-text search out of the box (requires adding search/indexing separately)

eziwiki is suited for users who want a simple, code-first documentation generator that produces static output and is easy to customize via TypeScript. It emphasizes minimalism, Markdown-first content, and straightforward deployment.

90stars
11forks
View Details

Why choose an open source alternative?

  • •Data ownership: Keep your data on your own servers
  • •No vendor lock-in: Freedom to switch or modify at any time
  • •Cost savings: Reduce or eliminate subscription fees
  • •Transparency: Audit the code and know exactly what's running