Docpose.cloud
Online File Converter, OCR & Developer API
Hey IndieHackers 👋
We’ve rolled out integrated, GPU-powered OCR inside the Docpose.cloud conversion API for paid users.
Now when a scanned PDF or image is uploaded, our system automatically detects non-searchable content and applies OCR directly inside the conversion pipeline — no extra endpoint, no additional workflow.
What’s included:
• GPU-accelerated OCR processing
• 100+ languages supported
• Automatic language detection
• Optional manual language override
• Table detection with structured layout preservation
• Handles complex layouts (multi-column docs, forms, mixed content)
• Works with scanned PDFs and images (JPG, PNG, TIFF, etc.)
• Output includes fully searchable PDFs
OCR-enabled conversions support output to:
TXT, RTF, DOCX, XLSX, XLS, CSV, PPTX, searchable PDF, EPUB, DJVU, FB2 — and many more formats supported by our pipeline.
Examples:
Scanned invoice → structured XLSX
Scanned contract → editable DOCX
Scanned legal agreement → searchable PDF
Scanned report → searchable PDF with selectable text
Scanned book → EPUB
Image → clean TXT or CSV
We focused heavily on preserving tables, formatting, and structured data because real-world documents aren’t simple paragraphs — they’re invoices, financial reports, compliance files, and legal documents where layout matters.
Architecture-wise:
OCR runs inside our existing S3-based job pipeline. No local persistence. Source files can be deleted instantly. Converted outputs follow our standard 24-hour retention policy. Logs remain scoped to system-level analytics.
This is built for SaaS teams handling document ingestion, legal tech workflows, compliance systems, financial automation, and archive digitization — where speed, structure, and accuracy are critical.
If you're running OCR in production, what’s been your biggest bottleneck: accuracy, layout preservation, or scaling under load?
Hey Indie Hackers 👋
I’m Eric, and I’ve been building SaaS products for years. One problem kept following me around: file conversion.
Every project needed it. PDFs, Office files, images, audio, video. And every time it meant stitching together libraries, dealing with broken edge cases, scaling workers, handling timeouts, or fighting unreliable third-party APIs.
It always became infrastructure debt.
So I built Docpose.cloud — a cloud-based file conversion platform and developer API that supports 400+ formats and 34,000+ conversion pairs.
What it does
Convert documents, images, audio, and even 4K/8K video
Simple REST API
Batch processing
Built for SaaS apps and automation workflows
No infrastructure to manage
The goal is simple:
Make file conversion boring, reliable, and production-ready.
Why now?
More SaaS tools are handling user-generated files. AI tools, no-code platforms, document apps, media platforms — everyone needs conversion somewhere in their pipeline.
But most teams don’t want to maintain LibreOffice containers, FFmpeg clusters, or custom workers.
They just want an API that works.
Current stage
Live product
Paying users
Actively improving performance and scaling
Working on better usage analytics & developer tooling next
I’d love feedback from the Indie Hackers community:
What would stop you from using a file conversion API?
What pricing model makes the most sense for this kind of infrastructure?
What integrations would you want first?
Happy to answer anything — technical or business.
— Eric
Founder, Docpose.cloud
-
2
Strong positioning. Making file conversion “boring” is actually a big value proposition for SaaS teams.
From a security perspective, this kind of infrastructure carries serious risk, so a few key questions:
• How are you sandboxing file processing workers to prevent malicious file exploits or container escapes?
• Do you scan uploads for malware before processing?
• How long are uploaded files retained, and are they encrypted at rest?
Trust will be a major differentiator here. Clear documentation around isolation, retention policy, and processing architecture would help convince security-conscious SaaS teams.
The idea is solid. Security guarantees will determine enterprise adoption.
-
1
Totally fair callout — here’s how we handle retention in practice:
Files go straight to S3. Jobs stream from S3, convert, and stream the output back to S3 (no local saving on workers).
Retention defaults:
Source files: deleted immediately after the job pulls/starts processing.
Converted files: kept for 24 hours by default.
Users can delete both source + converted files anytime.
Logs:
We keep job/task logs (status, timings, errors, API call trail) up to 30 days for debugging/abuse monitoring.
When files are deleted, the job’s file-related records effectively expire from the user side; what remains is minimal system-side analytics/debug metadata.
Agree with you: making this clearer in docs is important — “boring conversion” only works if the security + retention story is simple and explicit.
-
2
You are right to focus on this. Infrastructure products live or die on trust.
As a security team building Nautillo Pro, we ask these same questions when we evaluate any SaaS that processes untrusted input.
For security conscious SaaS teams, architecture clarity matters as much as features.
When you process untrusted files, isolation and short retention are baseline requirements.
We built Nautillo Pro with the same mindset. Black box. Strict scope control. Minimal retention. Safe by design.
We also offer a free version. If you want to evaluate your own web app security from an external attacker perspective, Nautillo Pro is available to test.
-
1
Well said — trust really is the foundation for infrastructure products.
At Docpose cloud, we follow the same principles: isolated processing, direct S3 uploads (no local disk storage), immediate source deletion, 24-hour max retention for outputs, and minimal scoped logging.
Appreciate you sharing Nautillo Pro as well. We’re already running internal security reviews and external testing, but we’re always open to evaluating additional tools, we’ll definitely take a look.
Good to see more builders prioritizing “safe by design.”
-
-
-
1
Be the one of first 100 users to get 25% off on all plans, use code "PH25OFF".
1 Comment
Hello Eric Lewis, I saw your recent milestone, congrats! I’m a Virtual Assistant who supports founders with Customer Support VA, Executive VA. Let me know if you will be needing some support right now!
Congratulation, once again