TiloBox
Back to directory
FerretDB project preview

FerretDB

Truly open-source MongoDB alternative built on top of PostgreSQL and SQLite.

LicenseApache-2.0
GitHub stars8.5k
Last commit1 weeks ago
Tags5 topics
Document Db ProxyMongodb AlternativeGolang FerretdbPostgres Document StoreDatabase
Overview

Why consider FerretDB?

FerretDB is an open-source proxy and database engine written in Go. FerretDB translates MongoDB wire protocol 6.0+ queries into SQL executed against PostgreSQL or SQLite, allowing organizations to run existing MongoDB apps and drivers on 100% open-source relational databases.

Guided learning

Learn FerretDB by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of FerretDB

FerretDB enables standard MongoDB drivers to store BSON documents seamlessly inside PostgreSQL tables.

Docker Quickstart

bash
1docker run -d --name ferretdb -p 27017:27017 -e FERRETDB_POSTGRESQL_URL=postgres://user:pass@db:5432/ferretdb ghcr.io/ferretdb/ferretdb:latest

FerretDB is licensed under the Apache License Version 2.0.

Related tools

More options with a similar category or technology profile.

FerretDB FAQs

FerretDB is listed as a Developer Tools tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

FerretDB is listed under the Apache-2.0 license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

FerretDB is listed as an alternative to DocumentDB. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.