The Klippa DocHorizon alternativewithout the suite lock-in.
Klippa was acquired by SER Group and now operates as Doxis: DocHorizon became Doxis AI.dp inside an enterprise ECM suite. MiruIQ is the independent, API-first alternative for teams that wanted a document processing tool, not a content-management platform.
MiruIQ vs Klippa DocHorizon
If you want a full ECM/DMS suite with IDP inside, Doxis (ex-Klippa) is a legitimate enterprise choice. If you chose Klippa DocHorizon because it was an API-first document processing tool, that product category is exactly what MiruIQ still is: independent, deployable anywhere including on-premise and Swiss hosting, with public pricing, three things the Doxis version no longer offers.
The honest comparison table
Facts a buyer can verify, not marketing adjectives. Both columns describe the products as they ship today.
| Dimension | MiruIQ | Klippa DocHorizon |
|---|---|---|
| Deployment options | Cloud, Swiss-hosted, on-premise or air-gapped, including the AI models, shipping today | Azure cloud (region of choice); no on-premise option published |
| Human-in-the-loop review | Built-in verify step: documents park at review nodes, reviewer edits flow back into the pipeline | Human-in-the-loop validation as a named feature |
| Extraction approach | Generic and schema-driven, not pre-trained per document type: define the structure once and extract from any document. Handles complex tables, including notes above a table that change how the numbers must be read (e.g. "zeros cut off on purpose"). | OCR + extraction, classification, fraud detection, identity verification; now the IDP engine of the Doxis ECM suite |
| Fraud detection | Data-level: cross-document validation, recalculation of figures that must add up, external verification via API gates (bank checks, registry lookups); deliberately no image forensics, which generative AI defeats | Image forensics: EXIF metadata and pixel analysis, plus identity verification and fraud-detection AI agents |
| Data residency | Switzerland or your own infrastructure; documents never leave your environment | EU hosting on Azure; no Swiss hosting, no sovereignty narrative |
| Local AI models | Yes: local LLMs on dedicated hardware, no US-cloud dependency | No |
| Ownership & independence | Independent Swiss company; document processing is the whole product | Acquired by SER Group (2025); Klippa brand wound down into Doxis (2026) |
| Pricing transparency | Public monthly plans: divide plan price by document volume for your per-document rate | No public pricing: the pricing page was removed; volume-based quotes |
| Best-fit segment | Mid-market and enterprise teams in regulated industries | Enterprises that want a full ECM/DMS suite with document AI inside |
Who should choose what
No tool wins every scenario. This is our honest read of where each product is the right choice.
When Klippa DocHorizon is the better choice
You actually want an ECM/DMS platform (archiving, records management, content workflows), and document AI is one capability inside that bigger purchase. Identity verification (validating ID documents in onboarding flows) is a core requirement; that tooling is mature in the Doxis portfolio. You are already an SER/Doxis customer and consolidation onto one suite outweighs tool independence.
When MiruIQ is the better choice
You wanted what Klippa DocHorizon originally was: an API-first extraction tool you integrate into your own stack, without buying an ECM suite around it. You need deployment options the Azure-only suite doesn't offer: on-premise, air-gapped, or Swiss hosting with local AI models. You want public pricing and a vendor whose roadmap isn't governed by suite strategy: the two things acquisition churn takes away first.
Beyond the head-to-head, three questions usually settle the choice:
Where must documents live?
If the answer is your own infrastructure or Switzerland, the field narrows fast: MiruIQ ships on-premise with local AI models and Swiss hosting as standard. If any compliant cloud works, Klippa DocHorizon stays in the running.
Who runs it day to day?
Developer APIs assume engineers own the workflow. MiruIQ is built for operations teams: reviewers work in the verify queue, and pipelines are configured, not coded.
Can you compute the price?
Public plans mean you know your per-document rate before the first sales call, and processing pauses instead of overrunning your budget.
Klippa alternative questions
What former DocHorizon evaluators ask most.
Klippa was acquired by SER Group in March 2025; SER rebranded to Doxis, and since early 2026 Klippa operates fully under the Doxis brand: DocHorizon is now Doxis AI.dp, sold as part of an enterprise ECM suite. The standalone, API-first product that DocHorizon buyers evaluated is being absorbed into a suite sale.
MiruIQ covers DocHorizon's core ground (OCR, classification, schema-based extraction, human-in-the-loop validation, API-first integration) as an independent product with deployment options Klippa never had: on-premise, air-gapped and Swiss hosting with local AI models, plus published pricing.
Deliberately not. Generative AI has made visually perfect forgeries trivial: a fabricated invoice or payslip can carry clean metadata and flawless pixels, so image forensics can no longer carry the burden of proof. MiruIQ detects fraud where it still reliably shows: in the data. Cross-document validation compares names, employers, dates and amounts across a bundle and recalculates figures that must add up. And because the result is structured data, it can be verified against the outside world: an API Acceptance Gate lets an external system (a bank check, a registry lookup, your own reference values) approve or reject a document before it continues. Pixels can be faked; a whole file of mutually consistent, mathematically correct, externally verified numbers is much harder.
Klippa's public pricing page was removed during the Doxis transition; what remains is volume-based quoting inside an ECM suite sales process. MiruIQ keeps public plan pricing you can compute per document, with a 14-day, 200-document free trial.
The API-first DocHorizon product your integration was built on now lives inside the Doxis suite, so migration is mostly about re-pointing integrations: MiruIQ is API-first, ingestion and delivery are configured as pipelines, and extraction is schema-driven, so there are no templates to rebuild. Most teams run the two side by side during the free trial.
Run your hardest documents through MiruIQ
The only comparison that matters is on your documents. Send us your five hardest (complex tables, mixed bundles, scanned mail) and see the extraction quality yourself.