Ecliptor

Name: Ecliptor
Brand: Ecliptor

AI Native

AI, embeddings and everything in-between.

Est 2023|Raised $500K

LinkedIn 223|Website|FTEs 2|HQ San Francisco, California, US

MarketsBuyer Intent & Signals Community-led Sales Platforms

Published Oct 2, 2026

01Common complaints

- If strong, publicly documented security and compliance evidence (SOC 2/ISO) is required before any engagement. - If transparent pricing is necessary for budgeting (particularly for ingestion at scale, e.g., millions of pages per year). - If primary documents are scanned images requiring best-in-class OCR and the OCR performance cannot be validated quickly. - If a large vendor ecosystem and enterprise support contracts are preferred (e.g., Adobe). - If a widely reviewed, off-the-shelf product with abundant third-party feedback is required (Ecliptor has limited credible review coverage). - Current limitations acknowledged by the vendor - The main product site is "Coming Soon," so vendor-disclosed limitations are not publicly available. - Features on the roadmap (not yet available) - Not publicly documented. - Scale limitations (at what volume/size does it break down?) - Not publicly documented. - Security or compliance gaps - Security certifications and policies are not publicly documented. - API limitations or integration constraints - No public API reference documentation was found beyond the demo.

Deal disqualifiers: conditions indicating lower suitability

The organization requires publicly available compliance certifications before engagement.
The organization needs broad document format support beyond PDFs.
The organization requires a highly mature platform with guaranteed SLAs and a long-established track record.

02Why they buy

- Potential unique selling points (based on demonstration behavior) - The demo focuses on a PDF-to-markdown ingestion workflow. - Output includes markdown plus chunking intended for embeddings and retrieval. - Demonstration content indicates handling of complex documents with images and tabular data; these claims are demonstration-based and not benchmarked. - What is not validated - No independent benchmark data was found for extraction accuracy, table fidelity, latency, or OCR quality. - No verified customer outcomes or independent performance metrics were publicly documented. - Areas where competitors have clear advantages - Adobe: enterprise maturity and likely compliance posture. - PDF.ai and similar providers: clearer public API documentation, pricing mechanics, and developer resources.

03Field reports

Important limitation - There are no accessible Gartner Peer Insights reviews found for Ecliptor as a product listing. Access to Gartner Peer Insights is often gated and the query did not surface an Ecliptor listing. - No credible, high-volume review corpus (G2/TrustRadius) was found for Ecliptor itself. Review summary (available sources) - A niche review site lists a small number of short, generic reviews with a moderate aggregate rating; reviewer identities appear low-confidence, so this source should be treated as low-confidence. - Review content summarized in neutral terms: - Some reviews describe the product as fast and reliable and note ongoing improvements. - Some reviewers reported reduced time spent on document tasks after adopting the tool. - Several reviews mentioned the user interface is confusing and in need of improvement. Reddit / community evidence (relevance caveat) - Searches for Ecliptor mostly returned unrelated topics (LEGO MOCs, a Power Rangers character named Ecliptor), not the B2B product. - No high-signal Reddit threads discussing Ecliptor usage were found in accessible results. Why customers evaluated this product over alternatives - Not directly evidenced in user reviews. - Inferred from demo positioning: evaluators may be seeking improved preservation of document structure in markdown output (tables/images) and chunking suited for embeddings. Why customers left for competitors (churn reasons) - Not evidenced. Specific outcomes customers reported (with metrics when available) - No verified outcomes or independent ROI metrics were publicly available. - A partner blog post describes a use case of document search for compliance automation; no independent metrics were provided.

Lantern example (document search + compliance automation)

- Lantern published a blog post describing use of Lantern with Ecliptor to build an application that searches compliance context from documents and uses retrieved context to automate compliance checks. - Critical evaluation: - This is a partner/vendor blog post rather than an independently audited case study. - The post does not include controlled metrics (precision/recall, extraction accuracy, time saved). - It should be interpreted as a solution pattern rather than proof of specific outcomes.

04Best fit

Company sizes: specific employee counts and revenue ranges

Likely best fit:
- Startups to mid-market organizations (small to mid-sized companies) building AI features where ingestion quality materially affects RAG performance.
Less likely fit:
- Large, highly regulated enterprises that require publicly available compliance reports and extensive security documentation before engagement (unless Ecliptor provides required evidence under NDA).

Industries and verticals where adoption is most relevant (with example use cases)

Potentially most relevant:
- B2B SaaS, developer tooling, and AI product teams.
- Regulated industries (finance/healthcare) as potential users if a strong security posture is demonstrable.
Example use case theme:
- Compliance and policy document search/automation (as described in a partner blog post).

Roles and personas: decision makers and end users

Decision makers:
- Head of AI/ML, VP Engineering, CTO.
- Security and Compliance leaders responsible for regulated document ingestion.
End users:
- Applied AI engineers.
- Data/ML platform engineers.
- Backend engineers implementing ingestion pipelines.

Pain points and challenges the product addresses

Converting PDFs to structured text while preserving tables and reading order.
Producing chunked markdown suitable for embeddings.

Qualification criteria: what makes a good fit

The organization has a document-heavy workflow where PDFs are a primary knowledge source.
Ingestion quality materially affects retrieval-augmented-generation (RAG) performance.
The organization can run a pilot to evaluate extraction quality with representative documents.

05The pitch

- What the product does (core value proposition in objective terms) - Ecliptor appears to be an early-stage B2B AI product focused on document ingestion for AI workflows, specifically a PDF-to-markdown ingestion API that converts complex documents (including images and tables) into markdown chunks for embedding and retrieval (RAG). The public demo frames the product as a "PDF to markdown ingest API" outputting markdown plus chunks intended for embedding and retrieval. - The primary marketing site at ecliptor.ai currently shows a "Coming Soon" landing page, limiting clarity on broader product scope and feature set. - Target market and market positioning - The strongest fit appears to be: - AI/LLM application teams building RAG pipelines, knowledge bases, compliance search, or agent workflows that require structured extraction from PDFs. - Developer-tool companies and B2B SaaS teams (per YC profile categorization) building AI features involving embeddings and retrieval. - Market positioning is ambiguous because third-party directories describe Ecliptor as a go-to-market / "product champion" identification platform for devtool companies (a category distinct from PDF parsing). The product demo, however, is focused on document-to-markdown ingestion. - Practical interpretation: Ecliptor may have pivoted or may be running multiple experiments or products under the same name. - Company background (founding year, HQ, key leadership) - Y Combinator profile lists: - Batch: Winter 2024 - Status: Active - Founded: 2023 - Location: San Francisco - Founders: Andre Fu and Nanki Grewal. - Funding and growth: investment rounds, acquisitions, estimated customer count/revenue if public - Public funding figures are inconsistent across sources: - Some directories list a small early funding amount with an accelerator investor. - Other profiles claim no external funding and a bootstrapped status and do not provide revenue information. - No credible public customer count or revenue is available from primary sources. - Pricing model with specific tiers and costs where available - Pricing is not publicly posted on the company’s main domain (site is "Coming Soon"). - The demo page directs interested users to schedule time or email, which suggests sales-led or pilot-based pricing. - Third-party directories typically list "contact for pricing." - Total cost of ownership considerations (implementation, training, hidden costs) - Likely cost drivers for a PDF→Markdown ingestion API in production: - Document volume (pages/month) and compute/OCR costs. - Quality requirements (tables, multi-column layouts, scanned PDFs) that increase processing time and error handling. - Downstream costs: embedding generation, vector DB storage, re-chunking strategies, and evaluation. - Security/compliance work (vendor due diligence, DPIA, data processing terms) may be substantial given limited public security documentation. - Key competitors in the space (list 4-6 direct alternatives) - PDF.ai "Parse" API (returns markdown, chunking, inline images). - Adobe PDF Services "PDF to Markdown API" (enterprise document extraction pipeline). - docpull.ai (PDF→markdown minimal HTTP API with per-page payment positioning). - pdf2markdown.io (PDF→Markdown + API). - markitdown.ai (multi-format document→markdown, web app + API positioning). - hardparse.com (OCR-focused, outputs markdown/LaTeX; "keyless" API positioning).

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

Download full report →