OctoBase
OctoBase is an open-source, offline-first collaborative database written in Rust, designed to power applications like AFFiNE. It combines CRDT-based P2P synchronization, full-text indexing, and binary storage in a single embedded or standalone engine.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | toeverything/OctoBase |
| Owner | toeverything |
| Primary language | Rust |
| License | AGPL-3.0 — OSI-approved |
| Stars | 2k |
| Forks | 138 |
| Open issues | 35 |
| Latest release | p20230904 (2023-09-04) |
| Last updated | 2025-03-05 |
| Source | https://github.com/toeverything/OctoBase |
What OctoBase is
A Rust-based CRDT database with native support for WebSocket and WebRTC sync, pluggable storage backends (SQLite, Postgres), schemaless data modeling, and multilingual full-text indexing. Embedded as a library or deployable as a standalone server.
Get the OctoBase source
Clone the repository and explore it locally.
git clone https://github.com/toeverything/OctoBase.gitcd OctoBase# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- AGPL-3.0 copyleft terms: any proprietary use requires separate license or CLA acceptance. Review your deployment model (SaaS vs. embedded).
- Project under heavy development; expect API instability and breaking changes before 1.0. Pin versions carefully and monitor issues/PRs.
- Requires Rust toolchain and Cargo for compilation. WebAssembly support and language bindings are incomplete; plan integration work.
- Storage backend choice (SQLite vs. Postgres) and sync transport (WebSocket vs. WebRTC) must be decided upfront; switching later may be costly.
- Fine-grained permission model is present but full-text indexing and S3 adapters still work-in-progress; validate against feature checklist.
When to avoid it — and what to weigh
- Production systems requiring high stability — Project explicitly states most components are not production-ready. Latest release is from Sep 2023; version 1.0 not reached. Major breaking changes possible.
- Proprietary or permissive-license-only requirements — AGPL-3.0 requires source disclosure of modifications and derivative works. Stated plan to switch to MPL 2.0 post-1.0, but currently AGPL-locked.
- Need for Java/Swift bindings in production — Java and Swift bindings are still in progress (marked 🚧). Only Rust and FFI integrations are stable.
- Simple relational data models only — OctoBase is optimized for schemaless, unstructured, and rich-media data with CRDT semantics; not a traditional RDBMS replacement.
License & commercial use
Licensed under AGPL-3.0 (GNU Affero General Public License v3.0). This is a copyleft license: any derivative work or SaaS deployment must publish source code and make modifications available to users. Not a permissive OSI license like MIT or Apache-2.0.
Commercial use is possible only under these conditions: (1) internal/private use without SaaS distribution, or (2) obtain a separate commercial license from ToEverything. Deployment as a cloud service triggers AGPL disclosure obligations. Contributor License Agreement required. Planned license migration to MPL 2.0 post-1.0 may relax terms, but no timeline given.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Limited |
| License clarity | Clear |
| Deployment complexity | High |
| DEV.co fit | Possible |
| Assessment confidence | Medium |
No security audit data, penetration test results, or vulnerability disclosure policy provided in documentation. CRDT sync and permission control are implemented, but security posture is unverified. AGPL copyleft may provide visibility into modifications. Recommend independent security review before production deployment and evaluation of blob encryption (not mentioned).
Alternatives to consider
y.js / Yjs + Postgres
Established CRDT library with MIT license, more mature ecosystem, and flexible backend options. Requires more custom integration but less production risk.
Firebase Realtime Database / Firestore
Managed cloud-first collaborative database with SaaS, strong docs, and no license concerns. Suitable if vendor lock-in acceptable and offline-first not critical.
WatermelonDB / Realm
Production-ready embedded mobile databases with simpler schema and licensing. Less full-featured than OctoBase but lower risk for MVP.
Build on OctoBase with DEV.co software developers
Review the production-readiness checklist, test the latest build in a sandbox environment, and assess AGPL licensing impact on your business model before committing.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
OctoBase FAQ
Can I use OctoBase in a commercial SaaS product?
Is OctoBase production-ready?
What storage backends are supported?
How do I sync data across devices?
Software development & web development with DEV.co
Adopting OctoBase is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source databases software in production.
Ready to evaluate OctoBase for your project?
Review the production-readiness checklist, test the latest build in a sandbox environment, and assess AGPL licensing impact on your business model before committing.