eidos
Eidos is a TypeScript-based personal data management framework that brings Notion-like functionality and SQLite capabilities to your local machine. It supports offline-first workflows, AI integration, and extensibility through custom scripts and UI blocks.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | mayneyao/eidos |
| Owner | mayneyao |
| Primary language | TypeScript |
| License | AGPL-3.0 — OSI-approved |
| Stars | 3.1k |
| Forks | 135 |
| Open issues | 17 |
| Latest release | v0.32.2 (2026-05-30) |
| Last updated | 2026-07-05 |
| Source | https://github.com/mayneyao/eidos |
What eidos is
Built in TypeScript, Eidos provides a local-first SQLite database with real-time document and table editing, LLM integration for AI features, and an extension system supporting custom JavaScript/TypeScript/Python scripts and micro-blocks. Data is stored in open SQLite format.
Get the eidos source
Clone the repository and explore it locally.
git clone https://github.com/mayneyao/eidos.gitcd eidos# 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 applies to the main project; plan carefully if building commercial products—use only MIT-licensed packages (@eidos.space/core, @eidos.space/react) or dual-license your derivative.
- Project is actively developed but pre-production; expect breaking changes, incomplete features, and API instability in minor releases.
- Requires Node.js/pnpm and SQLite extensions setup; desktop development flow is straightforward but verify extension compatibility with your target OS/platform.
- LLM integration is built-in but requires external LLM provider setup; no vendor lock-in but you manage API keys and costs.
- Extension system allows custom TypeScript/JavaScript/Python; requires developer familiarity with extension APIs and testing harness.
When to avoid it — and what to weigh
- Production systems requiring guaranteed uptime — README explicitly states Eidos is under active development and not recommended for production use. Stability and release timeline are uncertain.
- Enterprise multi-user collaboration — Designed as a personal data framework. No evidence of built-in multi-user synchronization, access controls, or team collaboration features.
- AGPL-incompatible commercial products — AGPL-3.0 license requires derivative works to be open-source and available to users. Proprietary closed-source deployments must use MIT-licensed subpackages only (core, react, extensions).
- Mature ecosystem with broad integrations — Early-stage project (launched mid-2023). Integration landscape, third-party plugins, and long-term vendor support are unknown.
License & commercial use
Eidos main project: AGPL-3.0 (derivative works must be open-source). Core, React, and extension packages: MIT (permissive, commercial-friendly). If you build on Eidos without modifications, AGPL does not apply; if you modify and deploy, AGPL obligations trigger.
Commercial use of Eidos as-is (unmodified) for personal/internal data management is likely permissible under AGPL, but distributing modified versions requires making source code available. Building commercial products on top requires using only MIT-licensed packages (@eidos.space/core, @eidos.space/react) to avoid AGPL viral clause. Consult legal counsel for your specific distribution model.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Needs review |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
Local-first architecture reduces attack surface (no cloud transmission). SQLite is mature and well-audited. No mention of data encryption at rest, secure key storage, or authentication mechanisms. If deploying beyond single-user local use, implement your own access controls, encryption, and audit logging. Third-party LLM integration may expose data to external services—review privacy implications. Extension system allows arbitrary code execution; review custom extensions carefully.
Alternatives to consider
Notion
Cloud-based competitor with team collaboration, mature integrations, and commercial support. Requires internet and vendor trust; Eidos offers local-first control.
Logseq
Open-source, local-first alternative focused on knowledge graphs. Lighter-weight than Eidos but less structured database support. MIT-licensed, simpler extension model.
Obsidian
Mature local-first PKM tool with large plugin ecosystem. Proprietary but permissive for personal use. Better documented, larger community, more stable. Less built-in database and AI features.
Build on eidos with DEV.co software developers
Contact Devco to assess whether Eidos fits your architecture, navigate AGPL licensing, or build custom extensions and integrations tailored to your use case.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
eidos FAQ
Can I use Eidos in a commercial product?
Is Eidos production-ready?
How do I run Eidos?
Can Eidos work offline?
Software development & web development with DEV.co
DEV.co helps companies turn open-source tools like eidos into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source databases stack.
Evaluate Eidos for your next project
Contact Devco to assess whether Eidos fits your architecture, navigate AGPL licensing, or build custom extensions and integrations tailored to your use case.