Datalab vs Google Cloud Document AI

Datalab 58

Hosted lines. Status page at status.datalab.to (incident.io) with Website and Datalab API components; the history page is drawn by script, so components are confirmed and history isn't (15 of 20, 5 for history). Rate limits per plan with numbers, plus page and size limits (15). 429 is retryable with sample backoff, and 500 and 529 say to check a known request ID before resubmitting; webhooks deduplicate by request_id (13 of 15). Custom SLAs only for Enterprise (0). Generally available (10). 15+5+15+13+0+10 = 58.

Google Cloud Document AI 90

Hosted reading. Google Cloud status page with a JSON incident feed (20). The feed holds eight incidents back to February 2026, four of them since 3 August, and none names Document AI. They are the 20 August outage that lists 27 products, the 1 September network degradation in us-central1-b, elevated upload and write errors in Cloud Storage in us-central1 from 8 to 9 October and the europe-west2 incident of 20 October (06:00 to 12:08 UTC, 38 products). Batch processing reads and writes Cloud Storage, but the GCS incident was in one region and Document AI isn't listed. The page shows only broad incidents (30). Quotas published with numbers, 1,800 requests a minute per user, 120 online process requests a minute per processor type in us and eu and 5 concurrent batch requests, on a page last updated 28 October (15). No retry or backoff guidance was found on the quotas, limits or request pages. Processing changes no state and failed requests are not billed, so a retry is safe (5 of 15). 99.9 per cent monthly SLA for online and batch prediction, re-read on 1 November (10). v1 is GA (10).

Datalab 68

Closed service under terms effective 30 June 2026 naming Endless Labs, Inc. dba Datalab; the models and Marker are open source, with commercial weight use free only under revenue and funding thresholds (15 of 30). Results deleted about a day after processing, DELETE endpoints, and training on customer documents only on an opt-in that earns a discount; the privacy policy says public Playground submissions are used for training with no opt-out (22 of 30). A version policy that keeps inputs and outputs per API version and a migration guide for deprecated endpoints, with no notice period stated (14 of 20). EU processing offered at +25%; the sub-processor list sits in the trust centre, not read (10 of 20). 15+22+14+10 = 61.

Google Cloud Document AI 90

Closed service under the Google Cloud terms, with Apache-2.0 client libraries (15 of 30). The security page says online requests are processed in memory, batch documents are deleted after processing with a failsafe of one day, and content is never used to train Document AI models. The service terms' training restriction and the Data Processing Addendum agree. Layout Parser versions on Gemini 3.0 route globally, which the docs state (27 of 30). The lifecycle page promises six months' notice for stable versions and lists a deprecation date per version, and the Cloud terms promise 12 months before a backwards-incompatible API change. The legacy processor notice of 17 February 2026 gave until 30 June 2026, about four and a half months (18 of 20). us and eu multi-regions, seven single regions and a public sub-processor list (20).

Datalab 40

No x402, MPP or L402 (0). Per-1,000-page rates for every processor and add-on on the public pricing page (20). A $10 to $20 monthly allowance with no card (20). A person signs up in a browser (0). 0+20+20+0 = 40.

Google Cloud Document AI 20

No x402, MPP or L402 (0). Per-page prices for every processor published without a login (20). The first 1,000 OCR pages show at $0.00 and new customers get $300 of credit, but the Free Trial page says sign-up needs a credit card or other payment method (0). A person creates the project and billing account in a browser (0).

Datalab 56

Several hashed API keys with per-key 30-day spend caps, revoke-and-replace rotation, no scopes (24 of 30). Spend caps limit damage; results and files can be deleted by the key holder, and there's no read-only key (10 of 20). Returns document text with no prompt-injection guidance (2 of 15). cost_breakdown per request and usage tracking in the dashboard (8 of 15). A Secureframe trust centre and a SOC 2 report on the Team plan, TOTP enforcement for teams; no disclosure policy or security.txt found (12 of 20). 24+10+2+8+12 = 56.

Google Cloud Document AI 70

OAuth 2.0 bearer tokens from service accounts with IAM. The docs and samples send the token in the Authorization header, but Google's OAuth 2.0 guide documents sending it as an access_token query parameter, the v1 Discovery document (revision 20261026) lists access_token, oauth_token and key as query parameters, and on 1 November documentai.googleapis.com and us-documentai.googleapis.com answered a request with no token "missing required authentication credential" and one with a made-up ?access_token= "invalid authentication credentials". So a token can travel in the URL, the 10-point deduction other Google APIs take (20). roles/documentai.apiUser allows processing only, roles can be granted on one processor, and deny policies and VPC Service Controls are supported. Nothing asks for confirmation before a processor is deleted (17 of 20). The service returns text from untrusted documents and no guidance on injected instructions was found in the pages read (0 of 15). The audit logging page (last updated 27 October) lists each method by permission type. ProcessDocument writes Data Access logs, which Google Cloud leaves off until the owner enables them (13 of 15). google.com security.txt valid to 1 April 2030 with the reward programme. The Document AI security page (last updated 26 October) states ISO 27001, SOC 2 and SOC 3 audits, FedRAMP High and HIPAA. None of the Google Cloud security bulletins, from GCP-2019-001 to GCP-2026-074 (28 October 2026), names Document AI (20).

Datalab 89

An OpenAPI 3.1 operation embedded in each reference page (spec version 0.0.1), no single downloadable file found (22 of 25). llms.txt with 159 pages and Markdown twins (10). Recipes say when to use each processor and mode (15 of 20). Typed request schemas with enums for output format and mode (12 of 15). An error table with type, HTTP code and whether to retry, plus SDK exception mapping (15). A written version policy and a dated changelog (15). 22+10+15+12+15+15 = 89.

Google Cloud Document AI 81

A public Discovery document for v1, revision 20261026, with 42 methods and 326 schemas, and a second for v1beta3 (25). docs.cloud.google.com/llms.txt answers 404 and Accept: text/markdown returns HTML. A page address with .md.txt added answers as Markdown, which no page we read links, so half (5 of 10). Method descriptions are one line each. The overview has a table of which processor fits which job (15 of 20). 952 of 966 properties carry a description and 58 are enums. Required fields are marked only in prose, the three document sources are a union stated in a comment, and advancedOcrOptions is a free list of strings (11 of 15). The request page has samples in curl, PowerShell, C#, Go, Java, Node.js, Python and Ruby. No Document AI page listing error codes was found (10 of 15). v1 and v1beta3, and dated release notes with a feed (15).