Crixaa vs DocRaptor

DocRaptor is an HTTP endpoint you POST HTML and CSS to; it renders that markup with the commercial PrinceXML engine and hands back a PDF or an XLS/XLSX file. Crixaa has no HTML path at all — you draw the document on a vector canvas, the canvas saves Crixaa's own layout JSON, and the API renders that. So the question is not which API is better. It is whether your document already exists as markup, or whether it exists as a design that nobody has written yet.

Concede this first, because it decides most evaluations

If your procurement checklist has SOC 2 on it, stop reading. DocRaptor states it is SOC 2 Type II compliant, audited against the 2017 Trust Services Criteria for Security, that it is fully GDPR compliant, and that HIPAA compliance is available on all paid plans at no additional charge once settings are updated and a BAA is executed. Crixaa holds no compliance certifications of any kind — no SOC 2, no HIPAA, no BAA, no ISO. We are not going to dress that up.

Three more that are equally final:

• Accessible PDFs. DocRaptor tags automatically when you set the Prince profile option to PDF/UA-1. Its own docs are candid that this covers the majority of the WCAG and Section 508 criteria, that some additional modifications may be required, and that ARIA roles are not tagged automatically. Crixaa produces no tagged PDFs, no PDF/UA, no PDF/A and no PDF/X. There is no flag to turn on.
• Print CSS. DocRaptor's PDF reference documents page floats, footnotes, cross references, leaders, page regions, margins and bleed, CMYK colours, bookmarks, annotations and metadata as first-class features. These are PrinceXML capabilities. Crixaa's layout DSL has no equivalent and no route to one.
• Long jobs and pinned engines. DocRaptor's documented limits are a one-minute default for synchronous generation and ten minutes in async mode, which returns a status id and accepts a callback URL. Its pipeline parameter selects a documented engine version in the range 6 to 10.1, so an upgrade need not reflow existing documents. Crixaa is synchronous inside a single HTTP request, has no async job model and no callback URL, and runs one engine version with no pinning.

DocRaptor also emits XLS and XLSX from HTML. Crixaa outputs PDF only — no DOCX, no ODT, no spreadsheet.

The trade Crixaa is actually offering

DocRaptor's model assumes someone on your team will author print CSS. That is a real skill, and it is not the same skill as writing web CSS: page regions, running headers and footnote flow behave differently from anything a browser renders. If that person exists on your team and the template is already written, DocRaptor is the better buy and this page will not talk you out of it.

Crixaa's bet is that on most teams, that person does not exist, and the document is being described in a Figma file or a PDF sent by finance. Crixaa gives you a vector design canvas instead: bezier path editing with control handles, boolean union and subtract on shapes, layers, rulers, smart guides and saved per-page guides. None of the hosted PDF APIs we compare against has a design canvas of any kind. You draw the document, bind fields to it, commit it, and call the API with data.

The corresponding cost is that the canvas is the only way in. There is no HTML import, no DOCX import, and three embedded font families — Inter, Source Serif 4 and JetBrains Mono. If your brand font is not one of those three, DocRaptor will honour it and Crixaa will not.

Where the canvas earns its keep: measurement

Every HTML-to-PDF pipeline has a preview problem. The thing you look at while editing is rendered by one engine and the deliverable is rendered by another, so a table that fits in the preview can break across a page in the output. DocRaptor's answer is unlimited watermarked test renders: setting test=true returns a watermarked PDF, test documents are unlimited on every plan including Free, and they do not count against your plan limit. That is a genuinely good answer to the problem, and it costs nothing.

Crixaa's answer is to remove the second engine. Text and table geometry on the canvas is measured by the PDF engine itself — the renderer runs its layout pass without emitting bytes and returns the geometry the render would compute, and the canvas draws that. So the line breaks and row heights you see are the ones the PDF will have. Be precise about the scope: this covers text-like elements and table row heights. Lists, images and shapes are not measured this way yet.

Two people editing the same document

Neither DocRaptor nor any other hosted PDF API in this comparison set has collaborative editing, because their template is a file in your repository and Git is the collaboration layer. That is a perfectly good answer for engineers, and a bad one for the finance lead who wants the payment terms moved down a line.

Crixaa's template is a live document. Two people can edit it at once with live cursors and follow mode, comments thread against the specific element they refer to, and there is a comment-only mode for reviewers who should not be moving things. On top of that sit review gates and ordered multi-step approvals: a commit is blocked while changes are requested, and an approval chain runs in the order you define. If your document changes because a non-engineer asked for a change, that loop happens inside Crixaa rather than in a ticket.

The receipt, and what it does not claim

Every Crixaa generation returns a sha256 of the exact bytes the caller receives, and anyone holding the resulting PDF can check it at crixaa.com/verify without an account. The file is hashed in the browser — it is never uploaded — and the lookup answers only whether that digest was issued and when.

Two honest qualifications. The signing certificate is self-signed, so Adobe Reader will show "signature validity is unknown" rather than a green tick; the verification story is digest comparison, not CA-trusted signing, and we will not imply otherwise. And this is a different guarantee from document delivery: DocRaptor's optional hosting add-on publishes a generated file at an unbranded documentdeliver.com URL, which is a distribution feature rather than a provenance one.

Pricing, and the currency problem

DocRaptor bills monthly in USD against a per-document quota. Read from its pricing table on 20 August 2026 — note that the table is served at /signup, and /pricing returns a 404:

Above quota you pay per document: 12¢ on Basic, 9¢ on Professional, 6¢ on Premium, 3¢ on Max, 2.66¢ on Bronze and 2.5¢ on Silver. Accounts are not auto-upgraded; DocRaptor says it sends multiple emails as you approach and reach the limit. The Free plan allows no overage. Two things worth knowing before you model this: a plan named Gold has a published overage rate of 2.25¢ but does not appear on the public pricing table at all, so its price and document count are not published; and the signup form collects card details alongside email, password and name, stating the card will not be charged for seven days — whether a card is mandatory to sit on the $0 Free plan is not stated anywhere we could find.

Two DocRaptor pricing properties are genuinely good and worth naming. Documents cost the same regardless of size or generation time, so a 400-page report and a one-page receipt bill identically. And the unlimited watermarked test renders mean you can build and style a template to completion before paying for a single document.

Crixaa's own pricing is on the pricing page, and here is the friction to pre-empt: billing runs through Razorpay and plans are denominated in INR. If your finance team needs a USD or EUR invoice, that is a real obstacle and you should establish it before you evaluate anything else. Separately, you can open any of our 50 free templates with no account and download one watermarked PDF without signing up, so the evaluation itself costs nothing.

Which one to pick

Pick DocRaptor if the document is a print-CSS problem, if you need tagged or archival PDF output, if a compliance checklist is involved, if generation can run for minutes, if you want the engine version pinned, or if you also need spreadsheets out. Its supporting operational detail is documented rather than implied — limits, overage, retention that can be configured to erase documents from its servers immediately on retrieval — and its support hours are stated as Monday to Friday, 10am to 6pm EST, which is worth checking against your timezone.

Pick Crixaa if the document does not exist yet and you would rather draw it than write markup for it; if the people who decide what the document says are not the people who can write CSS; if a change needs to pass a review gate before it can ship; or if you need to hand someone a PDF and let them verify independently that it is the file you issued. If you already have the HTML template and nobody on the team is asking to edit it, DocRaptor is the shorter path and we would rather you took it.