Keep documents on infrastructure you control
Use the same browser-based editor without sending documents through an account-first hosted SaaS path.
Self-hosting
Run mdedit.io on your own infrastructure with Docker
Self-host a browser-based Markdown editor with live preview, collaboration, citations, and PDF or DOCX export, without pushing documents into a hosted account-first SaaS workflow.
Why self-host mdedit
No desktop rollout required
Users open the editor in the browser. No local install is needed for everyday writing and export.
One workflow for writing and output
Markdown, preview, sharing, citations, PDF, and DOCX stay inside one product path rather than separate tools.
Simple runtime model
Docker Compose, SQLite, environment variables, and reverse-proxy compatibility keep the operating surface understandable.
What you get
- live Markdown preview in the browser
- Mermaid and KaTeX support
- shared documents and collaboration features
- citations and bibliography-aware export paths
- PDF and DOCX export from the same source document
- SQLite-backed storage
- environment-based configuration
- Docker and reverse-proxy deployment path
- open-source code under Apache 2.0
- private hosting without cloud dependency
Next steps
1. Start the stack
Use the Docker Compose path and verify the health endpoint locally.
2. Configure secrets
Set `COOKIE_SECRET` and optional AI provider keys in `.env` before public exposure.
3. Put it behind your domain
Use a reverse proxy for your production hostname and HTTPS termination.
4. Share the editor
Give your users a browser URL instead of a desktop installation checklist.
Mini FAQ
Does self-hosting remove export features?
No. PDF and DOCX export remain part of the same application path when the runtime dependencies are present.
Can I run it privately for a team?
Yes. That is one of the main reasons to self-host mdedit.io instead of relying on a public instance.
Is it account-based SaaS?
No. mdedit.io is a browser-based app and can be run without a hosted account model.
Where is the full setup documentation?
Use the main help page and the GitHub repository for the detailed Docker and deployment path.