Specifications, roadmap, and design documentation for inGitDB — covering the storage format, schema definitions, system-level features, and component behaviors shared across all implementations.
- Storage Format — directory layout, config files, collection schema, column types, record files
- Schema Reference —
.definition.yaml, views, triggers, subcollections, subscribers - Features — feature specifications with status (implemented / WIP / planned)
- Components — Validator, Scanner, Views Builder, Watcher, Triggers, MCP Server, Merge Conflict Resolver, Migration Generator
- Roadmap — nine delivery phases from Validator to GraphQL
- Backlog — concrete tasks with acceptance criteria, ordered by dependency
- Competitors — honest feature comparison with related tools
- Guidelines — design and process guidelines
- GitHub App — plans for dependency validation and PR auto-merge GitHub App
- Plans — migration and design decision records
- Proposals — feature proposals and integration design studies
- ingitdb-cli — Go CLI, the reference implementation
When working locally, both repos share the same parent directory:
../ingitdb-cli/
- github.com/ingitdb/ingitdb-cli/pkg/ingitdb — Go package for working with local inGitDB files
- github.com/ingitdb/dalgo2ingitdb — DALgo bridge to inGitDB
- TypeScript clients — ingitdb-ts — pnpm workspace monorepo:
- @ingitdb/client — core interface, shared types, and utilities
- @ingitdb/client-github — GitHub REST API implementation
- @ingitdb/client-fs — local filesystem implementation (coming soon)
See docs/components/clients.md for architecture details.
Apache 2.0 — see LICENSE.