Skip to content

Trust

Local-first is a product promise, not a badge

How MDLoom separates device-local tools from capability-checked server conversion without vague privacy copy.

MDLoom project5 min read

Different work needs different compute

Source editing, preview, standalone HTML conversion, HTML-to-Markdown, and table transforms can run well in a modern browser. Canonical PDF, office conversion, and ebook validation use pinned server binaries. OCR remains a disabled future beta, not a current public converter.

Calling every feature “local” would either shrink the product or mislead users. MDLoom labels processing before file selection and states size, retention, and fidelity beside the control that starts work.

Anonymous should still be useful

You should not need an account to test a Markdown idea. Account gates are reserved for configured workspace persistence, server-backed token sharing, publication ownership, and server quotas that need identity.

Server work is isolated and temporary

The bundled rich-conversion worker runs non-root with bounded resources, a read-only root filesystem, and an egress-denied internal network. Jobs receive expiry metadata and record safe reports. A hosted operator must still configure durable Postgres/PGMQ state, cleanup monitoring, telemetry redaction, and equivalent platform isolation before production traffic.

Put it into practice

Open a clean workspace for your next document.

Start anonymously, choose an explicit Markdown profile, and keep source, preview, and diagnostics together.

Open the editor  →