MongoDB has been a first-class Retool integration since 2018. Today, it’s one of the top-used databases on our platform, and Retool customers run millions of MongoDB queries every week across thousands of internal apps. That’s a lot of apps built on a lot of critical operations data.
As applications increasingly start with a prompt, that connection matters more than ever. Teams need to be able to build against real business data without creating a separate path to production.
That’s why we’re excited to make it official. Retool and MongoDB are kicking off a formal partnership, and we’re marking the moment with a big upgrade to how you connect Retool to MongoDB Atlas.
Built for how teams build now
Our customers run their operations on Retool and MongoDB every day. We’ve seen finance teams replace month-by-month reporting with live revenue dashboards, where every order sits in one place and can be filtered by time frame, product, or customer. We’ve seen sales teams build tools that generate custom purchase links in seconds, and operations teams pull vendor records and documents out of scattered files and into a single app that tracks orders in real time.
Look closely at what those apps touch: revenue, customers, and vendors. And more people are building apps like these than ever, faster than ever, with AI. If anyone can build an app on your most important data, how do you know it’s connected securely? Every app is only as secure as the credentials behind it, and the data layer is where the stakes are highest.
Together, we’re making it easier to ship apps on MongoDB Atlas without trading away security to do it. Our partnership is built on the data connection itself, giving teams a secure, governed path from MongoDB Atlas to the apps you build in Retool.
“Applications are increasingly starting with a prompt, but the data layer still has to carry them into production,” said Melissa Plunkett, VP of Product at MongoDB. “Our partnership with Retool makes it easier for teams to build against the MongoDB data their companies already rely on, with secure access and a foundation designed to scale as those applications become critical to the business.”
Secure credentials, built in
Connecting Retool to MongoDB has typically meant requesting access from your database admin (DBA). The DBA creates a database user, sets a password, and shares the connection details. That process works, but it adds manual steps for builders and DBAs. Over time, as databases, environments, and teams grow, it gets harder to keep track of which credentials exist and who’s responsible for them.
Now, if you’re on Retool’s cloud-hosted deployment, you can authorize Retool against your Atlas account, pick a cluster and a database, and choose read-only or read-write. Retool creates a database user scoped to exactly that. No human ever sees the password, so there’s nothing to leak and nothing to reuse outside Retool.
Least privilege becomes the default, because the tight option is now the easy one. Every credential Retool creates is scoped and tracked from the start, so when an auditor asks where a database credential came from, you have an answer. Builders ship today instead of next week, and your security team gets the visibility it needs without slowing anyone down.
A partnership years in the making
Your data is already in MongoDB. Your teams already know what they need to build. Now the connection between the two is fast, scoped, and secure by default. Automated Atlas credentials are available today for all Retool Cloud customers. Already connected to MongoDB? Your next resource can use the new flow. New to Retool? Talk to our team to see what you can build on your MongoDB data, or start building for free and connect your first cluster in minutes.