Underlayer VS DynamicDocumentAPI

Underlayer's answer

it's pre-launching

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.

Underlayer's answer

Underlayer is training with no portal. You build a course by API, by MCP, or in the visual builder, and add it to your product with one iframe. Then signed webhooks tell your systems who finished. Learners never create an account or leave your app, and the player uses your theme, so it looks like part of your product. We charge per course view, not per seat, and every price and overage rate is published.

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.

Underlayer's answer

Most course tools, like Coassemble, Trainn and LearningStudioAI, assume training happens on their own site: learners sign up, log in and get enrolled, and you pay per seat. Underlayer takes the opposite approach:

No learner accounts. You pass in your own user IDs and we track progress against them. Built for developers. A full REST API covers every resource, and an MCP server lets AI agents create and edit courses. Results in your own tools. Signed webhooks send completions to your CRM, your product or your data warehouse. SCORM 1.2 and 2004 export for customers who still need to load courses into an LMS. Public pricing. Plans start at $149/month for 25,000 course views, with unlimited learners and no sales call 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.

Underlayer's answer

SaaS product, customer success and engineering teams who want onboarding, product education or compliance training inside their own app. It also suits platforms that train other people's users, like partner networks, marketplaces and field-ops tools, where a separate LMS login gets in the way.

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.

Underlayer's answer

Every company putting training in front of its users hit the same wall: the LMS wanted to own the learner. That meant a separate portal, a second login and a per-seat bill for people who never opened a course. We built Underlayer as the layer underneath instead. You keep the product and the user relationship. We handle building the course, playing it and tracking progress, and we stay out of the way.

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.

Underlayer's answer

Next.js 16 (App Router) with React 19 and TypeScript, Tailwind CSS v4, and Supabase (Postgres with row-level security, Auth and Storage). Claude from Anthropic generates courses with AI. Stripe handles billing and Resend sends email. There is also a remote MCP server with OAuth 2.1 for AI-agent access.

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.