Alpaqa Studio
Keep using Alpaqa Studio
Stay productive through 2025 and export your saved connections when you’re ready to migrate.
- Full access and maintenance through 2025
- Export saved connections anytime
- We’ll help you plan your move
Thank you
Alpaqa Studio stays online through 2025
Keep using the product through December 31, 2025. Export your saved connections whenever you’re ready and we’ll help you transition smoothly.
- Service and support through end of 2025
- Export saved connections anytime
- Subscriptions deactivated and reimbursed
Thank you for being part of Alpaqa Studio
As of January 1, 2026, Alpaqa Studio is no longer available. Thank you for the feedback, ideas, and trust that shaped the work now continuing in Microsoft’s Azure Cosmos DB extension and in Q9 Studio.
- Service concluded on January 1, 2026
- Explore the Cosmos DB extension for familiar workflows
What comes next
Choose the path that fits your team
Keep working in Alpaqa Studio through 2025, shift to Microsoft’s Azure Cosmos DB tools, or explore Q9 Studio for NoSQL data health.
After January 1, 2026
Where to go from here
Alpaqa Studio is closed. Here are the best next steps and where to reach us if you need records or help.
Cosmos DB
Azure Cosmos DB for VS Code
Many Alpaqa Studio ideas live on in the official VS Code extension, with more coming.
- Works alongside your existing code
- Official Microsoft support
- Built-in guidance shaped by Alpaqa Studio learnings
Q9 Studio
Look at Q9 Studio
Data health monitoring for NoSQL systems, with a focus on DocumentDB and MongoDB.
- Health dashboards and alerts
- Schema insights for DocumentDB and MongoDB
- Early access for Alpaqa Studio users
Cosmos DB
Use the Azure Cosmos DB extension
Your favorite exploration and data-shape workflows continue inside Visual Studio Code, with Microsoft support.
- Aligned with the Alpaqa Studio experience
- Runs inside VS Code alongside your projects
- Built and maintained by Microsoft
Q9 Studio
Explore Q9 Studio
We continue the data health journey as Q9 Studio, focused on observability for DocumentDB and MongoDB.
- Health dashboards and alerts
- Schema drift and data quality insights
- Shaped with feedback from Alpaqa Studio users
Need help?
Contact us about the transition
If you need a receipt, have questions about your account, or want to talk migration, we’re here.
- Direct replies from the team
- Privacy-first: we do not share your contact details
- Clear next steps for your data workflows
Q9 Studio
Born from your requests for data health monitoring
You asked for deeper visibility into NoSQL health. That’s why we’re building Q9 Studio: a data health layer for DocumentDB and MongoDB, shaped by Alpaqa Studio users’ needs.
Q9 Studio
Continuing the journey on data health
Your feedback on schema exploration and data shape directly inspired Q9 Studio—a dedicated data health and observability product for DocumentDB and MongoDB.
- Health dashboards and alerts for NoSQL workloads
- Schema drift and data quality insights
- Built with feedback from teams using Alpaqa Studio
Need a hand?
We’ll help you plan the next move
Staying on Alpaqa Studio or testing Q9 Studio? Tell us what you need, and we’ll jump in with guidance, calls, or migration checklists.
We’re still here to help
Questions about the wind-down?
If you need a receipt, a confirmation for your records, or want advice on your next toolset, reach out. We’re happy to help.
FAQ
Common questions
What the change means and where to go next.
How long can I use Alpaqa Studio?
Alpaqa Studio remains available and supported through December 31, 2025. Use it as normal until then.
Can I export saved connections?
Yes. Export from inside the app anytime in 2025 so you can take your configurations elsewhere.
What happens to subscriptions?
All subscriptions have been deactivated, auto-renewals are off, and any active subscriptions are being fully reimbursed.
Is my data shared with Microsoft?
No. Your contact details are not being shared. Your privacy remains important to us throughout the transition.
What happened to Alpaqa Studio?
The product was sunset on January 1, 2026 as we focused on the Azure Cosmos DB extension and on Q9 Studio.
Can I still log in or export data?
No. The service is no longer available. If you need help with past records, please email hello@alpaqastudio.com.
Where should I work now?
Use the Azure Cosmos DB extension in VS Code for the workflows you knew from Alpaqa Studio, and look at Q9 Studio for data health.
What about my data and privacy?
We have followed our Privacy Policy during the wind-down. If you need confirmation for your records, reach out and we will assist.