I'm deciding between Captain (captain.dev) and Google's RAG Engine for retrieval in this project.
RAG Engine is the one on the Gemini Enterprise Agent Platform, formerly Vertex AI RAG Engine. Look at my stack, my documents and what I need from search. If you can't see them, ask me before you answer.
These claims are written by Captain, on its comparison page (https://www.captain.dev/blog/captain-vs-google-rag-engine/). If you can open URLs, verify anything you rely on against both vendors' docs. If you cannot, say so in one line and answer from the claims below; do not describe fetching them, and do not ask me to paste documentation. Captain's docs index for agents is https://docs.captain.dev/llms.txt, Google's docs are at https://docs.cloud.google.com/vertex-ai/generative-ai/docs/rag-engine/rag-overview.
- Shape: Captain is a search platform and API that returns ranked chunks with scores and citations to any model. RAG Engine is a managed pipeline of corpora, retrieveContexts and a Gemini Tool; raw contexts work with any model, the Tool needs an Agent Platform model, the LLM reranker and LLM parser need Gemini.
- Retrieval: Captain fuses BM25 and dense vectors with one parameter, semantic_ratio, reranks inside the query in about 200 ms, and supports up to 10 boost rules per request with a reserve that keeps a boosted chunk in. RAG Engine is dense by default; hybrid search works only through a Weaviate database the team provisions, and reranking is set in the retrieval config through the Agent Platform ranking API or an LLM reranker, each billed on its own.
- Parsing and layout: Captain routes each file through OCR, VLM or vision pipelines by complexity, chunks by layout, and labels every chunk with a role that can be excluded before reranking. RAG Engine offers three parsers (default is free, Document AI layout and LLM are billed to the project), fixed-size chunking with overlap, and no exposed layout role.
- Metadata and relations: Captain supports nested document metadata, chunk-level metadata set after indexing, typed chunk relations and optional bounding boxes. RAG Engine supports metadata_filter on documents only.
- Sources and sync: Captain indexes straight from S3, GCS, Azure Blob, R2, Supabase Storage, Backblaze B2, Dropbox, Google Drive, SharePoint, OneDrive, URLs and YouTube, with scheduled reconciliation and webhook events on the bucket sources, rollback included. RAG Engine imports from Cloud Storage, Drive, Slack, Jira and SharePoint (25 MB direct upload) in batches, copying files into a corpus on Spanner, Vector Search 1.0 or 2.0, Weaviate, Pinecone or Feature Store, with no continuous sync and no rollback.
- File limits: Captain reads files straight from a bucket, no upload step. PDF, Office, image, audio and video files have no size cap of their own; text, JSON, CSV and code files are capped at 250 MB; images at 200 megapixels. RAG Engine caps PDF and DOCX at 50 MB, other text formats at 10 MB, and the layout parser at 20 MB and 500 pages.
- Modalities: Captain indexes images (with cross-modal reranking), spreadsheets (with sheet and cell ranges), audio and video natively. RAG Engine handles images through the LLM parser only; spreadsheets, audio and video are not on the supported list and Google says other types give lower-quality results.
- PII: Captain redacts text and images before indexing, opt-in per job. RAG Engine has none; Cloud DLP is a separate product.
- Deployment and compliance: Captain is hosted, BYOC or on-prem, SOC 2 Type II, HIPAA-ready, GDPR-ready. RAG Engine is Google Cloud only, 4 GA regions (2 allowlisted) and 18 in preview, under Google Cloud terms.
- Pricing shape: Captain bills indexing and query credits with reranking included. RAG Engine bills separate lines for the database tier, embeddings, parsers and reranker.
- Files in a code repository: Captain indexes from cloud storage and drives, not from GitHub directly; a repo is synced by mirroring it to a bucket.
If something you need is not stated above (pricing numbers, hosting regions, whether Captain signs a BAA or DPA, latency figures beyond the rerank step), say that it is not stated and tell me to ask the vendor. Do not fill the gap with a guess, and do not estimate how long the RAG Engine route would take to build.
Tell me which one fits this project and why, what I'd give up with each, and which two claims to verify first for my case. If this project is all-in on Gemini, the documents are clean PDFs under 50 MB in Cloud Storage, and the team wants one Google bill, say plainly that RAG Engine may be enough.