Doctly

Name: Doctly
Brand: Dently.ai

AI Native

The most accurate PDF data extraction

Est 2025

LinkedIn 100|Web traffic 2K|FTEs 5

Published Sep 24, 2026

01Common complaints

- Company sizes or stages where this product is overkill or insufficient - For organizations that only require basic OCR on clean documents, hyperscaler OCR or open-source OCR may be more cost-effective and sufficient. - Industries or use cases where competitors are clearly superior - When highly productized, domain-specific processors (for invoices, IDs, etc.) are required and buyers prefer providers with long-established templates and procurement processes. - Technical requirements that this product may not meet - Workflows that require extraction and hosting of embedded images with retrievable URLs in Markdown outputs; community discussion indicates this is not provided in the referenced functionality. - Budget constraints that make alternatives more appropriate - Very high-volume OCR-only workloads may be cheaper with OCR-focused services; Doctly's value is greater when layout preservation and structured-output quality reduce downstream labor. - Specific workflows or integrations where the product falls short - When buyers need deep, native integration with a single cloud provider's IAM, logging, and governance tooling, hyperscalers may provide simpler procurement and integration paths. - Red flags in the buying process - Limited independent reviews and named references increase perceived procurement risk for regulated enterprises. - Buyers should request SOC 2 reports (under NDA if necessary), a BAA template for HIPAA use, subprocessors and data residency details, and retention/deletion guarantees rather than relying solely on public marketing statements. - Current limitations acknowledged by the vendor - Model refusals due to safety filters: the vendor notes some pages may be refused by models for safety reasons. - Image extraction / image URLs: community discussion and vendor responses indicate images are not extracted/provided in some output formats, resulting in placeholder image tags. - Features on the roadmap (not yet available) - No formal roadmap with dates was found in accessible sources. - Scale limitations - No published throughput benchmarks or documented scale limits were found. Pricing and product positioning suggest suitability for thousands of documents, but buyers should validate performance for their expected volumes. - Security or compliance gaps - SOC 2 Type II is claimed; additional artifacts (ISO certifications, pen-test summaries, subprocessors/location details) were not publicly available in accessible materials. - Technical debt or architectural limitations mentioned in reviews - There are insufficient third-party reviews to make authoritative claims about technical debt. - API limitations or integration constraints - Buyers should validate file size limits, rate limits, async job handling, retry semantics, and retention/deletion guarantees (including ZDR behavior) during procurement.

Deal disqualifiers: what makes a poor fit

Requirement for embedded image extraction with stable retrievable URLs as first-class outputs; this functionality was noted as not provided in a community discussion.
Requirement for extensive public third-party reviews, analyst coverage, or named references prior to procurement.
Necessity for explicit, publicly documented enterprise controls (SSO/SAML, SCIM, audit logs) before procurement.

Why some customers left for competitors (churn reasons)

Accessible third-party review content was insufficient to reliably summarize churn reasons.

02Why they buy

- Competitive advantages supported by accessible evidence - Limited but positive anecdotal validation from community sources indicates the product can produce usable outputs for some complex PDF conversion scenarios. - Unique features and capabilities described by the vendor - The vendor emphasizes producing Markdown as a primary output format suitable for RAG pipelines. - The vendor also describes a routing approach that directs pages to different models or OCR methods as part of processing logic. - Differentiation from competitors based on available signals - The evidence base for differentiation is limited and largely vendor-described; independent benchmarks were not located in accessible sources. - Value propositions with evidence from case materials - Vendor claims substantial time savings and high accuracy; accessible community examples show scale conversions but lack independent accuracy and cost reporting. - Areas where competitors have advantages - Hyperscalers provide mature documentation, procurement and security collateral, and broad regional availability. - Open-source options provide transparency and self-hosting control.

Why customers chose this product over alternatives

Founder narratives and vendor materials emphasize improved handling of complex PDFs (tables, rotated/scanned docs, handwriting) compared to some competing OCR/parsers.

03Field reports

Availability caveat (important)

The product has a limited presence on major enterprise review platforms based on accessible searches; most accessible community feedback comes from Reddit and Hacker News.

Direct quotes from community sources and vendor-provided materials

- Vendor-provided testimonial (presented on the vendor site; not independently verified): a testimonial claims a large reduction in document processing time and improved accuracy. - Founder statements (public forum): the founder acknowledged the parser "isn't perfect" while framing its performance relative to competing parsers. - Community feedback on public forums included brief positive observations such as "pretty good results" and noted specific limitations such as image URL handling.

Balance of sentiment

No verified corpus of star-rated reviews was found on major review platforms in accessible sources.
Community-sourced comments are limited: some positive anecdotal feedback exists alongside specific critical observations about image handling and billing clarity.
The accessible review volume is too small to represent a comprehensive customer sentiment distribution.

Common criticisms and complaints (support issues, bugs, missing features)

Image handling for Markdown: community members observed placeholder image references rather than extracted image URLs; the founder acknowledged that images were not extracted/provided in that context.
Pricing/usage transparency: community questions arose about how credits map to pages.
Model refusals / safety filters: the vendor notes that models may refuse to process certain pages due to built-in safety filters.

Specific outcomes customers achieved (with metrics when available)

Vendor-published testimonials include time-savings and accuracy claims; these lack named customers, baselines, document-mix descriptions, and independent verification.

Deal-breakers and reasons prospects did not purchase (inferred)

When embedded images with stable URLs are required as first-class outputs; the vendor acknowledged limitations in image extraction in a public forum.
When documents frequently trigger model safety refusals.
When large volumes of independent third-party reviews, analyst coverage, or named customer references are required for procurement.

Case Studies

- Vendor case studies - No detailed public case studies with named customers and reproducible metrics were found in accessible sources. - Community "project-style" case study - A community post reports converting a large volume of archival files to Markdown using the service, indicating capability at scale but not providing details on accuracy, cost, or QA processes. - Methodology gaps - Vendor outcome metrics are typically published without baselines, document-set descriptions, sampling methods, human QA protocols, or field-level accuracy reporting.

04Best fit

Company sizes

Likely fit: startups to mid-market and developer-led enterprise teams building document ingestion and AI pipelines.
Enterprise fit is possible given SOC 2 and HIPAA-related claims and an Enterprise tier, but independent proof points are limited.

Industries and verticals where adoption is relevant

Document types called out in vendor materials include regulatory filings, legal documents, financial reports, medical device records, and insurance forms.
No named public customers were identified in accessible sources.

Roles and personas: decision makers AND end users

End users: ML engineers, data engineers, platform engineers, operations and analyst teams responsible for document ingestion and cleanup.
Decision makers: heads of data/engineering, CTOs, AI platform leads, and compliance/security stakeholders.

Pain points and challenges the product addresses

Converting complex PDFs into structured outputs without losing document hierarchy.
Providing cleaner inputs for RAG pipelines to reduce downstream error and QA effort.
Handling scanned or rotated documents with tables and mixed formatting.

Qualification criteria: what makes a good fit

Primary need for Markdown/JSON/CSV outputs for downstream AI pipelines.
Corpus includes complex tables or multi-column PDFs.
Acceptance of a managed SaaS solution, or engagement of the Enterprise on-prem/private cloud deployment option.

Real customer examples with company names when available

Not found in accessible sources.

05The pitch

What the product does (core value proposition in objective terms)

- Doctly is a document parsing / "intelligent document processing" (IDP) SaaS that converts unstructured documents (PDFs and other formats) into structured outputs such as Markdown, JSON, and CSV via a web UI and API. - The vendor positions the product for handling documents with complex layouts (multi-column layouts, tables, charts, handwriting, scans) and producing outputs intended for downstream analytics and retrieval-augmented generation (RAG) or large language model (LLM) workflows. - Doctly documentation describes a single-API-call workflow in which a document is uploaded and structured data is returned.

Target market and market positioning

Primary users appear to be developers and operations teams building document pipelines and AI/RAG systems that require structured text and layout information from PDFs.
Marketing materials target enterprises and include claims such as vendor statements that the product is used by large companies; independent, third-party validation and named reference customers were not found in accessible sources.

Get a comprehensive analysis of Doctly including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →