Introducing RakeSign: Free, Unlimited Document Signing

Journal

Field notes

What we’re building, what we’re learning, and how operations hold up under AI.

  1. Give your agent hands: the paperwork CLI, skills, and MCP

    Day 5 of launch week. One CLI that is the whole API in your terminal, fifteen skills that teach an agent how to behave with documents, and an MCP server for everything that cannot run a shell. Your agent handles a thousand-page contract without reading a thousand pages.

  2. Introducing the Paperwork API: the whole platform, one surface

    Three days of models and products. Today, the API that ties them together. Six capabilities, one call pattern, evidence beside every step, and a repo of runnable examples you can steal from.

  3. Introducing rakeaudio-asr: conversations are documents too

    The audio pipeline behind the CloudRaker Paperwork API. Transcription at 270x realtime, speaker separation at 150x, one flat rate at every volume.

  4. Introducing RakeSign: Free, Unlimited Document Signing

  5. CloudRaker Achieves SOC 2 Type 2 Compliance

  6. Introducing rakedoc-nano: a state-of-the-art open-weight VLM for document parsing

    A 1.2B-parameter vision parser behind the CloudRaker Paperwork API. State-of-the-art among open-weight parsers, bounding boxes on every element, and enterprise pricing of $0.60 per 1,000 pages.

  7. CloudRaker vs. DocuSign: The Signature Workflow on Canadian Infrastructure (2026)

  8. CloudRaker vs. AWS Textract: A Full-Workflow Alternative (2026)

  9. CloudRaker vs. Datalab: OCR & Document Extraction API Comparison (2026)

  10. CloudRaker vs. LlamaParse: Document Processing Comparison (2026)

  11. CloudRaker vs. Reducto: Document AI Platform Comparison (2026)

  12. CloudRaker vs. Google Document AI: A Full-Workflow Alternative (2026)

  13. CloudRaker vs. CareWay: Build vs. Buy for the AI Medical Scribe

  14. Giving Claude (or any agent) a paperwork tool

  15. Inside the CloudRaker API: one pipeline, from raw PDF to signed document

    CloudRaker is the paperwork infrastructure. That's the tagline. This is what it means in code.

  16. CloudRaker vs. stitching a document pipeline together yourself

    If your product touches contracts, claims, forms, or any document-heavy workflow, at some point someone on your team has had this conversation: "we just need to pull structured data out of this PDF and get it signed — how hard can that be?" It's never just that.