Launch a Document Store: Managed MongoDB With a Browser Admin Console
Spinning up a document database you can actually look at usually means two jobs. Provision MongoDB. Then, because the shell is not where you want to browse a collection at 2am, install a GUI, point it at the database, paste in a connection string, and remember to turn on TLS. The store you wanted was always one round of plumbing away from being usable.
The Launch a document store stack collapses that into one button. You get a managed MongoDB running on your own infrastructure, EU-resident, with a Mongo Express admin console wired on top, in minutes, with nothing to connect by hand.
What you launch
Pick Launch a document store from the catalog and the platform stands up two things and connects them:
- Your own MongoDB. A managed MongoDB 7.0 database that is the durable home for your documents. A real database with a TLS endpoint and a primary user, not a black box. Connect any driver to it.
- Mongo Express, attached to it. An open-source web admin UI that lets you browse databases, collections, and documents, and run queries, all from your browser.
The console already knows the database address and credentials. A single full connection URL is injected during launch, so by the time the stack reaches Running there is nothing left to configure. You open the URL, sign in with the generated basic-auth password, and you are paging through documents.
A console and a database that agree
The point of the console is to make your data legible without a client install. Create a notes collection in the admin UI and insert a document:
{ "title": "First note", "tags": ["hello", "mongo"], "pinned": true }
Filter the collection with a query right in the search box:
{ "pinned": true }
That is the same data any MongoDB client sees, because the console reads it live from the database. For application traffic, connect a driver directly to the same store:
mongosh "mongodb://<db-user>:<password>@<db-host>:27017/defaultdb?tls=true&authSource=defaultdb" \
--eval 'db.notes.find({ pinned: true })'
The document you wrote in the browser is right there. The console and your application are two views of one database you own, with no proprietary store and no export job in between.
Trust, built into the launch
Like every stack, the document-store launch carries the platform guarantees in the flow itself.
A hard cost preview before you launch. You see exactly what the stack costs, the database plus the console, broken down per resource, before anything is provisioned. You accept a number, then the launch runs.
Atomic rollback. A stack is two resources coming up together. If either step fails, the whole launch rolls back cleanly. You end up with the finished document store or with nothing, never with an orphaned database quietly costing you money.
EU data residency. The database, the Mongo Express console, and the traffic between them all stay within the platform's European footprint. The console connects directly to the served MongoDB primary over TLS. Residency is where the platform runs, not a setting you remember to flip.
Launch one
# 1. Preview the cost
curl -X POST https://api.foundrydb.com/stacks/preview \
-H "Authorization: Bearer $FOUNDRYDB_TOKEN" \
-H "Content-Type: application/json" \
-d '{"template_name": "document-store"}'
# 2. Accept the previewed total and launch
curl -X POST https://api.foundrydb.com/stacks \
-H "Authorization: Bearer $FOUNDRYDB_TOKEN" \
-H "Content-Type: application/json" \
-d '{"name": "my-document-store", "template_name": "document-store", "accepted_monthly_cost": 51.00}'
Poll the stack until it is Running, open the endpoint_url, sign in, and you are browsing documents. Or do the whole thing from the Stacks catalog in the console with one click.
For the full walkthrough, including revealing the console password, inserting and querying documents, connecting a driver directly, and tearing the stack down atomically, read the Launch a document store tutorial.
Stop wiring a GUI to a database. Launch the finished thing, on MongoDB you own, in Europe, today.