Metamorphic VS DynamicDocumentAPI

Metamorphic's answer

Metamorphic is a new product and we don't disclose customer names. By design, we know as little about our users as possible — that's the point of zero-knowledge architecture.

DynamicDocumentAPI's answer:

Dynamic Document API is a young product. Our users are mostly developers and small SaaS teams, and we don't name customers without their permission.

Metamorphic's answer

Metamorphic is a zero-knowledge, end-to-end encrypted habit tracker — every piece of user data is encrypted client-side before it ever reaches the server. Unlike competitors that treat encryption as a premium add-on, Metamorphic includes it on every plan, including Free. It also uses hybrid post-quantum cryptography (ML-KEM-768 + X25519), the same approach adopted by Signal and Apple iMessage, making it one of the first habit trackers with quantum-resistant key distribution. The server never stores plaintext — not even your email address.

DynamicDocumentAPI's answer:

It covers the whole path from data to finished document in one API: you design a template in a visual or HTML editor (or send raw HTML, CSS or Markdown), send JSON, and get a PDF or image back. The same service also creates e-invoices (XRechnung, EN 16931, Factur-X / ZUGFeRD) that are validated against the official rules before they are returned, and can embed them in the PDF. Rendering is deterministic: the same template and data always give the same document, laid out by a headless browser, with no AI model generating content. Everything runs in the EU (Germany). It also ships an MCP server, so AI agents like Claude and ChatGPT can render documents directly.

Metamorphic's answer

Most habit trackers store your data in plaintext on their servers. Metamorphic never sees your data — all encryption and decryption happens in your browser. If the server were fully compromised, an attacker would get only opaque ciphertext. Beyond privacy, Metamorphic is a complete self-improvement platform: habit tracking with streaks and drag-and-drop reordering, goal setting with milestones and progress bars, daily self-reflections with mood tracking, a full schedule and calendar with recurring events and printable views, progress insights with activity heatmaps, and family/group accountability with shared habits and goals. You get the depth of a full-featured tracker with the privacy of an E2E encrypted system — no trade-off required.

DynamicDocumentAPI's answer:

Most document APIs do one thing: convert HTML to PDF, or fill templates. Dynamic Document API does both, adds image templates, PDF merging and validated e-invoices, and offers them through a REST API, SDKs for Node and Python, Zapier, Make, n8n and an MCP server for AI agents. Data is processed and stored in the EU only, files come back as signed links that expire, and storing nothing at all is a supported option. Pricing is predictable: one published credit table, the same core features on every paid plan and a spend cap you control. We also publish a render-time benchmark with its method and raw data, so you can check our speed instead of trusting a claim. The free plan includes 50 renders a month without a credit card.

Metamorphic's answer

Privacy-conscious individuals and families who want a serious habit and self-improvement tool without surrendering their personal data to a third party. People who care about building better routines — daily habits, long-term goals, journaling, scheduling — but also care about who can read their data. Particularly relevant for anyone who has thought twice about logging personal struggles, health habits, or family goals into an app that stores everything in plaintext.

DynamicDocumentAPI's answer:

Developers and product teams whose software has to send documents: invoices after a payment, certificates after a course, reports, labels and statements. Typical users are SaaS companies, marketplaces, e-commerce and learning platforms. A second group are businesses in Germany and the EU that need compliant e-invoices (XRechnung, ZUGFeRD) for the German B2B e-invoicing mandate and public-sector buyers. No-code builders use it through Zapier, Make and n8n, and teams building AI agents use the MCP server.

Metamorphic's answer

Metamorphic grew out of a personal conviction. Its creator, Mark Thayer, was building another app (Mosslet) around the time he was becoming a new dad. Reading Shoshana Zuboff's The Age of Surveillance Capitalism made him want a better digital world for his child. When Meta rolled back end-to-end encryption on its direct messaging, he was pushed to implement real E2EE in Mosslet — built on an asymmetric, password-derived key architecture.

The idea for Metamorphic itself came from his partner, who is passionate about psychology and behavior — always thinking about how to break old habits and form better ones. It clicked: something as personal as your habits, goals, and daily reflections should be private to only you, and you shouldn't have to worry about it being otherwise. So Metamorphic was built from day one around zero-knowledge architecture, where encryption is the foundation rather than an afterthought.

DynamicDocumentAPI's answer:

Almost every product eventually needs to produce documents, and most teams end up building their own rendering stack: a headless browser, fonts, page breaks, storage and retries. It works until an invoice splits a table row or a certificate shows the wrong date, and then it becomes a support ticket. We built Dynamic Document API to be that layer for them: templates, rendering and delivery as one service, hosted in Europe, treating pagination, fonts and formatting as engineering problems rather than edge cases. When e-invoicing became mandatory for B2B in Germany, we added validated XRechnung and ZUGFeRD output, and with AI agents producing more paperwork, an MCP server followed.

Metamorphic's answer

• Elixir and Phoenix LiveView (real-time web application)
• PostgreSQL with Ecto (database)
• libsodium / NaCl (client-side end-to-end encryption)
• @noble/post-quantum (ML-KEM-768 hybrid post-quantum key encapsulation)
• Cloak / AES-256-GCM (application-level at-rest encryption)
• Argon2id (password hashing and key derivation)
• Tailwind CSS (UI styling)
• Stripe (billing and subscriptions)
• Oban (background job processing)
• Fly.io (hosting, LUKS-encrypted storage volumes)

DynamicDocumentAPI's answer:

Rendering runs in Rust workers that drive headless Chromium over the DevTools protocol, with MiniJinja for templates. The API and control plane are built with Django and Django REST Framework, with Celery, PostgreSQL, Valkey and NATS JetStream for queues and events, and S3-compatible object storage for files. PDF/A output is checked with veraPDF and e-invoices with the official KoSIT validator. The dashboard and website are built with Next.js. Everything runs on Kubernetes in data centres in Germany.