MongoDB's own Voyage AI quick start says to create the model API key in the Atlas UI, and mongodb.com's Voyage page sends "Get Started" to Atlas with a Voyage onboarding scenario. But voyageai.com, titled "Voyage AI by MongoDB", sends both "Get Started" and "Sign in" to a separate Voyage dashboard login, and docs.voyageai.com tells developers to create a key there. A developer who starts at the older brand site lands in an account that is not Atlas, so the new Growth Marketing Manager cannot run the cross-sell into Atlas and Vector Search that the role is hired for.
First action
Count last month's new Voyage dashboard signups versus Atlas signups with the Voyage onboarding scenario.
How to measure it
New Voyage developers starting in Atlas
- Now
- –
- Target
- 90%
- By
- 90 days
Steps
Size the split
New Voyage dashboard accounts versus Atlas Voyage signups over the last 90 days, and how many of each later created a cluster.
Marketing Analytics 3 days
Agree the rule
New developers go to Atlas; existing dashboard users keep signing in where they are.
Growth Marketing Manager, Voyage AI 2 days
Change the buttons
"Get Started" on voyageai.com to Atlas with the Voyage onboarding scenario and a source tag.
Web Engineering Lead 2 days
Match the docs
docs.voyageai.com key page points new users to the Atlas key path first.
Documentation Lead 1 week
Offer the move
Guided migration for dashboard accounts that keeps their free tokens and keys.
Senior Director Product Management, Growth 1 month
Start the lifecycle
Atlas-native onboarding emails from first key to first embedding to first vector index.
Growth Marketing Manager, Voyage AI 2 weeks
Read the result
Activation and Atlas cluster creation by front door, weekly.
Marketing Analytics weekly
Why it works
Point voyageai.com's "Get Started" at Atlas registration with the Voyage onboarding scenario (keep "Sign in" for existing dashboard users), add a short "Already on Atlas? Create a model API key" path, and tag every entry with its source. For existing dashboard accounts, offer a guided move that keeps their free-token balance and key, then measure activation (first embedding call) and Atlas cluster creation by front door.
Every new Voyage developer then starts inside Atlas, where in-product prompts, lifecycle email and Vector Search are one click away, and the funnel is measured in one place.
Ready to use
ChecklistVoyage front door checklist
[ ] voyageai.com Get Started -> Atlas register (onboardingScenario=voyage, source tag) [ ] "Sign in" kept for existing dashboard users [ ] docs.voyageai.com key page: Atlas path first [ ] Pricing pages say the same free-token allowance [ ] Migration offer for dashboard accounts [ ] One activation event (first embedding) tracked for both paths [ ] Weekly report by front door
Risks and how to handle them
Existing Voyage customers feel pushed
Keep their login and keys working; make the move optional and keep their balance.
Standalone API users do not want a database account
Say on the page that no cluster is needed to use the models.
Evidence
- Voyage AI websitevoyageai.com (checked October 21, 2026) is titled "Voyage AI by MongoDB" and is its own canonical site. Its "Get Started" and "Sign in" buttons go to dash.voyageai.com, a separate Voyage account login, and its docs links go to docs.voyageai.com. It loads its own email marketing script.Source
- Your websitemongodb.com's Voyage AI page sends "Get Started" to Atlas registration with onboardingScenario=voyage, and the MongoDB docs quick start says: "To access Voyage AI models, create a model API key in the MongoDB Atlas UI", under "AI Model APIs" in an Atlas project.Source
- Voyage AI docsdocs.voyageai.com is a second, self-canonical documentation set with its own llms.txt, its own pricing page and its own key instructions: "sign in with your Voyage AI account and click the 'Create new secret key' button" in the Voyage dashboard. Its pricing gives "the first 200 million tokens" free for voyage-4 models "for every account".Source
- HiringGrowth Marketing Manager, Voyage AI (two openings, United States and Toronto, posted October 8, 2026): drives "growth and adoption of Voyage AI by MongoDB" across "discovery and onboarding through activation, adoption, and expansion", with lifecycle work "across email, in-product, content, and emerging channels", and asks for experience "designing and executing cross-sell/up-sell strategies to expand customer adoption across product offerings".Source