Lewis Lien PolanskyCEO & Co-FounderRagie's hosted service will end on Sunday, July 19, 2026. To help customers keep their applications running, many Ragie customers have been migrating to Captain.
9 min read
Fig. 00 · four steps from a Ragie index to a Captain collectionRagie's hosted service will end on Sunday, July 19, 2026. To help customers keep their applications running, many Ragie customers have been migrating to Captain.
Captain provides managed multimodal indexing and retrieval for AI applications. Most customers with access to their original source data can begin setting up their migration in under 15 minutes.
Need help migrating? Email humans@captain.dev with your company name, approximate data volume, and current Ragie integrations.
First, determine where your original documents and data are stored.
If your data remains available in a source such as local storage, Amazon S3, Google Drive, Google Cloud Storage, Dropbox, or another supported storage system, you can connect that source directly to Captain. You do not need to move the original data through Ragie first.
If the only copy of your data is stored in Ragie, email support@ragie.ai as soon as possible with:
Ragie will provide current information about export availability, processing time, pricing, and the data included in the export. Because exports require manual processing, customers should submit requests as early as possible.
Captain organizes indexed data into collections. A Captain collection generally serves the same role as a Ragie partition: it provides a logical boundary for a particular application, customer, workspace, or dataset.
Captain can index text, documents, images, audio, video, and other file types. It includes document parsing, hybrid search, reranking, relationships between related chunks, multimodal understanding, and built-in retrieval evaluations.
To receive migration assistance, email humans@captain.dev with:
Captain is providing hands-on migration support and discounted pricing for Ragie customers.
Using an AI coding assistant? Provide docs.runcaptain.com/llms.txt as context for current Captain API documentation and migration guidance.
Captain currently supports sources including:
See Captain’s documentation for specific guides and endpoints.
Some integrations are available through Captain Studio but do not yet support programmatic indexing through the Captain API. Captain’s team can confirm the best migration method for your particular sources.
When migrating exported Ragie data, Captain will help determine whether the export should be uploaded directly, transformed, or reindexed from the underlying source documents. In most cases, Captain will generate a new index rather than relying on previously generated embeddings.
After your indexing jobs complete successfully, update your application to query the corresponding Captain collection through Captain’s v3 Query API.
Before directing production traffic to the new collection, test a representative set of existing searches and application workflows. Compare the returned results, citations, metadata, filters, latency, and access-control behavior with your existing Ragie implementation.
Once you have validated retrieval quality and application behavior, update your production credentials and endpoint configuration to direct traffic to Captain.
Captain’s migration team is prioritizing Ragie customers during the transition. Contact humans@captain.dev for assistance mapping your existing implementation to Captain.
In most cases, yes. You can build and test your Captain collection while your current Ragie integration remains active, then switch your application after validating the new setup.
Because Ragie’s hosted service is scheduled to end on July 19, customers should begin the process immediately and allow enough time for indexing and testing.
Indexing time depends on the number, size, and type of files being processed. Large initial migrations may require a temporary indexing-capacity increase. Contact Captain in advance if your initial migration is large so the team can help plan appropriate indexing capacity.
Captain is offering discounted pricing for transitioning Ragie customers. Contact humans@captain.dev with your company name and expected data volume to receive migration pricing.
Tell Captain which integration or workflow is blocking your migration. The team will assess the requirement and determine whether it can provide a workaround, migration service, or prioritized integration support.
During the Ragie migration effort, Captain has already expanded support for capabilities including Dropbox API indexing, source change detection, Supabase Storage indexing, and improved transcription.
For questions about Ragie data exports or your existing Ragie account, contact support@ragie.ai.
For Captain onboarding, indexing, API migration, or pricing assistance, contact humans@captain.dev.
Lewis Lien Polansky
CEO & Co-Founder · CaptainLewis is co-founder and CEO of Captain, building self-tuning file search for AI agents.
Elasticsearch ships without parsing, OCR, chunking, embeddings, connectors or sync. Teams add four to seven vendors to cover the gaps, then own every seam between them. Captain includes all of it behind one index call.
5 min read
Cloudflare AI Search caps files at 4 MB, chunks at a token count and metadata at five fields, because it runs on Workers and Vectorize. Captain has no file size cap, picks optimal chunk boundaries, and stores whatever metadata you send.
6 min read
Google's RAG Engine ships the parts: a layout parser, an embedding model, a vector store and a reranker, each set up, billed and maintained on its own. Hybrid search needs sparse vectors you compute yourself, and import is a batch job with no rollback. Captain does all of it in one call from your bucket.
5 min read
Benchmarks, engineering write-ups and the occasional retraction, straight from the source.
